Re: 2.2.18/ext2: special file corruption?

2001-02-26 Thread Ulrich Windl
On 26 Feb 2001, at 10:48, Andreas Dilger wrote: > Ulrich Windl writes: > > I had an interesting effect: Due to NVdriver I had a lot of system > > freezes, and I had to reboot. Using e2fsck 1.19a (SuSE 7.1) I got the > > message that one specific "Special (device/socket/fifo) inode .. has > >

Re: 2.2.18/ext2: special file corruption?

2001-02-26 Thread Walter Hofmann
Ulrich Windl schrieb am Montag, den 26. Februar 2001: > I had an interesting effect: Due to NVdriver I had a lot of system > freezes, and I had to reboot. Using e2fsck 1.19a (SuSE 7.1) I got the > message that one specific "Special (device/socket/fifo) inode .. has > non-zero size. FIXED." I

Re: 2.2.18/ext2: special file corruption?

2001-02-26 Thread Andreas Dilger
Ulrich Windl writes: > I had an interesting effect: Due to NVdriver I had a lot of system > freezes, and I had to reboot. Using e2fsck 1.19a (SuSE 7.1) I got the > message that one specific "Special (device/socket/fifo) inode .. has > non-zero size. FIXED." > > Interestingly I got the message

2.2.18/ext2: special file corruption?

2001-02-26 Thread Ulrich Windl
Hi, I had an interesting effect: Due to NVdriver I had a lot of system freezes, and I had to reboot. Using e2fsck 1.19a (SuSE 7.1) I got the message that one specific "Special (device/socket/fifo) inode .. has non-zero size. FIXED." Interestingly I got the message for every reboot. So either

2.2.18/ext2: special file corruption?

2001-02-26 Thread Ulrich Windl
Hi, I had an interesting effect: Due to NVdriver I had a lot of system freezes, and I had to reboot. Using e2fsck 1.19a (SuSE 7.1) I got the message that one specific "Special (device/socket/fifo) inode .. has non-zero size. FIXED." Interestingly I got the message for every reboot. So either

Re: 2.2.18/ext2: special file corruption?

2001-02-26 Thread Andreas Dilger
Ulrich Windl writes: I had an interesting effect: Due to NVdriver I had a lot of system freezes, and I had to reboot. Using e2fsck 1.19a (SuSE 7.1) I got the message that one specific "Special (device/socket/fifo) inode .. has non-zero size. FIXED." Interestingly I got the message for

Re: 2.2.18/ext2: special file corruption?

2001-02-26 Thread Walter Hofmann
Ulrich Windl schrieb am Montag, den 26. Februar 2001: I had an interesting effect: Due to NVdriver I had a lot of system freezes, and I had to reboot. Using e2fsck 1.19a (SuSE 7.1) I got the message that one specific "Special (device/socket/fifo) inode .. has non-zero size. FIXED." I see

Re: 2.2.18/ext2: special file corruption?

2001-02-26 Thread Ulrich Windl
On 26 Feb 2001, at 10:48, Andreas Dilger wrote: Ulrich Windl writes: I had an interesting effect: Due to NVdriver I had a lot of system freezes, and I had to reboot. Using e2fsck 1.19a (SuSE 7.1) I got the message that one specific "Special (device/socket/fifo) inode .. has non-zero