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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 20 May 2015 12:31:48 -0400
From:	Theodore Ts'o <>
To:	Phil Susi <>
Cc:	ext4 development <>
Subject: Re: Unused block group, but all blocks not free?

On Wed, May 20, 2015 at 11:15:59AM -0400, Phil Susi wrote:
> On 5/20/2015 11:10 AM, Theodore Ts'o wrote:
> >Have you checked to see if the metadata for other block groups are
> >taking up space in the block group.  This can happen when using the
> >flex_bg layout.  (And without flex_bg, then *all* block groups will
> >always have blocks in use, for their own metadata blocks.)
> That was my first thought and no, they aren't.  The metadata is in bg 0 and
> bg 32, not 25.  Even still, when the metadata is there, shouldn't the
> allocation bitmap mark those blocks as in use rather than be uninitialized?

As an optimization, if we can reconstruct the allocation bitmap from
the block group descriptors, we'll leave the block allocation bitmap
uninitialized, so that programs like e2fsck don't have to read the
bitmap block.  For a mostly empty file system, this optimization is
quite noticeable.

Can you send me a compressed raw e2image of the file system so I can
take a look?

					- Ted
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists