Re: Weird ext4 bug: 256P used?

[Theodore Tso]

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?

     	    	     	  	     	 - Ted
--
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/