Bug #12469

Resize ISO history and Tor Browser archive LVs

Added by intrigeri 2017-04-22 09:15:06 . Updated 2017-04-22 10:45:34 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Infrastructure
Target version:
Tails_3.0~rc1
Start date:
2017-04-22
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

This requires pvmove’ing LV data around so we don’t store on SSDs data that’s barely ever accessed, and on HDs data that is used more often, both for ISO history and Tor Browser archive + isobuilder1 data that was put on the wrong PV, all this taking into account our storage plans (Feature #11806).

Subtasks

Related issues

Related to Tails - Feature #11806: Update server storage planning needs for at least 2017 Resolved 2016-09-19

History

#1 Updated by intrigeri 2017-04-22 09:25:08

  • % Done changed from 0 to 50

Done, here’s essentially what I did:

sudo pvmove --name isobuilder1-data /dev/mapper/md2_crypt /dev/mapper/md1_crypt
sudo pvmove --name isos-www /dev/mapper/md2_crypt /dev/mapper/md1_crypt
sudo pvmove --name isos /dev/mapper/md1_crypt /dev/mapper/md2_crypt
sudo pvmove --name torbrowser-archive /dev/mapper/md1_crypt /dev/mapper/md2_crypt
sudo pvmove --name torbrowser-archive-www /dev/mapper/md2_crypt /dev/mapper/md3_crypt
sudo lvextend -L 105G /dev/lizard/isos /dev/mapper/md2_crypt
sudo lvextend -L 105G /dev/lizard/isos-www /dev/mapper/md1_crypt
sudo lvextend -L  85G /dev/lizard/torbrowser-archive /dev/mapper/md2_crypt
sudo lvextend -L  85G /dev/lizard/torbrowser-archive-www /dev/mapper/md3_crypt
virsh shutdown www
virsh shutdown puppet-git
sudo e2fsck -f /dev/lizard/isos
sudo e2fsck -f /dev/lizard/isos-www
sudo e2fsck -f /dev/lizard/torbrowser-archive
sudo e2fsck -f /dev/lizard/torbrowser-archive-www
sudo resize2fs /dev/lizard/isos
sudo resize2fs /dev/lizard/isos-www
sudo resize2fs /dev/lizard/torbrowser-archive
sudo resize2fs /dev/lizard/torbrowser-archive-www
virsh start www
virsh start puppet-git

#2 Updated by intrigeri 2017-04-22 09:26:21

  • related to Feature #11806: Update server storage planning needs for at least 2017 added

#3 Updated by intrigeri 2017-04-22 09:26:40

  • Subject changed from Resize ISO history LVs to Resize ISO history and Tor Browser archive LVs

#4 Updated by intrigeri 2017-04-22 09:31:21

Rationale: we don’t have enough room on the HDs to store both copies of ISO history + Tor Browser archive; the copies that are attached to www.lizard are accessed much more often than the copies that are attached to puppet-git.lizard, so I’ve stored the former on SSDs and the later on HDs. Everything else is on SSDs except rsync and Jenkins data volumes.

#5 Updated by intrigeri 2017-04-22 10:45:34

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 50 to 100

Monitoring confirms it’s fixed.