Hi quxuan, Could you have a test with ext3's journal disabled? In our production, I encountered several cases where deleting on a deleted entry happened in ext2, however it doesn''t bother apps, so we didn't dig the cause. Yongqiang. On Wed, Dec 5, 2012 at 11:46 PM, qixuan wu <wuqixuan@xxxxxxxxx> wrote: > Hi Tao, > > On Wed, Dec 5, 2012 at 9:58 PM, Tao Ma <tm@xxxxxx> wrote: >> Hi qixuan, >> On 12/05/2012 12:16 AM, qixuan wu wrote: >>> Hi Tao, all, >>> >>> I guess it's a memory(or ext3/kenrel) issue. Beause in one >>> machine, after report this issue, the partition is made to readonly, >>> we use debugfs to "ls dir", and it's fine. It can list all files >>> without error. If the disk has issue, when we using ls command, it >>> will give error also. (The dir name is also using debugfs to get by >>> issue inode ID.) >> Are you sure the disk is good? I just checked the code in e2fsprogs, it >> seems that it will not complain if rec_len = 0, and the dir iteration >> just aborts. I guess the right way should be dd the corresponding block >> out, decode and read it in binary format. :( > > Good idea, will do it. > > Thanks > wuqixuan > >> Thanks >> Tao > -- > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Best Wishes Yongqiang Yang -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
