From Bugzilla Helper: User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.2-2 i686) Description of problem: if on root partition is a reiserfs filesystem at boot the operating system always want to check the filesystem How reproducible: Always Steps to Reproduce: 1.halt 2.boot 3. Actual Results: At this sequence from the rc.sysinit the system always stops and asks if I want to perform a fsck if [ -z "$fastboot" -a "$ROOTFSTYPE" != "nfs" ]; then STRING=$"Checking root filesystem" echo $STRING initlog -c "fsck -T -a $fsckoptions /" rc=$? Additional info:
Doesn't the reiserfs fsck Do The Right Thing if it's unmounted cleanly? Assigning to reiserfs-utils.
It doesn't do the right thing because reiserfs fsck is ultimately broken (which is one of the reasons we aren't supporting it on root filesystems). -T isn't implemented at all (will fix), -a is supposed to enter a "do nothing mode" (and doesn't work). Looking into it.
ReiserFS doesn't require fsck utility, because it provides meta-data journalling. /sbin/reiserfsck is to repair fs corrupted due to internal kernel error of disk IO error, it's not a substitute for the traditional fsck and requires interaction with user most of the time. Proper way to fix this is either modify rc scripts or symlink /sbin/fsck.reiserfs to /bin/true.
Just as Nikita says, Reiser FS is not to be checked 'automatically' by the utility, so it's better to put 0 0 at the 5th and 6th fields in /etc/fstab for any Reiser Filesystem you have.
Any chance this fix will be making it into initscripts? As Nikita said, linking /sbin/fsck.reiserfs to /bin/true is one fix, other other is to fix /etc/rc.sysinit with the patch I will be attaching.
Created attachment 26092 [details] Patch to /etc/rc.d/rc.sysinit to avoid running fsck on reiserfs partitions
Assigning back to initscripts - I don't think fixing reiserfsck would be such a good idea (would break compatibility with everyone else, and doing it right would mean rewriting reiserfs ;) )
I object to the general idea of reiserfsck being handled differently than other filesystems. If it's not meant to be run generally, don't put the binary there with that name.
Closing out bugs on older, no longer supported releases. Apologies for any lack of response.