Tails

#1 Updated by intrigeri 2017-08-05 12:34:37

• blocks Feature #13233: Core work 2017Q3: Sysadmin (Maintain our already existing services) added

#2 Updated by bertagaz 2017-08-06 10:15:25

• Category set to Infrastructure
• Status changed from New to Confirmed

groente wrote:
> I’m tempted to give it another 20GB so it won’t give warnings for a while, but we’re starting to run low on diskspace on lizard.

Given how short we are in disk space, I’d say let’s grow it only from 10G for now. Better not to allocate too much. This should be enough to get rid of the warnings too anyway.

After 3.1, I should be able to resume on Bug #13425 to get things forward faster.

#3 Updated by intrigeri 2017-08-13 17:03:07

• Target version set to Tails_3.2

What’s the status here? This has been in warning state since 9 days, and at this rate things will start breaking by the end of the month.

#4 Updated by groente 2017-08-15 21:32:44

• Priority changed from Elevated to Low
• Target version changed from Tails_3.2 to Tails_3.3

considering the apt-snapshot disk troubles have been solved, i went and gave bitcoin another 20GB, 10 would’ve only solved the problem for a month, maybe two.
after Bug #13425 has been solved, it would be nice to give it another 100GB or so, so it can keep up with the blockchain for a while again.

#5 Updated by groente 2017-08-15 21:33:23

• related to Bug #13425: Upgrade lizard's storage (2017 edition) added

#6 Updated by groente 2017-08-15 21:33:39

• related to deleted (Bug #13425: Upgrade lizard's storage (2017 edition))

#7 Updated by groente 2017-08-15 21:33:48

• blocked by Bug #13425: Upgrade lizard's storage (2017 edition) added

#8 Updated by intrigeri 2017-08-26 06:37:32

• related to Bug #13177: Sort out the bitcoin-disk partition situation on lizard added

#9 Updated by intrigeri 2017-08-26 06:39:24

• blocks deleted (Bug #13425: Upgrade lizard's storage (2017 edition))

#10 Updated by intrigeri 2017-08-26 07:02:34

• Status changed from Confirmed to Resolved
• Priority changed from Low to Normal
• Target version changed from Tails_3.3 to Tails_3.2
• % Done changed from 0 to 100

groente wrote:
> i went and gave bitcoin another 20GB,

IMO this was a bit too bold a move: now we have only 35GB left on SSDs (+50GB left on rotating drives, but that’s useless for most of our needs), which leaves us very little margin to satisfy storage needs growth for other services until Bug #13425 is done.

> 10 would’ve only solved the problem for a month, maybe two.

Right, but I think the conclusion (adding 20GB instead) is buggy IMO. Let me explain :) There are two options:

• Either Bug #13425 is resolved within 1-2 months: then 10GB would have been enough.
• Or Bug #13425 is not resolved within 1-2 months: then quite possibly other, more critical services may need more storage as well in 2 months, and the additional 10GB you added for bitcoin-data might be exactly what we will lack to satisfy their needs.

Of course, in general we try to allocate enough storage to services for 1 year or so, in order to avoid having to constantly struggle with issues like the one this ticket is about. Sadly, due to suboptimal storage planning and work prioritization we’ve been in a less than ideal situation for a few months regarding available storage, so unfortunately we have had to incrementally add a little bit of storage here and there as needed recently instead of doing what we would ideally do.

See what I mean?

Moving up 1 meta level: I believe that’s the message bertagaz tried to convey in his comment above. It’s fine to disagree (neither bertagaz nor I are always right!), but in the future I’d rather see us resolve such disagreements before we perform operations that are hard to rollback. Most of our sysadmin work can be easily reverted, but shrinking storage volumes is not exactly cheap. OK?

> after Bug #13425 has been solved, it would be nice to give it another 100GB or so, so it can keep up with the blockchain for a while again.

Absolutely! Note that the exact estimate in sysadmin.git:systems/lizard/storage-2017-ticket_11806_2017Q2.ods is a bit lower. bertagaz updated it in July so I would hope it matches reality. It wouldn’t hurt if someone double-checked though :)

This being said, I’m closing this ticket as the immediate problem it was about has been resolved. I think we’ll add storage to have sufficient margin to all volumes once Bug #13425 is done, so let’s not keep this ticket open (tracking in Redmine only a tiny subset of this problem doesn’t seem very useful).

Thanks for fixing the immediate problem!

#11 Updated by groente 2017-12-08 21:57:31

• Status changed from Resolved to In Progress
• Assignee changed from groente to intrigeri
• Target version changed from Tails_3.2 to Tails_3.5
• QA Check set to Ready for QA

The chain keeps on growing, do you agree with increasing the lv with 60GB? According to the spreadsheet (which seems pretty accurate), that should keep it happy for another year.

#12 Updated by intrigeri 2017-12-09 06:01:14

• Assignee changed from intrigeri to groente
• QA Check changed from Ready for QA to Dev Needed

> The chain keeps on growing, do you agree with increasing the lv with 60GB? According to the spreadsheet (which seems pretty accurate), that should keep it happy for another year.

LGTM. Hopefully our SSD / rotating rust current status will allow you to do it the way it should despite Feature #14797 not being completed yet.

#13 Updated by groente 2017-12-09 21:27:30

• Status changed from In Progress to Resolved

done