Howdy, I'm updating my old rig. Well, I'm trying to. I kept running out of space while compiling rust. I need to make /var larger. Thank goodness that is on a LVM. I have room left on that old drive so I wanted to just extend and then resize the ext4 file system, like I've done in the past I might add. I dug out my little cheat sheet and sure enough, lvextend -L <size to add> < lv name> and then resize file system. Simple enough. Should be, but it's not. This is some info, keep in mind, this is my old rig, not my new one.
root@fireball / # pvs PV VG Fmt Attr PSize PFree /dev/sda7 OS lvm2 a-- <124.46g 5.39g root@fireball / # vgs VG #PV #LV #SN Attr VSize VFree OS 1 3 0 wz--n- <124.46g 5.39g root@fireball / # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert swap OS -wi-ao---- 12.00g usr OS -wi-ao---- 39.06g var OS -wi-ao---- 68.00g root@fireball / # resize2fs /dev/mapper/OS-var resize2fs 1.47.2 (1-Jan-2025) open: Device or resource busy while opening /dev/mapper/OS-var root@fireball / # I checked other info on how to do this with searches. All report the same thing. Use lvextend to add to the size and then resize the file system. It also says to use resize2fs to do it. I even rebooted just to be sure something wasn't off somewhere. In the past, I've resized ext4 while mounted several times, especially when growing the file system and when encrypted I might add. Am I missing something? Has something changed since I did this several years ago on this rig? Some extra step that isn't well documented yet for search engines to find? Or have I slipped my old rig into a worm hole?? ROFL By the way, I added 15GBs I think. Old rig has the OS on a 160GB drive, that someone from this list donated I might add. Any thoughts? What's making this not work this time? Dale :-) :-) P. S. The only way I could work around this, uninstall Kicad and clean out distfiles, including for packages I have installed. O_O There is a next time tho.
