Linux-kernel mailing list archive 1998-31,: Re: ext2 corruption. How to remove the result.

# Re: ext2 corruption. How to remove the result.

Theodore Y. Ts'o (tytso@MIT.EDU)
Wed, 5 Aug 1998 17:03:36 -0400

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Geert Uytterhoeven: "Re: 2.1.113 Mill I 8MB & scrollback :-("
- Previous message: Mike A. Harris: "Re: IDE drive data transfer rates, kernel optimization?"

Date: Wed, 05 Aug 1998 11:29:34 +0300
From: "Ville =?ISO-8859-1?Q?P=E4tsi" ?= <NOSPAMdrc@zoo-gate.fi>

s-----xrwx 1 65535 65535 4294967295 Jul 3 1969 Makefile.in

That file appeared during the time i realised my /ext drive was
corrupted. Apparently the cause for corruption was doing compilation,
rm and df at the same time on that drive.

That's bad; can you report on what your hardware was? This sort of
thing shouldn't be happening, and to date many of the problems where
chalked up to hardware problems or the DMA problem that a few people
where having.

Hmm... actually given the values 65535 and 429496729 (0xFFFF and
0xFFFFFFFF, respectively), my guess was this was a hardware problem that
scribbed all ones on a part of your inode table.

E2fsck fixed the drive but left this file there.

Oops. In 1.12 I fixed the problem for character and block devices
(which were the most commonly reported case), but I forgot to fix it for
Unix-domain socket files. I'll get this fixed in the next release.

In the meantime, you're going to have to fix this by using the debugfs's
clri command. Make sure you do this with the filesystem unmounted; run
the command "debugfs -w /dev/XXXX", then use the cd and ls commands to
find the appropriate file. You can them remove it using the clri
command; then quit debugfs and make sure you run e2fsck on the device
before you remount the drive.

Sorry for the inconvenience.

- Ted

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html

- Next message: Geert Uytterhoeven: "Re: 2.1.113 Mill I 8MB & scrollback :-("
- Previous message: Mike A. Harris: "Re: IDE drive data transfer rates, kernel optimization?"