Bug 55773 - reiserfs causes forced fsck failure at boot
Summary: reiserfs causes forced fsck failure at boot
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: reiserfs-utils
Version: 7.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Garzik
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-11-06 14:11 UTC by Andrew Pam
Modified: 2013-07-03 02:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-04-22 15:50:45 UTC
Embargoed:


Attachments (Terms of Use)

Description Andrew Pam 2001-11-06 14:11:12 UTC
Description of Problem:
On an unclean shutdown, rc.sysinit asks if you want to force an fsck.
Unfortunately it implements this by calling fsck against each mountpoint
with the "-f" option which is not implemented in fsck.reiserfs and returns
with an error code, resulting in rc.sysinit incorrectly concluding that the
fsck failed and forcing a reboot.

Version-Release number of selected component (if applicable):
initscripts-6.40-1, reiserfs-utils-3.x.0j-2

How Reproducible:
Every time.

Steps to Reproduce:
1. On my system, all filesystems are journalled - a mix of ext3 and reiserfs
2. Shut down without removing /.autofsck
3. When asked to press "f" to force an fsck, do so.

Actual Results:
Any non-reiserfs fscks will proceed normally, but at the first
reiserfs mountpoint it will fail to run fsck (since "-f" is not a valid
option to fsck.reiserfs) and you will have to reboot again without having
actually run the fsck.  You will have to start without the reiserfs
partitions mounted and fsck them manually if desired.

Expected Results:
fsck.reiserfs should have been run without the non-existent "-f" option.
Alternatively, "-f" should be added to reiserfsck as an ignored option.

Comment 1 Bill Nottingham 2001-11-06 15:57:48 UTC
'"-f" should be added to reiserfsck as an ignored option' sounds like the
correct solution to me.

Comment 2 Tomas Mraz 2005-04-22 15:50:45 UTC
This is already fixed.



Note You need to log in before you can comment on or make changes to this bug.