Skip to contentSkip to conversation

persistent 2.6.[13] filesystem corruptions

DISCUSSION Marc Singer 1 participant 1 message Mar 7, 2004

lore
Share & tools
lore
#0 lore raw

My system has 2 CPUs as well as four SCSI disks in a RAID5 configuration. On top of this, there are several LVM/device-mapper volumes with ext3 filesystems on them. The system was running this way for almost a year on the 2.4 kernel. I switched to 2.6.1 when it was available. Periodically, I login in the morning to find that several of the LVM volumes were mounted RO. Never did I find out why though I suspected that there was a FS corruption and the kernel was remounting the volumes RO. Remounting them RW usually worked, but ext3 filesystems often had errors requiring an fsck.

I switched to 2.6.3 to see if the problems would go away. No luck. In fact, it's worse because the corruptions are more frequent. On one occasion, the system froze.

This message, too, is new:

EXT3-fs error (device dm-5): ext3_readdir: bad entry in directory #11: directory entry across blocks - offset=0, inode=808464430, rec_len=12336, name_len=48 Remounting filesystem read-only

Any ideas what might be the culprit or where to look?