Re: 2.2.12 file system corruption?

Stephen C. Tweedie (sct@redhat.com)
Tue, 9 Nov 1999 16:24:32 +0000 (GMT)


Hi,

On Mon, 8 Nov 1999 08:51:09 +0100 (CET), peter karlsson <pk@mds.mdh.se>
said:

> <root> /usr/bin# ls -l pwgen
> s---rwxr-x 21 21 49214 65548 Jan 2 1970 pwgen=
> <root> /usr/bin# lsattr pwgen
> lsattr: Innapropriate "ioctl" för device While reading flags on pwgen

e2fsck from e2fsprogs-1.17 _should_ be able to remove that file. The bug

> Ferrari: 63626/257000 files (5.0% non-contiguous), 772771/1024001 blocks
> Segmentation fault

is now apparently known and Ted is working on a fix.

However, Ted, in looking through the e2fsck source I did notice a couple
of oddities: a regular device or socket inode with the correct zeroes in
the inode direct blocks but with the immutable flag set will _not_ be
touched by e2fsck. We really do need a way to clear the immutable flag
on such inodes.

> Nov 7 06:47:04 dat95pkn kernel: swap_duplicate: entry 00000030,
> nonexistent swap file

That sort of pte corruption usually (>99 times out of 100) means
hardware memory corruption.

--Stephen

-
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.tux.org/lkml/