[Technology] Resizing my encrypted /home partition

I just wrote a post about why I reinstalled Fedora 22: because I wanted root to be on the SSD, and I needed to purge a lot of old installed software anyway. :P  And how that led to trying out the open source b43 wireless driver.

This is more interesting than my wireless problem. 
Because I no longer needed a / partition on my HDD, I wanted to extend
my home partition.  It isn't as dead-simple as back a decade ago.  Back
then, I would use fdisk to delete and recreate partitions and resize2fs
to resize the file system.

Now I have layers upon
layers of useful abstraction.  I'm calling each something potentially
inaccurate, and the tool I needed in brackets. (Those with wildcards
match multiple tools with the same beginning.)


  • ext4 file system (resize2fs)

  • Logical volume (lv*)

  • Volume group (vg*)

  • Physical volume (pv*)

  • partitions (fdisk)


At first I was almost a little annoyed
at the apparent complexity, but it's actually straight forward.  My
drive is still divided into multiple partitions in a partition table. 
(/dev/sda1, /dev/sda2, /dev/sda3, etc; I have 8 for various reasons).

volumes seem to correspond to those partitions, but mostly just the
useful storage ones (e.g. I don't have them for EFI or swap
partitions).  pvcreate lets me define them.

physical volumes are collected into volume groups.  For example,
/dev/sdb1 (my intended root) might be a part of "pantaloons-fedora-ssd"
(if I named my machine pantaloons), and /dev/sda2 and /dev/sda4 might
both be part of "pantaloons-fedora-hdd" (two large areas for my /home
that I'd like to combine later, but which are currently separated by some other, annoying partition).

volume group kind of looks like a single contiguous (!) entity (despite
being a collection of disparate physical partitions).  Then, I can
define logical volumes atop the volume groups.

I can
have both / and swap as separate logical volumes atop
"pantaloons-fedora-ssd" (talk about cramped - maybe I don't want to
hibernate after all), and have a single logical volume for /home atop
the "pantaloons-fedora-hdd" volume group.

This is where things get a little trippy though.  Where does the encryption happen?

For my root file system, it looks like it happens like:

partition /dev/sdb1 > LUKS > physical volume > EXT4 file system

For my home file system, it looks like this:

/dev/sda2,/dev/sda4 > two physical volumes > 1 volume group > 1
logical volume > LUKS > EXT4 file system

disks/dev/sdb (SSD)/dev/sda (HDD)

The home partition and its LUKS (using
cryptsetup/dm-crypt) was originally configured through whichever tool
Fedora provided years ago (preupgrade? fedup? anaconda?), while the
configuration on my SSD was what was recommended in F22.

Basically, I had to (with steps that actually increase space emboldened):

  • define a new partition in the partition table, 

  • define a new Physical Volume (PV) over top it, 

  • extend my Volume Group (VG) to include the new Physical Volume

  • unmount the file system I was going to extend, 

  • close its LUKS setup

  • extend the file system's Logical Volume (LV) overtop the new space in the Volume Group

  • reopen the LUKS setup

  • resize the LUKS setup (are these two out of order? hope not!), and

  • resize the Ext4 partition

A bit more detail, here are the steps I used on my system (from
my bash_history, probably missing some steps; I think I also used
or pvremove to remove LVs and PVs related to the old home partition, oh

  • # cfdisk, to delete the old root on the /dev/sda4 partition and recreate it

  • # pvcreate /dev/sda4 (creates a physical volume)

  • # vgextend pantaloons-fedora-hdd /dev/sda4 (add the PV into the VG increasing its overall size)

  • make sure /home isn't mounted

  • # fsck.ext4 -C 0 -f /dev/mapper/luks-BAR (let's make sure the inodes are fine on our file system before messing with it)

  • # cryptsetup luksClose luks-BAR (close LUKS while we change the underlying LV)

  • # lvextend -L +61G /dev/pantaloons-fedora-hdd/home (increase the size of our LV within the VG)

  • # lvextend -L +242M /dev/pantaloons-fedora-hdd/home (catch a little more space)

  • there is probably a way to just extend it to the full space available, maybe read the man page

  • # cryptsetup luksOpen /dev/pantaloons-fedora-home luks-BAR

  • # cryptsetup resize luks-BAR (resizing the LUKS setup)

  • # fsck.ext4 -C 0 -f /dev/mapper/luks-BAR (for paranoia maybe)

  • # resize2fs /dev/mapper/luks-BAR (finally, let's resize our Ext4 file system)

Sadly, I can't cite the sources I pieced some parts together from, because I did this form a live USB key which is supposed to keep history as persistent storage but the browser history was empty when I tried checking it later :S  However, man pages were also useful.

Keine Kommentare:

Kommentar veröffentlichen

Dieses Blog durchsuchen


#Technology #GNOME gnome gxml fedora bugs linux vala google #General firefox security gsoc GUADEC android bug xml fedora 18 javascript libxml2 programming web blogger encryption fedora 17 gdom git libgdata memory mozilla open source serialisation upgrade web development API Spain design emacs evolution fedora 16 fedora 20 fedora 22 fedup file systems friends future glib gnome shell internet luks music performance phone photos preupgrade tablet testing yum #Microblog Network Manager adb art automation bash brno catastrophe containers css data loss deja-dup disaster emusic errors ext4 facebook fedora 19 gee gir gitlab gitorious gmail gobject google talk google+ html libxml mail microsoft mtp namespaces nautilus php picasaweb podman ptp resizing rpm school selinux sms speech dispatcher systemd technology texting time management typescript uoguelph usability video web design youtube #Tech Air Canada C Empathy Europe GError GNOME 3 GNOME Files Go Google Play Music Grimes IRC Mac OS X Mario Kart Memento Nintendo Nintendo Switch PEAP Selenium Splatoon UI VPN Xiki accessibility advertising ai albums anaconda anonymity apache apple ask asus eee top automake autonomous automobiles b43 backup battery berlin bit rot broadcom browsers browsing canada canadian english cars chrome clarity comments communication compiler complaints computer computers configuration console constructive criticism cron customisation dataloss dconf debian debug symbols debugging design patterns desktop summit development discoverability distribution diy dnf docker documentation drm duplicity e-mail efficiency email english environment estate experimenting ext3 fedora 11 festival file formats firejail flac forgottotagit freedom friendship fuse galaxy nexus galton gay rights gdb german germany gimp gio gjs gnome software gnome-control-center google assistant google calendar google chrome google hangouts google reader gqe graphviz growth gtest gtg gtk gvfs gvfs metadata hard drive hard drives hardware help hp humour identity instagram installation instant messaging integration intel interactivity introspection jabber java java 13 jobs kernel keyboard language languages law learning lenovo letsencrypt libreoffice librpm life livecd liveusb login macbook maintainership mario memory leaks messaging mounting mouse mysql netflix new zealand node nodelist numix obama oci ogg oggenc oh the humanity open open standards openoffice optimisation org-mode organisation package management packagekit paint shedding parallelism pdo perl pipelight pitivi privacy productivity progress progressive web apps pumpkin pwa python quality recursion redhat refactoring repairs report rhythmbox sandboxes scheduling screenshots self-navigating car shell signal sleep smartphones software software engineering speed sql ssd synergy tabs test tests themes thesis tracker travel triumf turtles tv tweak twist typing university update usb user experience valadoc volunteering vpnc waf warm wayland weather web apps website wifi wiki wireless wishes work xinput xmpp xorg xpath
Powered by Blogger.