Re: [RFC] [PATCH] Flex_BG ialloc awareness V2.

2007-12-13 Thread Jose R. Santos
On Tue, 11 Dec 2007 16:15:28 -0700 Andreas Dilger [EMAIL PROTECTED] wrote: On Dec 11, 2007 10:08 -0600, Jose R. Santos wrote: I'd think being able to avoid the divide for every inode allocation is more important than 8 bits in the superblock. We already avoid the divide since

[PATCH, RFC] - issue warning when bad inode found via ext3_lookup

2007-12-13 Thread Eric Sandeen
I have a hand-crafted bad filesystem image which has a corrupted directory entry: [EMAIL PROTECTED] ~]# ls mnt/Picture LINKS_20 OBEN_20 VORNE_20 VORN_LINKS_20 VORN_RECHTS_20 [EMAIL PROTECTED] ~]# ls mnt/Picture/VORN_LINKS_20 ls: cannot access mnt/Picture/VORN_LINKS_20: No such file or

Re: [RFC] [PATCH] Flex_BG ialloc awareness V2.

2007-12-13 Thread Andreas Dilger
On Dec 13, 2007 09:51 -0600, Jose R. Santos wrote: Now, storing the bits only guaranties that the flexbg size is always a power-of-two and does not guarantee that the super block flexbg size represents the actual meta-data grouping on disk. For this we need to verify that the bitmap offsets