<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 Andreas,<o:p></o:p> Thanks for your reply.<o:p></o:p> Are there any patches in this kernel for these ext3 bugs? Please guide me to these patches if available.<o:p></o:p> What is the suitable file system for compact flash? I read that JFFS2 is suitable for raw NAND flash card and is not suitable for CF card. Is it true?<o:p></o:p> My application has write operation performed to the CF card even every 3 secs.(worst case)<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> Arun<o:p></o:p> <o:p> </o:p> <o:p> </o:p> -----Original Message----- From: Andreas Dilger [mailto:adilger@clusterfs.com] Sent: Wednesday, June 06, 2007 3:06 AM To: Somasundaram, Arun (IE10) Cc: ext3-users@redhat.com Subject: Re: Help on ext3 file system corruption issue <o:p> </o:p> On Jun 05, 2007 22:01 +0530, Somasundaram, Arun (IE10) wrote:<o:p></o:p> > I have a Kernel 2.4.7-10 with ext3 file system in compact flash. The<o:p></o:p> > system was up for 3 months and was running with average load conditions.<o:p></o:p> <o:p> </o:p> Unless you have a support contract with some vendor, nobody will look at<o:p></o:p> bugs from such an old kernel. There are a hundred old bugs that might<o:p></o:p> have been fixed already.<o:p></o:p> <o:p> </o:p> > One fine day, it just started sending kernel messages on the serial<o:p></o:p> > console. The message was like this.<o:p></o:p> > <o:p></o:p> > <o:p></o:p> > <o:p></o:p> > hda: read_intr: status=0x51 { DriveReady SeekComplete Error }<o:p></o:p> > <o:p></o:p> > hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=667854,<o:p></o:p> > sector=163854<o:p></o:p> > <o:p></o:p> > end_request: I/O error, dev 03:02 (hda), sector 163854<o:p></o:p> > <o:p></o:p> > EXT3-fs error (device ide0(3,2)): ext3_get_inode_loc: unab<o:p></o:p> > <o:p></o:p> > le to read inode block - inode=20089, block=81926<o:p></o:p> <o:p> </o:p> This is likely a hardware error. Probably due to the fact that ext3<o:p></o:p> is not a good filesystem to use on CF because the journal is always<o:p></o:p> overwriting the same part of the CF device. Try something like JFFS2<o:p></o:p> instead.<o:p></o:p> <o:p> </o:p> Cheers, Andreas<o:p></o:p> --<o:p></o:p> Andreas Dilger<o:p></o:p> Principal Software Engineer<o:p></o:p> Cluster File Systems, Inc.<o:p></o:p> </div> </body> </html>