Bug in init.d/fsck causes severe filesystem corruption
Elvis Pranskevichus
Mon Mar 16 02:04:06 2009
Hi Roy,
One of the servers I manage died today as a consequence of the openrc allowing
the system to boot with filesystem errors uncorrected.
Here's a relevant part from /etc/init.d/fsck:
4) if [ "${RC_UNAME}" = "Linux" ]; then
ewend 1 "Fileystem errors left uncorrected"
return 0
else
ewend 1 "Filesystems repaired, but reboot needed"
_reboot
fi;;
I'm wondering why "Filesystem errors left uncorrected" is somehow ok?
This is what actually happened:
* Checking local filesystems ...
root contains a file system with errors, check forced.
root: Deleted inode 84 has zero dtime. FIXED.
root: Inodes that were part of a corrupted orphan linked list found.
root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
* Fileystem errors left uncorrected
[ !! ]
* Remounting root filesystem read/write...
[ ok ]
The result is a completely messed up fs.
I'm using openrc-0.4.3 and baselayout-2.0.0 on gentoo.
Thanks!
Elvis
Archive administrator: postmaster@marples.name