> On Tue, 16 Jun 1998 13:15:42 -0400 (EDT), you wrote:
> >
> >And I think __everybody__ has such problems with versions above 2.1.102
> >(or thereabouts), but they don't notice it because a complete fsck isn't
> >done if the file-system has been dismounted proberly.
> >
> >To check, boot with init=/bin/bash.
> >
> >Then fsck -f /
>
>
> Confirmed - I tried this with 2.1.106-ac2 and I got filesystem errors, after
> cleanly shutting down the system. I believe this should not happen under any
> circumstances? I have never aborted a filesystem check if one was forced.
>
> Ganesh
> --
Thanks for the confirmation. I think there is a "small" problem that
will lead to "creeping" file-system corruption. It may be very hard to
find, so in the meantime, one could 'force' a complete fsck upon bootup
so problems don't exponentiate.
Cheers,
Dick Johnson
***** FILE SYSTEM MODIFIED *****
Penguin : Linux version 2.1.105 on an i586 machine (66.15 BogoMips).
Warning : It's hard to remain at the trailing edge of technology.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu