linux-ext4 - Re: uninit block group/mballoc and fsstress

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071011044641.GD8122@schatzie.adilger.int>
Date:	Wed, 10 Oct 2007 22:46:41 -0600
From:	Andreas Dilger <adilger@...sterfs.com>
To:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Cc:	linux-ext4 <linux-ext4@...r.kernel.org>,
	Avantika Mathur <mathur@...ux.vnet.ibm.com>
Subject: Re: uninit block group/mballoc and fsstress

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.

> 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