Red Hat Bugzilla – Bug 149850
attempt to access beyond end of device
Last modified: 2007-11-30 17:11:00 EST
Description of problem:
I was building OpenOffice.org from the CVS and I decided to check
used space (approximately about 10GB) via the 'du -s' command.
Few seconds later, aggressive disk access, I received lot of errors
from my desktop programs and build of OOo stops. The problem is in
Feb 28 09:00:30 echelon kernel: attempt to access beyond end of device
Feb 28 09:00:30 echelon kernel: hda6: rw=0, want=13075849984, limit=75778542
Feb 28 09:00:30 echelon kernel: EXT3-fs error (device hda6): ext3_readdir:
directory #3042557 contains a hole at offset 0
Feb 28 09:00:30 echelon kernel: Aborting journal on device hda6.
[ hundreds of similiar message ]
Version-Release number of selected component (if applicable):
Will try to reproduce tomorrow, when I'll backup everything
in my /home.
No data loss ...
Furnished upon request.
There's nothing to go on here. You appear to have bad data on the disk; fsck
logs would be useful. But unless it's reproducible, or you have additional
kernel logs, we can't tell if it's a hardware fault --- disk, cables, CPU or
memory; or a device driver, VM or filesystem problem.
memtest86 and a decent filesystem stresser such as "dt" would be good places to
start if you want to give the hardware a proper shakedown.
My laptop went through these stress tests before I installed FC,
all my computers are treated in this way.
I'll try to reproduce this tomorrow. If there will be no success,
I'll close this bug.
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
Closing as NOTABUG since there's still no indication whether this is hardware or
software as a root cause, and there has been no followup. Please reopen if you
can reproduce this with more information against a current kernel.