Les Mikesell wrote:
>
>>> Back to this problem again. I did a new mkfs.ext3 and ran more than
>>> a week before hitting this again:
>>>
>>> Mar 14 04:12:29 linbackup1 kernel: md3: rw=0, want=14439505280,
>>> limit=1465143808
>>> Mar 14 04:12:29 linbackup1 kernel: EXT3-fs error (device md3):
>>> ext3_readdir: directory #34079247 contains a hole at offset 0
>>> Mar 14 04:12:29 linbackup1 kernel: Aborting journal on device md3.
>>> Mar 14 04:12:29 linbackup1 kernel: md3: rw=0, want=5260961472,
>>> limit=1465143808
>>> Mar 14 04:12:29 linbackup1 kernel: EXT3-fs error (device md3):
>>> ext3_readdir: directory #34079247 contains a hole at offset 4096
>>>
>>> I don't see any hardware related errors, and the rest of the
>>> filesystems all seem fine, although this is the one that is busy.
>>
>> Is your memory ECC? If not then a memory problem can fly under the radar.
>
> dmidecode says single-bit ECC
Just to clear up this old thread, the problem did turn out to be memory
but it took most of a day's run of memtest86 to find it and even then it
only reported soft errors. After replacing the RAM everything has been
fine for several weeks.
--
Les Mikesell
lesmikesell at gmail.com