Re: FW: Corrupted filesystem

Trevor Johnson (
Wed, 20 May 1998 15:32:09 -0700 (PDT)

> We experienced a system crash and the fsck upon reboot failed with
> the following message:
> Directory Inode 5, block 0, offset 0: directory corrupted
> Salvage <y>?

By default, Linux uses write caching, meaning that data and directory
information isn't written immediately to disk. If you run /sbin/update,
then that information will be written out periodically. If you use the
"sync" option to mount (this is the default in *BSD), then the write
caching will be disabled. This can be much slower, but if your system
crashes, or you have users accustomed to DOS who abruptly power it off,
there will be minimal loss of data.

The folks here would definitely be interested in just why and how your
system crashed. The Documentation/oops-tracing.txt file that comes with
the Linux source might be relevant if you want to make a report.

As for recovering your files, I've had success with LDE
( but
having a backup is much better. Good luck.
Trevor Johnson

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to