Ext3 users - Aug 2007 - ext3-fs error with RAID 5 Array.

Hi,

I have a Fedora core 4 machine (kernel-
2.6.11-1.1369_FC4smp) conneted to external DAS using
Ultra 320 SCSI controller card. The DAS is configured
as RAID 5 of 3.5 TB. I partitioned this array into two
partitions of size 1.9TB and 1.6 TB. These are
assigned to 2 different LUNS so that these two appear
as two partitions in the my Linux machine. 

I use this DAS for backup and after backing up for 30
hours i observe that partition gets remounted as
read-only with following error message in dmesg,

EXT3-fs error (device sdb1): ext3_add_entry: bad entry
in directory #2: directory entry across blocks -
offset=1080, inode=135216, rec_len=4132, name_len=25
Aborting journal on device sdb1.
ext3_abort called.
EXT3-fs error (device sdb1): ext3_journal_start_sb:
Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device sdb1) in start_transaction:
Journal has aborted
EXT3-fs error (device sdb1) in ext3_create: IO failure
EXT3-fs error (device sdb1): ext3_readdir: bad entry
in directory #2: directory entry across blocks -
offset=1080, inode=135216, rec_len=4132, name_len=25
EXT3-fs error (device sdb1): ext3_readdir: bad entry
in directory #2: directory entry across blocks -
offset=1080, inode=135216, rec_len=4132, name_len=25
EXT3-fs error (device sdb1): ext3_readdir: bad entry
in directory #2: directory entry across blocks -
offset=1080, inode=135216, rec_len=4132, name_len=25
EXT3-fs error (device sdb1): ext3_readdir: bad entry
in directory #2: directory entry across blocks -
offset=1080, inode=135216, rec_len=4132, name_len=25
EXT3-fs error (device sdb1): ext3_readdir: bad entry
in directory #2: directory entry across blocks -
offset=1080, inode=135216, rec_len=4132, name_len=25


Any suggestions on how to solve this problem?

Best regards and thanks in advance for your help,

Raghu



       
____________________________________________________________________________________
Building a website is a piece of cake. Yahoo! Small Business gives you all the
tools to get online.
http://smallbusiness.yahoo.com/webhosting

On Wed, 29 Aug 2007, Kannan Raghuprasath wrote:
> EXT3-fs error (device sdb1): ext3_add_entry: bad entry
> in directory #2: directory entry across blocks -
> offset=1080, inode=135216, rec_len=4132, name_len=25
> Aborting journal on device sdb1.
> ext3_abort called.
> EXT3-fs error (device sdb1): ext3_journal_start_sb:
> Detected aborted journal
Proably too late, but: are there any device-related errors in the log?
Have you checked the device for errors? (eg. a simple
dd if=/dev/sdb of=/dev/null should do).

If the device (and the cabling) is fine, did you try fsck.ext3 yet? If 
so, what does it say?

C.
-- 
BOFH excuse #261:

The Usenet news is out of date

Hi Kannan,

we had similar problems with ext3. After a month of searching for the
error we changed the mainboard of the server. The maiboard was to old to
work properly with the new areca raid controler we used.
Without heavy load the device was o.k.


Best regards, Jan

> Hi,
> 
> I have a Fedora core 4 machine (kernel-
> 2.6.11-1.1369_FC4smp) conneted to external DAS using
> Ultra 320 SCSI controller card. The DAS is configured
> as RAID 5 of 3.5 TB. I partitioned this array into two
> partitions of size 1.9TB and 1.6 TB. These are
> assigned to 2 different LUNS so that these two appear
> as two partitions in the my Linux machine. 
> 
> I use this DAS for backup and after backing up for 30
> hours i observe that partition gets remounted as
> read-only with following error message in dmesg,
> 
> EXT3-fs error (device sdb1): ext3_add_entry: bad entry
> in directory #2: directory entry across blocks -
> offset=1080, inode=135216, rec_len=4132, name_len=25
> Aborting journal on device sdb1.
> ext3_abort called.
> EXT3-fs error (device sdb1): ext3_journal_start_sb:
> Detected aborted journal
> Remounting filesystem read-only
> EXT3-fs error (device sdb1) in start_transaction:
> Journal has aborted
> EXT3-fs error (device sdb1) in ext3_create: IO failure
> EXT3-fs error (device sdb1): ext3_readdir: bad entry
> in directory #2: directory entry across blocks -
> offset=1080, inode=135216, rec_len=4132, name_len=25
> EXT3-fs error (device sdb1): ext3_readdir: bad entry
> in directory #2: directory entry across blocks -
> offset=1080, inode=135216, rec_len=4132, name_len=25
> EXT3-fs error (device sdb1): ext3_readdir: bad entry
> in directory #2: directory entry across blocks -
> offset=1080, inode=135216, rec_len=4132, name_len=25
> EXT3-fs error (device sdb1): ext3_readdir: bad entry
> in directory #2: directory entry across blocks -
> offset=1080, inode=135216, rec_len=4132, name_len=25
> EXT3-fs error (device sdb1): ext3_readdir: bad entry
> in directory #2: directory entry across blocks -
> offset=1080, inode=135216, rec_len=4132, name_len=25
> 
> 
> Any suggestions on how to solve this problem?
> 
> Best regards and thanks in advance for your help,
> 
> Raghu
> 
> 
> 
>        
>
____________________________________________________________________________________
> Building a website is a piece of cake. Yahoo! Small Business gives you all
the tools to get online.
> http://smallbusiness.yahoo.com/webhosting 
> 
> _______________________________________________
> Ext3-users mailing list
> Ext3-users at redhat.com
> https://www.redhat.com/mailman/listinfo/ext3-users

-- 
Jan Stobbe                              Netropol Digitale Systeme GmbH
jan.stobbe at netropol.de                  Stresemannstrasse 161
Tel: +49 40 284167-20                   D-22769 Hamburg/Germany
Fax: +49 40 284167-40                   http://www.netropol.de/

Registergericht: 			Gesch?ftsf?hrer:
Handelsregister Hamburg, HRB 75989	Jan Stobbe, Karl-Heinz Dellwo