Dear all, First of all, I'm very sorry to post such a vague question. I've been working this it for months now, but the ext3 errors keep reoccurring every once in a while. That is, every week or sometimes once a month. The errors I get in such a situation: > May 20 09:13:14 infinity kernel: attempt to access beyond end of device > May 20 09:13:14 infinity kernel: loop0: rw=0, want=15629775440, limit=4404019200 > May 20 09:13:14 infinity kernel: attempt to access beyond end of device > May 20 09:13:14 infinity kernel: loop0: rw=0, want=13075964688, limit=4404019200 > May 20 09:13:14 infinity kernel: attempt to access beyond end of device > May 20 09:13:14 infinity kernel: loop0: rw=0, want=15354014352, limit=4404019200 > (...) > and a little bit later: > May 20 09:15:07 infinity kernel: EXT3-fs error (device loop0): ext3_free_blocks: Freeing blocks not in datazone - block = 1953721929, count = 1 > May 20 09:15:07 infinity kernel: Remounting filesystem read-only > May 20 09:15:07 infinity kernel: EXT3-fs error (device loop0): ext3_free_blocks: Freeing blocks not in datazone - block = 1634495585, count = 1 > May 20 09:15:07 infinity kernel: EXT3-fs error (device loop0): ext3_free_blocks_sb: bit already cleared for block 543517044 > May 20 09:15:07 infinity kernel: EXT3-fs error (device loop0): ext3_free_blocks: Freeing blocks not in datazone - block = 1919251793, count = 1 > (...) > After running e2fsck everything is fine again for a week or a little longer... The situation is not really trivial: I'm importing block devices from several other machines using ATA over Ethernet (AoE). These block devices are combined in a set of RAID5 arrays, each of them a physical volume for LVM. Inside one large LVM volume group there exists a cryptoloop encrypted logical volume, of which the 'plain' version is accessible via /dev/loop0. As you can see, there are a lot of possible failure points, I don't expect you to identify those for me. I already performed thorough tests on all servers (from memtest to I/O stressing to networking) and another point is: this configuration did work flawlessly for about two years! What I would like to know: what are the possible underlying causes for the "attempt to access beyond en of device" error? Does anyone see any meaning in the block (?) numbers mentioned in my syslog? I would really like to hear from you, this problem is really causing me headaches! Regards, Bas -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
