[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <470DC928.7000609@linux.vnet.ibm.com>
Date: Thu, 11 Oct 2007 12:26:40 +0530
From: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
To: Andreas Dilger <adilger@...sterfs.com>
CC: linux-ext4 <linux-ext4@...r.kernel.org>,
Avantika Mathur <mathur@...ux.vnet.ibm.com>
Subject: Re: uninit block group/mballoc and fsstress
Andreas Dilger wrote:
> On Oct 10, 2007 22:07 +0530, Aneesh Kumar K.V wrote:
>> I am hitting this with the below config
>>
>> mke2fs -j -I 256 -O lazy_bg $dev
>
> Note that "-O lazy_bg" has nothing really to do with the uninit_groups
> feature. Also, if you don't have the CFS e2fsprogs patches for
> uninit_groups then mke2fs creates an invalid filesystem if the journal is
> large (this was an unrelated bug we fixed while testing uninit_groups).
> Try running e2fsck right after the above mke2fs and you will likely
> see errors.
>
e2fsprogs found at
ftp://ftp.clusterfs.com/pub/lustre/other/e2fsprogs
sets unint with -O lazy_bg. Is there any other option that i can use to set
the uninit block group feature ?
>> jbd2_journal_bmap: journal block not found at offset 31780 on sda7
>
> The problem is that lazy_bg allocates the journal blocks incorrectly, IIRC.
>
> Cheers, Andreas
> --
> Andreas Dilger
> Principal Software Engineer
> Cluster File Systems, Inc.
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists