Hi all, i'm having problem with ext3 on Suse 8.2: EXT3-fs error (device sd(8,17)): ext3_readdir: bad entry in directory #2654270: rec_len % 4 != 0 - offset=13, inode=4093651072, rec_len=527, name_len=2 this server has a replica of data contained on another server which is running RH7.3 and gives no problem on the ext3. The FileSystem affected is mounted via NFS and backed up with cpbk. Many other FS backed-up the same way don't give any problem. has anybody got any hints on this. I've been searching the web but can't find a solution to it. thanks allot for your help --------------------------------------- Gianluca Francavilla System Administrator ION Trading S.r.l. Via San Martino, 52 - 56125 Pisa Tel. : 0039 050 220371 Email : g.francavilla@iontrading.com ---------------------------------------
On Mondayen den 4 October 2004 11.02, Gianluca Francavilla wrote:
Hi all,
i'm having problem with ext3 on Suse 8.2:
EXT3-fs error (device sd(8,17)): ext3_readdir: bad entry in directory #2654270: rec_len % 4 != 0 - offset=13, inode=4093651072, rec_len=527, name_len=2
this server has a replica of data contained on another server which is running RH7.3 and gives no problem on the ext3. The FileSystem affected is mounted via NFS and backed up with cpbk. Many other FS backed-up the same way don't give any problem.
has anybody got any hints on this. I've been searching the web but can't find a solution to it.
Well, the error message tells you that some directory has a bad entry, the entry length isn't a multiple of 4 (a requirement in ext2/3). Are you sure this isn't a problem on the original server? Try, on the suse box, doing find /mountpoint_of_ext3 -inum 4093651072 That should tell you which directory has the problem. Then look at that directory on the original server and see if you don't get the same error message. In any case, the first try towards fixing it should be running fsck.ext3 on the partition
participants (2)
-
Anders Johansson
-
Gianluca Francavilla