On 5/11/25 11:36 AM, Jay Faulkner wrote:
Hey Dale, couple of comments:
- LVM should not impact the resizing of the FS at all. I'm assuming
the 68GB you see for /dev/OS/var is the new size in the lvscan output?
If so, you should be ready to resize. If not, your LVM is not quite
ready yet.
- Are you sure you're using ext2/3/4 as the FS? Use lsblk to check. If
yes, another thing to try might be remounting the fs as read only
during the action: `mount -oremount,rw /var`
Good luck,
Jay
On 5/11/2025 7:39 AM, Dale wrote:
open: Device or resource busy while opening /dev/OS/var
I know this is old now but after the recent FUBAR, I had to expand this
file system even if it meant moving to another hard drive with larger
partitions etc. I tried again to resize the file system and it still
failed. I ended up booting rescue media, Ventoy with SysRescue on it,
and doing a fsck and then resizing from it. It did the fsck and resize
with no complaints at all. It worked just like it should.
As I mentioned before, I've resized file systems like that before while
they were not only mounted but even while copying files to or from
them. I still have no idea why it no longer works on that system. I
used it on my main rig not long ago with no problems. Again, not only
mounted but files being actively accessed.
I'm clueless on the reason for this but I got it done. That's the update.
Dale
:-) :-)
