Hey, I've a problem with an ext3 filesystem and don't know how to fix it or find the failure :( The Hardware: Tyan mainboard, AMD Athlon CPU, ARECA ARC-1120 RaidController Raid5 with 400GB Seagate HD's, 756 MB Ram, other harddisks for system, network and avm isdn controller. Couse of the filesystem problems I run memtest and found one bad memory module which I replaced yet. The System: Kernel 2.6.19.1 Debian Gnu/Linux 3.0 with e2fsck 1.37 (21-Mar-2005) I've setup one ext3 partition with around 1.4 TB on the raid5 volume. The first four month we run the raid without any problems. About two month ago I noticed that the filesystem was remounted ro. A filesystem check found a lot of errors. After a filesystem check and a new mount of the partition and copy data on the partition you get the errors again. Also with Kernel 2.6.17.3 I got this problems. A raid volume check with the areca command line tools doesn't find any errors. Errors from dmesg / kernel.log: EXT3-fs: mounted filesystem with ordered data mode. init_special_inode: bogus i_mode (113301) init_special_inode: bogus i_mode (170101) init_special_inode: bogus i_mode (115140) init_special_inode: bogus i_mode (117302) init_special_inode: bogus i_mode (111700) EXT3-fs error (device sda1): ext3_readdir: bad entry in directory #143278260: rec_len % 4 != 0 - offset=0, inode=1857588108, rec_len=8466, name_len=34 Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode (111501) Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode (113301) Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode (170101) Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode (115140) Dec 22 14:25:19 datahaven kernel: EXT3-fs error (device sda1): ext3_readdir: bad entry in directory #150569204: rec_len %% 4 != 0 - offset=0, inode=3038782558, rec_len=28425, name_len=75 Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode (111501) Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode (113301) Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode (170101) Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode (115140) Dec 22 06:31:54 datahaven kernel: EXT3-fs error (device sda1): ext3_readdir: bad entry in directory #20351025: directory entry across blocks - offset=0, inode=20353857, rec_len=13600, name_len=1 Dec 22 06:31:55 datahaven kernel: EXT3-fs error (device sda1): ext3_readdir: bad entry in directory #20417957: rec_len %% 4 != 0 - offset=96, inode=20437734, rec_len=27291, name_len=6 Dec 22 06:31:59 datahaven kernel: EXT3-fs error (device sda1): ext3_readdir: bad entry in directory #21007912: directory entry across blocks - offset=296, inode=21005643, rec_len=32184, name_len=25 Dec 22 06:32:24 datahaven kernel: init_special_inode: bogus i_mode (114764) Dec 22 06:32:29 datahaven kernel: EXT3-fs error (device sda1): ext3_readdir: bad entry in directory #21839877: rec_len %% 4 != 0 - offset=24, inode=21839878, rec_len=22019, name_len=7 Dec 22 06:32:30 datahaven kernel: init_special_inode: bogus i_mode (55314) Dec 22 06:32:34 datahaven kernel: init_special_inode: bogus i_mode (117302) Dec 22 06:32:36 datahaven kernel: EXT3-fs error (device sda1): ext3_readdir: bad entry in directory #22448122: rec_len %% 4 != 0 - offset=24, inode=22417991, rec_len=28145, name_len=8 Any hints how to solve this problem or to isolate the failure ? Best regards and thanks in advance for your help, Jan
The machine is used mainly as fileserver with samba and netatalk. this should be the only server applications which are placing data on the drive. For testing I disabled netatalk yet. I can do an fsck and the filesystem is fine after that. I do a remount and copy witch cp a few GB, do an unmount and the fsck will have errors again in the target directory of the copied files. In this test there are no samba or netatalk users connected. When I copied files with a client connected with samba I got the same errors. Jan> What is this machine being used for, primarily? What types of local > applications/binaries are placing data on the drive? > > - Kevin > > Jan wrote: >> Hey, >> >> I've a problem with an ext3 filesystem and don't know how to fix it or >> find the failure :( >> >> The Hardware: >> >> Tyan mainboard, AMD Athlon CPU, ARECA ARC-1120 RaidController Raid5 with >> 400GB Seagate HD's, 756 MB Ram, other harddisks for system, network and >> avm isdn controller. >> >> Couse of the filesystem problems I run memtest and found one bad memory >> module which I replaced yet. >> >> The System: >> >> Kernel 2.6.19.1 >> Debian Gnu/Linux 3.0 with e2fsck 1.37 (21-Mar-2005) >> >> >> I've setup one ext3 partition with around 1.4 TB on the raid5 volume. >> The first four month we run the raid without any problems. About two >> month ago I noticed that the filesystem was remounted ro. A filesystem >> check found a lot of errors. After a filesystem check and a new mount of >> the partition and copy data on the partition you get the errors again. >> Also with Kernel 2.6.17.3 I got this problems. A raid volume check with >> the areca command line tools doesn't find any errors. >> >> Errors from dmesg / kernel.log: >> >> >> EXT3-fs: mounted filesystem with ordered data mode. >> init_special_inode: bogus i_mode (113301) >> init_special_inode: bogus i_mode (170101) >> init_special_inode: bogus i_mode (115140) >> init_special_inode: bogus i_mode (117302) >> init_special_inode: bogus i_mode (111700) >> EXT3-fs error (device sda1): ext3_readdir: bad entry in directory >> #143278260: rec_len % 4 != 0 - offset=0, inode=1857588108, rec_len=8466, >> name_len=34 >> >> Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode >> (111501) >> Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode >> (113301) >> Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode >> (170101) >> Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode >> (115140) >> Dec 22 14:25:19 datahaven kernel: EXT3-fs error (device sda1): >> ext3_readdir: bad entry in directory #150569204: rec_len %% 4 != 0 - >> offset=0, inode=3038782558, >> rec_len=28425, name_len=75 >> >> >> Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode >> (111501) >> Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode >> (113301) >> Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode >> (170101) >> Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode >> (115140) >> Dec 22 06:31:54 datahaven kernel: EXT3-fs error (device sda1): >> ext3_readdir: bad entry in directory #20351025: directory entry across >> blocks - offset=0, inode=20353857, rec_len=13600, name_len=1 >> Dec 22 06:31:55 datahaven kernel: EXT3-fs error (device sda1): >> ext3_readdir: bad entry in directory #20417957: rec_len %% 4 != 0 - >> offset=96, inode=20437734, rec_len=27291, name_len=6 >> Dec 22 06:31:59 datahaven kernel: EXT3-fs error (device sda1): >> ext3_readdir: bad entry in directory #21007912: directory entry across >> blocks - offset=296, inode=21005643, rec_len=32184, name_len=25 >> Dec 22 06:32:24 datahaven kernel: init_special_inode: bogus i_mode >> (114764) >> Dec 22 06:32:29 datahaven kernel: EXT3-fs error (device sda1): >> ext3_readdir: bad entry in directory #21839877: rec_len %% 4 != 0 - >> offset=24, inode=21839878, rec_len=22019, name_len=7 >> Dec 22 06:32:30 datahaven kernel: init_special_inode: bogus i_mode >> (55314) >> Dec 22 06:32:34 datahaven kernel: init_special_inode: bogus i_mode >> (117302) >> Dec 22 06:32:36 datahaven kernel: EXT3-fs error (device sda1): >> ext3_readdir: bad entry in directory #22448122: rec_len %% 4 != 0 - >> offset=24, inode=22417991, rec_len=28145, name_len=8 >> >> Any hints how to solve this problem or to isolate the failure ? >> >> Best regards and thanks in advance for your help, >> >> Jan >> >> _______________________________________________ >> Ext3-users mailing list >> Ext3-users at redhat.com >> https://www.redhat.com/mailman/listinfo/ext3-users >
I did some more test. First I split the raid in two partitions and run
mkfs.ext3 -c for badblocks.
then I tried to copy data on the first partion. after a while i got
errors (around 130gb were on th partition) :
attempt to access beyond end of device
sda1: rw=0, want=3151373440, limit=1464846304
attempt to access beyond end of device
sda1: rw=0, want=2853870672, limit=1464846304
attempt to access beyond end of device
sda1: rw=0, want=1751501064, limit=1464846304
attempt to access beyond end of device
sda1: rw=0, want=2783268072, limit=1464846304
attempt to access beyond end of device
sda1: rw=0, want=2835511344, limit=1464846304
attempt to access beyond end of device
so I googled and found this thread:
http://lkml.org/lkml/2006/10/5/353
I tried the script from there on my partition (whith around 130 gb on it):
dd bs=1M count=200 if=/dev/zero of=test0
while :; do
echo "cp 0-1"; cp test0 test1 || break
echo "cp 1-2"; cp test1 test2 || break
echo "cp 2-3"; cp test2 test3 || break
echo "cp 3-4"; cp test3 test4 || break
echo "od 0" ; od test0 || break
echo "rm 1"; rm test1 || break
echo "rm 2"; rm test2 || break
echo "rm 3"; rm test3 || break
echo "rm 4"; rm test4 || break
done
The script was running not more then 10 minutes and I got:
EXT3-fs error (device sda1) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs error (device sda1) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs error (device sda1) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs error (device sda1) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda1): ext3_free_blocks: Freeing blocks in system
zones - Block = 327680, count = 1
EXT3-fs error (device sda1) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda1): ext3_free_blocks: Freeing blocks in system
zones - Block = 327680, count = 1
EXT3-fs error (device sda1) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda1): ext3_free_blocks: Freeing blocks in system
zones - Block = 327680, count = 1
Then I create a new fs on the partition without any data on it and
got the same errors while running ths script.
On internal ide harddisk softwareraid-1 but partiton size only 4 gb no
problem with the test script.
The testscript with 10mb file is now running for several hours without
any problems on the sata raid partition.
New Partion with size of 340GB, testscript with 200mb files. Errors:
ock = 65536, count = 1
EXT3-fs error (device sda2) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda2): ext3_free_blocks: Freeing blocks in system
zones - Block = 65536, count = 1
EXT3-fs error (device sda2) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda2): ext3_free_blocks: Freeing blocks in system
zones - Block = 65536, count = 1
EXT3-fs error (device sda2) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda2): ext3_free_blocks: Freeing blocks in system
zones - Block = 65536, count = 1
EXT3-fs error (device sda2) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs error (device sda2) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs error (device sda2) in ext3_reserve_inode_write: Readonly filesystem
EXT3-fs error (device sda2) in ext3_truncate: IO failure
EXT3-fs error (device sda2) in ext3_reserve_inode_write: Readonly filesystem
EXT3-fs error (device sda2) in ext3_orphan_del: Readonly filesystem
EXT3-fs error (device sda2) in ext3_reserve_inode_write: Readonly filesystem
EXT3-fs error (device sda2) in ext3_delete_inode: IO failure
And with 180 GB Partition:
ree_blocks: Freeing blocks in system zones - Block = 262144, count = 1
EXT3-fs error (device sda3) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system
zones - Block = 262144, count = 1
EXT3-fs error (device sda3) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system
zones - Block = 262144, count = 1
EXT3-fs error (device sda3) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs error (device sda3) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Readonly filesystem
EXT3-fs error (device sda3) in ext3_truncate: IO failure
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Readonly filesystem
EXT3-fs error (device sda3) in ext3_orphan_del: Readonly filesystem
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Readonly filesystem
EXT3-fs error (device sda3) in ext3_delete_inode: IO failure
Strange ? I still don't know how to solve the problem.
Regards, Jan
> Hey,
>
> I've a problem with an ext3 filesystem and don't know how to fix it
or
> find the failure :(
>
> The Hardware:
>
> Tyan mainboard, AMD Athlon CPU, ARECA ARC-1120 RaidController Raid5 with
> 400GB Seagate HD's, 756 MB Ram, other harddisks for system, network and
> avm isdn controller.
>
> Couse of the filesystem problems I run memtest and found one bad memory
> module which I replaced yet.
>
> The System:
>
> Kernel 2.6.19.1
> Debian Gnu/Linux 3.0 with e2fsck 1.37 (21-Mar-2005)
>
>
> I've setup one ext3 partition with around 1.4 TB on the raid5 volume.
> The first four month we run the raid without any problems. About two
> month ago I noticed that the filesystem was remounted ro. A filesystem
> check found a lot of errors. After a filesystem check and a new mount of
> the partition and copy data on the partition you get the errors again.
> Also with Kernel 2.6.17.3 I got this problems. A raid volume check with
> the areca command line tools doesn't find any errors.
>
> Errors from dmesg / kernel.log:
>
>
> EXT3-fs: mounted filesystem with ordered data mode.
> init_special_inode: bogus i_mode (113301)
> init_special_inode: bogus i_mode (170101)
> init_special_inode: bogus i_mode (115140)
> init_special_inode: bogus i_mode (117302)
> init_special_inode: bogus i_mode (111700)
> EXT3-fs error (device sda1): ext3_readdir: bad entry in directory
> #143278260: rec_len % 4 != 0 - offset=0, inode=1857588108, rec_len=8466,
> name_len=34
>
> Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode (111501)
> Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode (113301)
> Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode (170101)
> Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode (115140)
> Dec 22 14:25:19 datahaven kernel: EXT3-fs error (device sda1):
> ext3_readdir: bad entry in directory #150569204: rec_len %% 4 != 0 -
> offset=0, inode=3038782558,
> rec_len=28425, name_len=75
>
>
> Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode (111501)
> Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode (113301)
> Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode (170101)
> Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode (115140)
> Dec 22 06:31:54 datahaven kernel: EXT3-fs error (device sda1):
> ext3_readdir: bad entry in directory #20351025: directory entry across
> blocks - offset=0, inode=20353857, rec_len=13600, name_len=1
> Dec 22 06:31:55 datahaven kernel: EXT3-fs error (device sda1):
> ext3_readdir: bad entry in directory #20417957: rec_len %% 4 != 0 -
> offset=96, inode=20437734, rec_len=27291, name_len=6
> Dec 22 06:31:59 datahaven kernel: EXT3-fs error (device sda1):
> ext3_readdir: bad entry in directory #21007912: directory entry across
> blocks - offset=296, inode=21005643, rec_len=32184, name_len=25
> Dec 22 06:32:24 datahaven kernel: init_special_inode: bogus i_mode (114764)
> Dec 22 06:32:29 datahaven kernel: EXT3-fs error (device sda1):
> ext3_readdir: bad entry in directory #21839877: rec_len %% 4 != 0 -
> offset=24, inode=21839878, rec_len=22019, name_len=7
> Dec 22 06:32:30 datahaven kernel: init_special_inode: bogus i_mode (55314)
> Dec 22 06:32:34 datahaven kernel: init_special_inode: bogus i_mode (117302)
> Dec 22 06:32:36 datahaven kernel: EXT3-fs error (device sda1):
> ext3_readdir: bad entry in directory #22448122: rec_len %% 4 != 0 -
> offset=24, inode=22417991, rec_len=28145, name_len=8
>
> Any hints how to solve this problem or to isolate the failure ?
>
> Best regards and thanks in advance for your help,
>
> Jan
>
> _______________________________________________
> 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/
I did some more test. First I split the raid in two partitions and run
mkfs.ext3 -c for badblocks.
then I tried to copy data on the first partion. after a while i got
errors (around 130gb were on th partition) :
attempt to access beyond end of device
sda1: rw=0, want=3151373440, limit=1464846304
attempt to access beyond end of device
sda1: rw=0, want=2853870672, limit=1464846304
attempt to access beyond end of device
sda1: rw=0, want=1751501064, limit=1464846304
attempt to access beyond end of device
sda1: rw=0, want=2783268072, limit=1464846304
attempt to access beyond end of device
sda1: rw=0, want=2835511344, limit=1464846304
attempt to access beyond end of device
so I googled and found this thread:
http://lkml.org/lkml/2006/10/5/353
I tried the script from there on my partition (whith around 130 gb on it):
dd bs=1M count=200 if=/dev/zero of=test0
while :; do
echo "cp 0-1"; cp test0 test1 || break
echo "cp 1-2"; cp test1 test2 || break
echo "cp 2-3"; cp test2 test3 || break
echo "cp 3-4"; cp test3 test4 || break
echo "od 0" ; od test0 || break
echo "rm 1"; rm test1 || break
echo "rm 2"; rm test2 || break
echo "rm 3"; rm test3 || break
echo "rm 4"; rm test4 || break
done
The script was running not more then 10 minutes and I got:
EXT3-fs error (device sda1) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs error (device sda1) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs error (device sda1) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs error (device sda1) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda1): ext3_free_blocks: Freeing blocks in system
zones - Block = 327680, count = 1
EXT3-fs error (device sda1) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda1): ext3_free_blocks: Freeing blocks in system
zones - Block = 327680, count = 1
EXT3-fs error (device sda1) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda1): ext3_free_blocks: Freeing blocks in system
zones - Block = 327680, count = 1
Then I create a new fs on the partition without any data on it and
got the same errors while running ths script.
On internal ide harddisk softwareraid-1 but partiton size only 4 gb no
problem with the test script.
The testscript with 10mb file is now running for several hours without
any problems on the sata raid partition.
New Partion with size of 340GB, testscript with 200mb files. Errors:
ock = 65536, count = 1
EXT3-fs error (device sda2) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda2): ext3_free_blocks: Freeing blocks in system
zones - Block = 65536, count = 1
EXT3-fs error (device sda2) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda2): ext3_free_blocks: Freeing blocks in system
zones - Block = 65536, count = 1
EXT3-fs error (device sda2) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda2): ext3_free_blocks: Freeing blocks in system
zones - Block = 65536, count = 1
EXT3-fs error (device sda2) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs error (device sda2) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs error (device sda2) in ext3_reserve_inode_write: Readonly filesystem
EXT3-fs error (device sda2) in ext3_truncate: IO failure
EXT3-fs error (device sda2) in ext3_reserve_inode_write: Readonly filesystem
EXT3-fs error (device sda2) in ext3_orphan_del: Readonly filesystem
EXT3-fs error (device sda2) in ext3_reserve_inode_write: Readonly filesystem
EXT3-fs error (device sda2) in ext3_delete_inode: IO failure
And with 180 GB Partition:
ree_blocks: Freeing blocks in system zones - Block = 262144, count = 1
EXT3-fs error (device sda3) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system
zones - Block = 262144, count = 1
EXT3-fs error (device sda3) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs unexpected failure: !jh->b_committed_data;
inconsistent data on disk
EXT3-fs error (device sda3): ext3_free_blocks: Freeing blocks in system
zones - Block = 262144, count = 1
EXT3-fs error (device sda3) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs error (device sda3) in ext3_free_blocks_sb: Readonly filesystem
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Readonly filesystem
EXT3-fs error (device sda3) in ext3_truncate: IO failure
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Readonly filesystem
EXT3-fs error (device sda3) in ext3_orphan_del: Readonly filesystem
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Readonly filesystem
EXT3-fs error (device sda3) in ext3_delete_inode: IO failure
Strange ? I still don't know how to solve the problem.
Regards, Jan
> Hey,
>
> I've a problem with an ext3 filesystem and don't know how to fix it
or
> find the failure :(
>
> The Hardware:
>
> Tyan mainboard, AMD Athlon CPU, ARECA ARC-1120 RaidController Raid5 with
> 400GB Seagate HD's, 756 MB Ram, other harddisks for system, network and
> avm isdn controller.
>
> Couse of the filesystem problems I run memtest and found one bad memory
> module which I replaced yet.
>
> The System:
>
> Kernel 2.6.19.1
> Debian Gnu/Linux 3.0 with e2fsck 1.37 (21-Mar-2005)
>
>
> I've setup one ext3 partition with around 1.4 TB on the raid5 volume.
> The first four month we run the raid without any problems. About two
> month ago I noticed that the filesystem was remounted ro. A filesystem
> check found a lot of errors. After a filesystem check and a new mount of
> the partition and copy data on the partition you get the errors again.
> Also with Kernel 2.6.17.3 I got this problems. A raid volume check with
> the areca command line tools doesn't find any errors.
>
> Errors from dmesg / kernel.log:
>
>
> EXT3-fs: mounted filesystem with ordered data mode.
> init_special_inode: bogus i_mode (113301)
> init_special_inode: bogus i_mode (170101)
> init_special_inode: bogus i_mode (115140)
> init_special_inode: bogus i_mode (117302)
> init_special_inode: bogus i_mode (111700)
> EXT3-fs error (device sda1): ext3_readdir: bad entry in directory
> #143278260: rec_len % 4 != 0 - offset=0, inode=1857588108, rec_len=8466,
> name_len=34
>
> Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode (111501)
> Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode (113301)
> Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode (170101)
> Dec 22 14:25:03 datahaven kernel: init_special_inode: bogus i_mode (115140)
> Dec 22 14:25:19 datahaven kernel: EXT3-fs error (device sda1):
> ext3_readdir: bad entry in directory #150569204: rec_len %% 4 != 0 -
> offset=0, inode=3038782558,
> rec_len=28425, name_len=75
>
>
> Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode (111501)
> Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode (113301)
> Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode (170101)
> Dec 22 06:31:43 datahaven kernel: init_special_inode: bogus i_mode (115140)
> Dec 22 06:31:54 datahaven kernel: EXT3-fs error (device sda1):
> ext3_readdir: bad entry in directory #20351025: directory entry across
> blocks - offset=0, inode=20353857, rec_len=13600, name_len=1
> Dec 22 06:31:55 datahaven kernel: EXT3-fs error (device sda1):
> ext3_readdir: bad entry in directory #20417957: rec_len %% 4 != 0 -
> offset=96, inode=20437734, rec_len=27291, name_len=6
> Dec 22 06:31:59 datahaven kernel: EXT3-fs error (device sda1):
> ext3_readdir: bad entry in directory #21007912: directory entry across
> blocks - offset=296, inode=21005643, rec_len=32184, name_len=25
> Dec 22 06:32:24 datahaven kernel: init_special_inode: bogus i_mode (114764)
> Dec 22 06:32:29 datahaven kernel: EXT3-fs error (device sda1):
> ext3_readdir: bad entry in directory #21839877: rec_len %% 4 != 0 -
> offset=24, inode=21839878, rec_len=22019, name_len=7
> Dec 22 06:32:30 datahaven kernel: init_special_inode: bogus i_mode (55314)
> Dec 22 06:32:34 datahaven kernel: init_special_inode: bogus i_mode (117302)
> Dec 22 06:32:36 datahaven kernel: EXT3-fs error (device sda1):
> ext3_readdir: bad entry in directory #22448122: rec_len %% 4 != 0 -
> offset=24, inode=22417991, rec_len=28145, name_len=8
>
> Any hints how to solve this problem or to isolate the failure ?
>
> Best regards and thanks in advance for your help,
>
> Jan
>
> _______________________________________________
> Ext3-users mailing list
> Ext3-users at redhat.com
> https://www.redhat.com/mailman/listinfo/ext3-users
[please reply on-list, so that all can comment] On Fri, 29 Dec 2006, ..:::BeOS Mr. X:::.. wrote:> Hey how would I check my syslog on BeOS ? I have dd. Is there I way I can use > that to calculate my hard drive MB/s read speed ?um, I wasn't aware that ext3fs is supported on BeOS? Otherwise it's a bit off topic, no? 1) syslog: if BeOS has no syslog, how do you know what's wrong with the system? 2) if you have GNU/dd, you can send a USR1 to the dd process to see the progress and a MB/s value. still, I don't see the relation to ext3 or even with the OP's problem. cheers, Christian. -- BOFH excuse #328: Fiber optics caused gas main leak
[please reply on-list, so that everybody can comment] On Wed, 3 Jan 2007, Jan wrote:> thanks, I already moved all data from this device. I did run this test > and got no errors yet. I also did dd directly on the device. No error in > syslog....so, the device is fine then?> Now I tried jfs on one device and did my test with 200 mb files > - no errros....and JFS is fine too.> I installed a 400GB sata disk with a sata card and tried > this with ext3 and my test script and got also no errors....and now ext3 on this device is alsofine? So, that means the problem you had is not reproducible, no?> there are problems with the disks or the cable the controller should > notice this ? Perhaps I should ask at areca ?your 2nd post[0] indeed looked a lot like hardware errors. So yes, if these errors persist/are reproducible, you're probably better off asking the maintainer or the sata folks for known issues... Christian. [0]https://www.redhat.com/archives/ext3-users/2006-December/msg00025.html -- BOFH excuse #125: we just switched to Sprint.