Re: ext4dev oddity

["Trever L. Adams" <trever adams gmail com>]

Eric Sandeen wrote:
> So, in the course of other things, I found a way to reproduce this
> error.  And, just for mailing-list-posterity, it seems to be fixed,
> upstream, with:
>
> commit 0bf7e8379ce7e0159a2a6bd3d937f2f6ada79799
> Author: Jose R. Santos <jrs us ibm com>
> Date:   Tue Jun 3 14:07:29 2008 -0400
>
>     ext4: Fix uninit block group initialization with FLEX_BG
>
>     With FLEX_BG block bitmaps, inode bitmaps and inode tables _MAY_ be
>     allocated outside the group.  So, when initializing an uninitialized
>     block bitmap, we need to check the location of this blocks before
>     setting the corresponding bits in the block bitmap of the newly
>     initialized group.  Also return the right number of free blocks when
>     counting the available free blocks in uninit group.
>
>     Tested-by: Aneesh Kumar K.V <aneesh kumar inux vnet ibm com>
>     Signed-off-by: Jose R. Santos <jrs us ibm com>
>     Signed-off-by: Mingming Cao <cmm us ibm com>
>     Signed-off-by: "Theodore Ts'o" <tytso mit edu>
>
> which made it to the 2.6.26 kernels.
>
> the description sounds innocuous but in my case it was actually
> corrupting memory ...
>
> -Eric
>   
Is this going to be seen fixed in F9? And yes, this can be deadly to 
your data. I have seen it trash a file system. I am going to have to 
back up /home and /etc and re-ext4 the drive.

Trever

Attachment: signature.asc
Description: OpenPGP digital signature