|Product:||[Retired] Red Hat Linux||Reporter:||margarita|
|Component:||e2fsprogs||Assignee:||Florian La Roche <laroche>|
|Status:||CLOSED NOTABUG||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2000-02-16 13:55:12 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description margarita 1999-09-18 19:22:27 UTC
On bootup sometimes fsck cannot fix everything it drops the user into some kind of maint mode and reports to the user that fsck needs to be run without flags. fsck should always give a very stromg warning that it is dangerous to run on a mounted file system if that attempt is made. fsck called me a probable "bonehead" after it had already made some changes. I laughed, but wished it had stated it earlier and informed this "bonehead" how to fsck the root filesystem without mounting it. Fortunately no damage was done and I have a sense of humor about the incident.
Comment 1 Bernhard Rosenkraenzer 2000-02-16 13:55:59 UTC
fsck'ing a read-only mounted file system (like the root filesystem in the emergency mode you're referring to) can't hurt.