Ext3 users - Dec 2001 - EXT3-fs error..bad entry in directory

Hello ext3-users,

We have a RH71 machine running 2.4.16 kernel with e2fsprogs 1.25.
I noticed many of these errors in our logs.

EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory
#884828: directory entry across blocks - offset=0, inode=404600689,
rec_len=23080, name_len=59

EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory
#966714: rec_len % 4 != 0 - offset=0, inode=607908378, rec_len=18495,
name_len=70

EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory
#884829: directory entry across blocks - offset=0, inode=202413069,
rec_len=16652, name_len=11


I am seeing many lines much like these, I don't really know what this
error means. The inode values reported to not match the inodes on the
disk.

Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/sda1            11206656  219569 10987087    2% /zdata

all the EXT3-fs errors have an inode= value thats greater than the total
number of inodes on this disk.

We have been running EXT3 fs for sometime now, and recently upgraded
kernels from 2.4.10-ac11 to 2.4.16

sda1 is a RAID5 hardware array (DPT PM1554U2).

Can anyone make out what these errors mean?

-- 
-----------------------------------------------------
 Jessie Bryan
 e - jbryan@netlojix.com
 w - www.netlojix.com
-----------------------------------------------------

>We have a RH71 machine running 2.4.16 kernel with e2fsprogs 1.25.
>I noticed many of these errors in our logs.
>
>EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory
>#884828: directory entry across blocks - offset=0, inode=404600689,
>rec_len=23080, name_len=59
I've seen this kind of corruption on ext2 as well.

We run a 2.2.19 kernel with 3Ware Escalade RAID cards (running RAID 10),
no ext3 (just plain ext2) and get exactly this kind of corruption.

Our sda file systems get outrageous inode numbers for the errors.  When I
decode the numbers and look at them as ASCII, I often see parts of words.

Something is amiss with the SCSI disk code, I think.  I don't think
it's an ext3 problem.

-- 
-IAN!  Ian! D. Allen   Ottawa, Ontario, Canada   idallen@ncf.ca
       Home Page on the Ottawa FreeNet: http://www.ncf.ca/~aa610/
       College professor at: http://www.algonquincollege.com/~alleni/
       Board Member, TeleCommunities CANADA  http://www.tc.ca/