Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Has anyone learned anything more about the drbd file corruption issues? It has started to become a big problem now. I have two different servers, different motherboards, both running scsi disks on an md0 device. I'm getting them both to go read-only. About every couple of days (and sometime multiple times a day) I'm getting this error. I'm using drbd version 0.7.17 on both. Might there be a fix in a later release? Server 1 ======== Centos 4.3 (2.6.9-34.0.1.ELsmp) Jul 8 11:16:34 nfs5 kernel: EXT3-fs error (device drbd0): ext3_readdir: bad entry in directory #9339548: rec_len is smaller than minimal - of fset=512, inode=3614863868, rec_len=0, name_len=0 Jul 8 11:16:34 nfs5 kernel: Aborting journal on device drbd0. Jul 8 11:16:34 nfs5 kernel: ext3_abort called. Jul 8 11:16:34 nfs5 kernel: EXT3-fs error (device drbd0): ext3_journal_start_sb: Detected aborted journal Jul 8 11:16:34 nfs5 kernel: Remounting filesystem read-only Server 2 ======== Fedora core 2 (2.6.10-2.3.legacy_FC2) Jul 6 11:33:10 nfs1 kernel: EXT3-fs error (device drbd0): ext3_readdir: bad entry in directory #770049: directory entry across blocks - offse t=0, inode=805306368, rec_len=28744, name_len=64 Jul 6 11:33:10 nfs1 kernel: Aborting journal on device drbd0. Jul 6 11:33:10 nfs1 kernel: ext3_abort called. Jul 6 11:33:10 nfs1 kernel: EXT3-fs error (device drbd0): ext3_journal_start_sb: Detected aborted journal Jul 6 11:33:10 nfs1 kernel: Remounting filesystem read-only Thanks, Brent