no fsck for unmounted filesystems

Reindl Harald h.reindl at thelounge.net
Mon Feb 16 16:10:43 UTC 2015


Am 16.02.2015 um 17:03 schrieb Eric Sandeen:
> On 2/16/15 10:00 AM, Reindl Harald wrote:
>> the corruption itself may come from https://bugzilla.redhat.com/show_bug.cgi?id=1192834 which is also really strange
>
> Let's continue the discussion in that bug, if this behavior is a result of the testcase in that bug

these are two different things, even without any corruption the result 
is the same - i have here 30 clones using the same /boot and even the 
ones with a clean FS don't allow unmount and fsck

the fact that you mostly can't unmount and/or fsck annoys me over years 
and on raid-devices it's neraly 100% so but that it also affects a ext2 
/boot partition seems to be recent "improvement" of that behavior

if you comment out the /boot entry in /etc/fstab fsck you can call fsck 
without any issue and i would strongly expect the same behavior after 
unmount since if the device really is in use unmount would fail



More information about the kernel mailing list