Messages in this thread | | | From | "Sergei Viznyuk" <> | Subject | Re: Fw: fsck fails to detect uncleanly unmounted fs on 2.1.7x | Date | Fri, 16 Jan 1998 21:08:33 -0500 |
| |
>At 8:04 PM -0500 1/15/98, Sergei Viznyuk wrote: >>>On Tue, Jan 13, 1998 at 09:45:12PM -0500, Sergei Viznyuk wrote: >>> >>>> The subject says it. >>>> I found out that if I pull the plug on my linux box >>>> without doing shutdown first, the subsequent >>>> fsck -a upon bootup does not run the >>>> fs check, as it used to with earlier kernels >>>Not a kernel problem. This message is printed by your startup scripts >>>when it detects some magic file (usually /fastboot or /etc/fastboot) during >>>the boot process. The file should be deleted during startup and >>>recreated during a clean shutdown. As it looks the file is never >>>being removed on your box. >>> >>> Ralf >> >>Please give me some credit. I didn't really quote >>the message from fsck (e2fsck). >>It just says the filesystem is clean plus some usual numbers. >>And believe me, IT IS a kernel problem. >>If I boot 2.1.57 kernel, fsck runs OK and does >>detect uncleanly unmounted filesystem. >>In 2.1.7x kernels it does not, no matter >>how hard I crash the system. >>Someone screwd up something in ext2 code >>in recent kernels. > >Where x >= 2. I saw that with 2.1.72 repeatedly now (after a panic() while >mounting the root fs the fsck was skipped afterwards).
Cool.
2.1.77 (and all earlier 2.1.7x kernels I tried) have the same bug.
Just how long would it take for the ones who screwd up ext2 code to notice it ?
Cordially, Serge
| |