Re: Weird ext4 bug: 256P used?

[Felipe Contreras]

On Tue, Oct 13, 2009 at 4:05 AM, Theodore Tso <tytso@xxxxxxx> wrote:
> On Tue, Oct 13, 2009 at 02:27:48AM +0300, Felipe Contreras wrote:
>>
>> stat /var/lib/yum/yumdb/s/160f96bb8689bae7bed1f8801385845d47913ace-skype-2.0.0.72-fc5-i586
>> Â File: `/var/lib/yum/yumdb/s/160f96bb8689bae7bed1f8801385845d47913ace-skype-2.0.0.72-fc5-i586'
>> Â Size: 4096 Â Â Â Â ÂBlocks: 281470681743368 IO Block: 4096 Â directory
>> Device: fe00h/65024d ÂInode: 141257 Â Â ÂLinks: 2
>> Access: (0755/drwxr-xr-x) ÂUid: (4294901760/ UNKNOWN) Â Gid: (16711680/ UNKNOWN)
>> Access: 2009-10-12 16:36:22.326920328 +0300
>> Modify: 2009-07-27 20:52:23.000000000 +0300
>> Change: 2009-07-27 20:52:23.000000000 +0300
>
> OK, I see what's going on. Â i_blocks_hi is getting set to 0xFFFF.
>
> So I definitely see the bug in e2fsck in not reporitng and fixing the
> problem (and I'll fix that). ÂI'm not sure how i_blocks_hi got set to
> that value, though; it looks like everything should be doing the right
> thing in the latest mainline kernel. ÂWhat version of the kernel are
> you using?

I was using F11 kernels, and at some point I went back to compile my
own kernels. I think I started with 2.6.31 and now 2.6.31.1.

-- 
Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/