Messages in this thread |  | | Date | Thu, 02 Jan 1997 08:06:20 -0500 (EST) | From | "Mark H. Wood" <> | Subject | Re: Serious ext2fs problem |
| |
On Tue, 31 Dec 1996, Chris Adams wrote:
> Once upon a time, Stephen C. Tweedie wrote > > In article <199612311454.IAA18638@sh1.ro.com> Chris Adams > > <cadams@ro.com> writes: > > > In my case, the filesystem error in questions is > > > > > EXT2-fs error (device 08:31): ext2_new_block: Free blocks count > > > corrupted for block group 546 > > > > > This is on a 10 gig RAID 0 news spool (on a DPT 3224). The system is > > > running Linux 2.0.27 + the noatime patch and INN 1.4unoff4. When I run > > > e2fsck (1.04 that comes with RedHat 4.0 and 1.06 from tsx-11), no errors > > > are reported. > > > > Bad SCSI bus. > > > > This is almost certainly bad hardware, either the disk or the SCSI > > bus. I'd check your cables and try pushing the bus speed down to 5 > > MHz. I have seen almost identical symptoms on a news server myself, > > and it turned out to be hardware. The reason you see the free blocks > > count message is just that this is one place that the kernel is in a > > position to do some self-checking; single-bit errors on the SCSI bus > > in other blocks won't normally be detected. > > Once the errors start happening, they keep happening at the same place > over and over again. However, if I stop INN, umount the drive, mount > the drive, and start INN, everything is happy (I had it giving me the > above error twice everytime I tried to tell INN to "go"). Since I > umounted the drive and remounted it, it has been running just fine for > ~24 hours. That doesn't seem like hardware to me.
Sure does to me. Bad memory, that is. Once a cached block gets corrupted it stays put and stays corrupted.
Mark H. Wood, Lead System Programmer MWOOD@INDYVAX.IUPUI.EDU Those who will not learn from history are doomed to reimplement it.
|  |