在 2013-2-28，上午12:56，Dave Jones <davej@xxxxxxxxxx> 写道：
> On Wed, Feb 27, 2013 at 11:44:17AM -0500, Theodore Ts'o wrote:
>> On Wed, Feb 27, 2013 at 11:04:46AM -0500, Dave Jones wrote:
>>>>> EXT4-fs error (device sdb1): htree_dirblock_to_tree:919: inode #172235804: block 152052301: comm ls: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=0, name_len=0
>>>
>>> Yeah, looks similar. The missing files/dirs reappeared when I
>>> booted an older kernel, so it looks like the corruption doesn't
>>> hit the disk. Fsck (1.42.5) didn't find anything either.
>>
>> I suspect I see the problem... can you send me the results of
>>
>> debugfs -R "stat <172235804>" /dev/sdb1
>>
>> to confirm?
>
> debugfs 1.42.5 (29-Jul-2012)
> Inode: 172235804 Type: directory Mode: 0775 Flags: 0x80000
> Generation: 1174354732 Version: 0x00000000:00000055
> User: 1000 Group: 1000 Size: 4096
> File ACL: 0 Directory ACL: 0
> Links: 24 Blockcount: 8
> Fragment: Address: 0 Number: 0 Size: 0
> ctime: 0x512d0fdc:71fe3000 -- Tue Feb 26 14:41:16 2013
> atime: 0x512d106e:5a143300 -- Tue Feb 26 14:43:42 2013
> mtime: 0x512d0fdc:71fe3000 -- Tue Feb 26 14:41:16 2013
> crtime: 0x50e76c35:1d69aad8 -- Fri Jan 4 18:56:37 2013
> Size of extra inode fields: 28
> Extended attributes stored in inode body:
> selinux = "unconfined_u:object_r:file_t:s0\000" (32)
> EXTENTS:
> (0):688923213
>
>
> That took about 2 minutes to run btw, expected ?
Hi Dave and Ted,
Thanks for the report. From the result, I think extent status tree is root cause because of wrong logical-to-physical block mapping. I am very sorry about that. I will try to fix the bug ASAP.
Ted, I am not sure whether we need to revert the patch or give me sometimes to fix it.
Thanks!!
- Zheng--
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
