On Sunday, 11 May 2025 14:10:48 British Summer Time Dale wrote: > root@fireball / # lvscan > ACTIVE '/dev/home/home-lv' [<7.28 TiB] inherit > ACTIVE '/dev/backup/backup' [698.63 GiB] inherit > ACTIVE '/dev/OS/usr' [39.06 GiB] inherit > ACTIVE '/dev/OS/var' [68.00 GiB] inherit <== That's the path > ACTIVE '/dev/OS/swap' [12.00 GiB] inherit > root@fireball / # resize2fs /dev/OS/var > resize2fs 1.47.2 (1-Jan-2025) > open: Device or resource busy while opening /dev/OS/var > root@fireball / #
Hmm ... the fine manual of resize2fs command states upfront: "The resize2fs program will resize ext2, ext3, or ext4 file systems. It can be used to enlarge or shrink an unmounted file system located on device. If the file system is mounted, it can be used to expand the size of the mounted file system, assuming the kernel and the file system supports on- line resizing." So you should not need to unmount it - but I wonder if the LVM layer introduces some complexity here. :-/ > I think all those link to the same device node, usually dm-<some number> > tho. Still, I tried it anyway. Worst thing, same excuse for not > resizing the darn thing. :/ > > Am I going to have to boot other media and resize this thing???? Since /var/ is in use by the OS and you keep getting warnings about it being busy, I think you'll have to reboot with a LiveUSB to finish this job with var unmounted.
signature.asc
Description: This is a digitally signed message part.
