Ext3 users - Oct 2001 - possible ext3 bug?

hiya!

i'm currently running 2.4.12-ac1 w/o any further ext3 patches.

i've got a dir with some fairly big files (like 15mb/file) in it and while
sfv-checking these i got the following errors:

Oct 14 21:47:59 srck@trottelkunde attempt to access beyond end of device
Oct 14 21:47:59 srck@trottelkunde 16:42: rw=0, want=600889688, limit=12289725
Oct 14 21:47:59 srck@trottelkunde attempt to access beyond end of device
Oct 14 21:47:59 srck@trottelkunde 16:42: rw=0, want=600889688, limit=12289725
Oct 14 21:48:00 srck@trottelkunde attempt to access beyond end of device
Oct 14 21:48:00 srck@trottelkunde 16:42: rw=0, want=1526984940, limit=12289725
Oct 14 21:48:00 srck@trottelkunde attempt to access beyond end of device
Oct 14 21:48:00 srck@trottelkunde 16:42: rw=0, want=1526984940, limit=12289725
Oct 14 21:49:51 srck@trottelkunde attempt to access beyond end of device
Oct 14 21:49:51 srck@trottelkunde 16:42: rw=0, want=600889688, limit=12289725
Oct 14 21:49:51 srck@trottelkunde attempt to access beyond end of device
Oct 14 21:49:51 srck@trottelkunde 16:42: rw=0, want=600889688, limit=12289725
Oct 14 21:49:51 srck@trottelkunde attempt to access beyond end of device
Oct 14 21:49:51 srck@trottelkunde 16:42: rw=0, want=1526984940, limit=12289725
Oct 14 21:49:51 srck@trottelkunde attempt to access beyond end of device
Oct 14 21:49:51 srck@trottelkunde 16:42: rw=0, want=1526984940, limit=12289725

Some of the files reportet an input/output-error while accessing them.

after deleting the whole directory (which was very stupid, no chance for
debugging at all) i got the following errors:

Oct 14 21:50:50 srck@trottelkunde EXT3-fs error (device ide1(22,66)):
ext3_free_blocks: Freeing blocks not in datazone - block = 1223964245, count = 1
Oct 14 21:50:50 srck@trottelkunde EXT3-fs error (device ide1(22,66)):
ext3_free_blocks: Freeing blocks not in datazone - block = 59368495, count = 1
Oct 14 21:50:50 srck@trottelkunde EXT3-fs error (device ide1(22,66)):
ext3_free_blocks: Freeing blocks not in datazone - block = 2698791693, count = 1
Oct 14 21:50:50 srck@trottelkunde EXT3-fs error (device ide1(22,66)):
ext3_free_blocks: Freeing blocks not in datazone - block = 875055598, count = 1
Oct 14 21:50:50 srck@trottelkunde EXT3-fs error (device ide1(22,66)):
ext3_free_blocks: Freeing blocks not in datazone - block = 381746234, count = 1
Oct 14 21:50:50 srck@trottelkunde EXT3-fs error (device ide1(22,66)):
ext3_free_blocks: Freeing blocks not in datazone - block = 3876116832, count = 1

Imho this seems to be an ext3 bug because there where no further errors
regarding a disk-access problem

i have not the slightes clue on how to reproduce this error because when i
pushed the filesystem really hard (like copying files from the lan onto
the box while sfv-checking other files on the same drive) everything was
fine.

is this a known problem and/or is there anything i can do to debug this
problem? (unfortunately i haven't had jbd debugging in my kernel)

greetz michael

On Sun, Oct 14, 2001 at 10:11:06PM +0200, Michael Renner
wrote:
> hiya!
> 
> i'm currently running 2.4.12-ac1 w/o any further ext3 patches.
> 
> i've got a dir with some fairly big files (like 15mb/file) in it and
while
> sfv-checking these i got the following errors:
> 
> Oct 14 21:47:59 srck@trottelkunde attempt to access beyond end of device
> Oct 14 21:47:59 srck@trottelkunde 16:42: rw=0, want=600889688,
limit=12289725
> after deleting the whole directory (which was very stupid, no chance for
> debugging at all) i got the following errors:
> 
> Oct 14 21:50:50 srck@trottelkunde EXT3-fs error (device ide1(22,66)):
> ext3_free_blocks: Freeing blocks not in datazone - block = 1223964245,
count = 1
> 
> Imho this seems to be an ext3 bug because there where no further errors
> regarding a disk-access problem
What these errors all point to is that an indirect block (more
likely), or possibly part of an inode table, got corrupted.  *Why*
that happened is a different question; it could have been caused by a
kernel bug in the buffer/page cache code, or it could have been caused
by hardware problem (i.e., disk block written to the wrong place,
perhaps caused by bad SCSI/IDE cable, or an actual hard drive failure
causing garbage to be written or read), or it could be caused by an
ext3 error.

The real trick is figuring out how to reproduce the problem.  I
haven't other reports of this happening on recent kernels, so this
isn't a known problem.

The first thing to do is to unmount the filesystem and run e2fsck -f
on the device to make sure there aren't other parts of the filesystem
which had gotten corrupted somehow.  After that, the main trick will
be to see if you can push the filesystem hard and see if you can
reproduce the problem, and see if we can find a pattern there.
Another thing to try would be to drop back to an older kernel that's a
bit more trustworthy.  I'd suggest 2.4.9 plus ext3-0.9.6 --- that
version has been very stable for me and others.  So if it's still
happening there, that might be a hint that it might be a potential
hardware problem.

						- Ted