On Sunday, 11 May 2025 16:10:43 British Summer Time Dale wrote: > Michael wrote: > > I'm not the best person to advise on LVM, I just shared what I know, but I > > haven't used LVM in anger for a few years now. Hopefully someone with > > more > > hands on experience will chime in. > > Since the lv command worked, I don't think this is a LVM problem. That > part of the growth is there. It seems to be resize2fs that has the > problem. I just wonder, if I could do a file system check, would it > work then? Thing is, it to wants it unmounted. It makes me wonder if > there is something that needs to be fixed, even if it is minor and not a > actual data problem, but it isn't just saying the file system needs to > be fixed first. When I did my searches, most people had a part in the > output about a bad super block or that a super block wasn't found. Mine > doesn't have that tho. I'm not sure what difference that makes. > > I'll try to boot some media and do it I guess. Just not today. > > Dale > > :-) :-)
Last thing to mention just in case it applies this your case. You know you may be able to extend a LV and resize the underlying fs in one go? The command 'lvextend --resizefs -L +5G /dev/VG/LV' should do this in one go (according to the man page it will use fsadm to resize the fs).
signature.asc
Description: This is a digitally signed message part.
