Linux-kernel mailing list archive 1997-11,: Filesystem corruption with 2.0.32

# Filesystem corruption with 2.0.32

Jochen Heuer (jogi@planetzork.ping.de)
Sun, 23 Nov 1997 17:48:34 +0100

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Krzysztof G. Baranowski: "working kdebug"
- Previous message: Matthias Urlichs: "Re: glibc"
- Next in thread: Jeff Wiegley: "Re: Filesystem corruption with 2.0.32"
- Reply: Jeff Wiegley: "Re: Filesystem corruption with 2.0.32"

Hello everybody,

I'm experiencing some problems with filesystem corruption under
2.0.32 because I could not compile anything anymore. Having a
little look I found out that some files got *strange* permissions.

These are the permissions of some files and directories I found:

b--xrw-r-t 1 26988 25376 10, 59 Nov 6 2030 /usr/include/i386/syscall.h
br-srwSr-T 1 15730 9760 115, 97 Nov 18 2031 /usr/include/langinfo.h

I did a manual e2fsck -f on /dev/hda3 and I got plenty of
error messages. Stupid as I am I did not write them down.

The only thing I remember are some *bad mode for something* error.

I'm using kernel-2.0.32 with the foof-patch by Hans Lermen,
e2fsprogs-1.10.
Some informations on the affected drive:

ide: i82371 PIIX (Triton) on PCI bus 0 function 57
ide0: BM-DMA at 0xf000-0xf007
hda: WDC AC21600H, 1549MB w/128kB Cache, CHS=787/64/63, DMA
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14

There are no messages in any logfile. If I can give you some further
informations, please let me know.

Btw. I'm running a server with 2*P133 without corruption although
it's using an internal adaptec-2940uw.

Regards,

Jogi

    --

    Well, yeah ... I suppose there's no point in getting greedy, is there?

        << Calvin & Hobbes >>

- Next message: Krzysztof G. Baranowski: "working kdebug"
- Previous message: Matthias Urlichs: "Re: glibc"
- Next in thread: Jeff Wiegley: "Re: Filesystem corruption with 2.0.32"
- Reply: Jeff Wiegley: "Re: Filesystem corruption with 2.0.32"