Bug 150847
Summary: | "-D" in /fsckoptions cause reboot cycling until "fastboot" is used on boot command line | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Peter Bieringer <pb> |
Component: | e2fsprogs | Assignee: | Thomas Woerner <twoerner> |
Status: | CLOSED NOTABUG | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | notting, sct, srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-03-11 17:05:46 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Peter Bieringer
2005-03-11 10:46:12 UTC
Here an verbose execution of fsck: # fsck.ext3 -f -D /dev/md1; echo $? e2fsck 1.35 (28-Feb-2004) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 3A: Optimizing directories Pass 4: Checking reference counts Pass 5: Checking group summary information /: ***** FILE SYSTEM WAS MODIFIED ***** /: ***** REBOOT LINUX ***** /: 35138/513024 files (1.0% non-contiguous), 708739/1024112 blocks 3 It's a little bit strange, it looks like that using "-D" on the root partition results in rc=3, while using "-D" e.g. on the "/boot" partition results in rc=1: # fsck.ext3 -f -D /dev/md0; echo $? e2fsck 1.35 (28-Feb-2004) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 3A: Optimizing directories Pass 4: Checking reference counts Pass 5: Checking group summary information /boot: ***** FILE SYSTEM WAS MODIFIED ***** /boot: 59/26104 files (16.9% non-contiguous), 30629/104320 blocks 1 EXIT CODE The exit code returned by e2fsck is the sum of the following condi- tions: 0 - No errors 1 - File system errors corrected 2 - File system errors corrected, system should be rebooted initscripts is just following orders. The "-D" flag forces the htree information on-disk to be rebuilt unconditionally. That *always* modifies the filesystem. That *always* causes e2fsck to return non-zero. That will *always* require a reboot if you do it to the root filesystem. In short, everything is working just as you'd expect if you add options to /fsckoptions which require compulsory changes to the root filesystem. The answer is not to do this. :) To do this manually, I'd boot either to a rescue CD or to a readonly root mount (eg. boot with init=/bin/sh),force the fsck -D from there, and then reboot. |