<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Hi All,<o:p></o:p> I m a novice developer of Linux applications. Recently I faced a file system corruption. (I guess)<o:p></o:p> I have a Kernel 2.4.7-10 with ext3 file system in compact flash. The system was up for 3 months and was running with average load conditions.<o:p></o:p> One fine day, it just started sending kernel messages on the serial console. The message was like this.<o:p></o:p> <o:p> </o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unab<o:p></o:p> le to read inode block - inode=20089, block=81926<o:p></o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block<o:p></o:p> - inode=20090, block=81926<o:p></o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block<o:p></o:p> - inode=20091, block=81926<o:p></o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block<o:p></o:p> - inode=20092, block=81926<o:p></o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block<o:p></o:p> - inode=20093, block=81926<o:p></o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block<o:p></o:p> - inode=20094, block=81926<o:p></o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block<o:p></o:p> - inode=20095, block=81926<o:p></o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block<o:p></o:p> - inode=20096, block=81926<o:p></o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block<o:p></o:p> - inode=20097, block=81927<o:p></o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block<o:p></o:p> - inode=20098, block=81927<o:p></o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block<o:p></o:p> - inode=20099, block=81927<o:p></o:p> Assertion failure in do_get_write_access() at transaction.c:606: "!(((jh2bh(jh))<o:p></o:p> ->b_state & (1UL << BH_Lock)) != 0)"<o:p></o:p> invalid operand: 0000<o:p></o:p> CPU: 0<o:p></o:p> EIP: 0010:[<d080e9e5>]<o:p></o:p> EFLAGS: 00010286<o:p></o:p> eax: 00000021 ebx: c171ce94 ecx: 00000001 edx: 0015991c<o:p></o:p> esi: c171ce00 edi: c788cdc0 ebp: cb5f4690 esp: cf581bf0<o:p></o:p> ds: 0018 es: 0018 ss: 0018<o:p></o:p> Process syslogd (pid: 608, stackpage=cf581000)<o:p></o:p> Stack: d0816990 0000025e 00000000 00000000 c171ce00 cf641820 c171ce94 c171ce00<o:p></o:p> c788cdc0 cb5f4690 d080edb5 c788cdc0 cb5f4690 00000000 00000000 000001ae<o:p></o:p> cfc86400 cfa670e0 d081a0cb c788cdc0 cfa67140 cf581c60 c1448088 cfa66800<o:p></o:p> Call Trace: [<d0816990>] [<d080edb5>] [<d081a0cb>] [<c018526c>] [<d081c049>]<o:p></o:p> [<d081c33d>] [<d081c1d0>] [<d081c990>] [<d080f3de>] [<d081ec95>] [<d081ed1a>]<o:p></o:p> <o:p> </o:p> [<d081caac>] [<c0133283>] [<d0813ebb>] [<d080e276>] [<c01339cd>] [<d081ca48>]<o:p></o:p> <o:p> </o:p> [<d081cfa6>] [<d081ca48>] [<c01265c8>] [<d081aa7b>] [<c0130ec9>] [<d081aa5c>]<o:p></o:p> <o:p> </o:p> [<d080f777>] [<d081ab0f>] [<c0130fe1>] [<c0106dd3>]<o:p></o:p> <o:p> </o:p> Code: 0f 0b 5b 5e 8b 54 24 24 f6 42 10 04 bb e2 ff ff ff b8 01 00<o:p></o:p> hda: read_intr: status=0x51 { DriveReady SeekComplete Error }<o:p></o:p> hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=667854, sector=163854<o:p></o:p> end_request: I/O error, dev 03:02 (hda), sector 163854<o:p></o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block<o:p></o:p> - inode=20100, block=81927<o:p></o:p> hda: read_intr: status=0x51 { DriveReady SeekComplete Error }<o:p></o:p> hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=667854, sector=163854<o:p></o:p> end_request: I/O error, dev 03:02 (hda), sector 163854<o:p></o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block<o:p></o:p> - inode=20101, block=81927<o:p></o:p> hda: read_intr: status=0x51 { DriveReady SeekComplete Error }<o:p></o:p> hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=667854, sector=163854<o:p></o:p> end_request: I/O error, dev 03:02 (hda), sector 163854<o:p></o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block<o:p></o:p> - inode=20102, block=81927<o:p></o:p> hda: read_intr: status=0x51 { DriveReady SeekComplete Error }<o:p></o:p> hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=667854, sector=163854<o:p></o:p> end_request: I/O error, dev 03:02 (hda), sector 163854<o:p></o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block<o:p></o:p> - inode=20103, block=81927<o:p></o:p> hda: read_intr: status=0x51 { DriveReady SeekComplete Error }<o:p></o:p> hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=667854, sector=163854<o:p></o:p> end_request: I/O error, dev 03:02 (hda), sector 163854<o:p></o:p> EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unable to read inode block<o:p></o:p> - inode=20104, block=81927<o:p></o:p> 30916<o:p></o:p> <o:p> </o:p> Some more information on this system: Wondering if this could have some deep impact on this issue.<o:p></o:p> <ol style='margin-top:0in' start=1 type=1> <li class=MsoNormal style='mso-list:l0 level1 lfo1'>LILO boots the 2.4.7-10 kernel image with option ide=nodma. Can this have any impact on these errors?<o:p></o:p></li> <li class=MsoNormal style='mso-list:l0 level1 lfo1'>The system has a postgresql database which writes data to the maximum of 1 record per 5 second. That much data writes will it do.<o:p></o:p></li> <li class=MsoNormal style='mso-list:l0 level1 lfo1'>On restart, the fsck in the bootup scipts (rc.sysinit) could not resolve this, <o:p></o:p></li> </ol> It said.<o:p></o:p> Checking filesystems<o:p></o:p> Could this be a zero-length partition?<o:p></o:p> fsck.ext3: Attempt to read block from filesystem resulted in short read while tr<o:p></o:p> ying to open /dev/hda2<o:p></o:p> /dev/hda3: recovering journal<o:p></o:p> /dev/hda3: clean, 81/125488 files, 35684/500472 blocks<o:p></o:p> Checking all file systems.<o:p></o:p> [/sbin/fsck.ext3 -- /tmp] fsck.ext3 -a /dev/hda2<o:p></o:p> [/sbin/fsck.ext3 -- /tmp2] fsck.ext3 -a /dev/hda3<o:p></o:p> [FAILED]<o:p></o:p> <o:p> </o:p> *** An error occurred during the file system check.<o:p></o:p> *** Dropping you to a shell; the system will reboot<o:p></o:p> *** when you leave the shell.<o:p></o:p> Give root password for maintenance<o:p></o:p> (or type Control-D for normal startup):<o:p></o:p> <o:p> </o:p> <o:p> </o:p> I went ahead and further gave root password and ran the command. e2fsck -a -c -C 0 /dev/hda2<o:p></o:p> It said:<o:p></o:p> <o:p> </o:p> e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/hda2<o:p></o:p> Could this be a zero-length partition?<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Please give your advice, as this problem has become a big-bang show stopper for our product.<o:p></o:p> Your advice will be very helpful for me to go ahead with this issue.<o:p></o:p> <o:p> </o:p> Thanks in advance,<o:p></o:p> Arun S<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> </div> </body> </html>