[Technology] Resizing my encrypted, ext4 file system

I normally just upgrade my Linux distro from its semiannual release in place.  I keep my existing file system and just upgrade packages en masse.   I don't usually reformat and restore files from a backup.

For Fedora 17 last year, though, I wanted to upgrade all my file systems from the ext3 format to ext4.  It's "better".  You can do it in place, but there are attributes that won't apply to any old file system entries, only to new ones (new files that get added).  I could in theory have upgraded it in place, and then just copied files back and forth from another drive, but whatever.  Clean start.  I backed up all my personal files, and reformatted the whole disk as ext4, and moved it back.

Now, the disk setup was this.

  • 0.5GB boot partition (device: /dev/sda1, mount point: /boot)

  • 465GB volume group (device: /dev/sda2)

    • 4GB swap partition

    • 24GB ext4 root volume (mount point: /)
      This is where all the system files go, like programs.

    • 200GB LUKS ext4 volume (mount point: /home)
      This was my primary file system for personal files.  It's encrypted so that if someone steals my laptop, they won't be able to read my data. :)

    • 237GB ext4 volume (mount point: /home2)
      This was a secondary one.  I wasn't sure whether the LUKS encryption on /home would slow down IO-heavy activities, like managing media files.  I didn't mind having things like videos and music stored unencrypted.

Ultimately, though, I found /home2 was unnecessary.  /home was adequately fast for my media.  While I have a laptop, it's 7200RPM rather than 5400RPM, so that helps.  Thanks to my photography habit, I found /home getting almost full, only 1GB free!  I considered moving my music collection to /home2, but decided instead to try to get rid of /home2 and expand /home over that space.

I used system-config-lvm to delete /home2 and then used it to resize /home over top it.  However, that alone did not resize my file system to cover it.  Interestingly, gnome-disks reports the LUKS volume and ext4 file system as taking up the full space, but df reports the ext4 file system as taking up only 200GB.  Uh oh.

So, I read this tutorial on Ubuntu forums about resizing encrypted file systems, and found the one step I still needed to take.  Apparently, system-config-lvm won't really resize the ext4 file system, even though gnome-disks claims afterwards that it larger.  So, I just ran resize2fs on it.  I used mount to figure out which volume it was on (mine was /dev/mapper/luks-blah-blah-blah) and then ran resize2fs /dev/mapper/luks-blah-blah-blah, while it was even mounted (!).  Hooray for live resizing.  It worked well, and after a reboot still worked too.

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 emacs libgdata memory mozilla open source serialisation upgrade web development API Spain containers design evolution fedora 16 fedora 20 fedora 22 fedup file systems friends future glib gnome shell internet luks music performance phone photos php podman preupgrade tablet testing typescript yum #Microblog Network Manager adb apache art automation bash brno catastrophe css data loss debian debugging deja-dup disaster docker emusic errors ext4 facebook fedora 19 gee gir gitlab gitorious gmail gobject google talk google+ html libxml mail microsoft mtp mysql namespaces nautilus nextcloud owncloud picasaweb pitivi ptp python raspberry pi resizing rpm school selinux signal sms speech dispatcher systemd technology texting time management uoguelph usability video web design youtube #Tech Air Canada C Electron Element 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 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 cropping customisation dataloss dconf debug symbols design patterns desktop summit development discoverability distribution diy dnf documentation drm duplicity e-mail efficiency email english environment estate experimenting ext3 fedora 11 festival file formats firejail flac flatpak 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 ide identity instagram installation instant messaging integration intel interactivity introspection jabber java java 13 jobs kernel keyboard language language servers languages law learning lenovo letsencrypt libreoffice librpm life livecd liveusb login lsp macbook maintainership mariadb mario matrix memory leaks messaging mounting mouse 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 privacy productivity progress progressive web apps pumpkin pwa pyright quality recursion redhat refactoring repairs report rhythmbox sandboxes scheduling screenshots self-navigating car shell 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 video editing volunteering vpnc waf warm wayland weather web apps website wifi wiki wireless wishes work xinput xmpp xorg xpath
Powered by Blogger.