linux-ext4 - Re: About strange behaviour of ext4 allocation algorithm

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] [day] [month] [year] [list]

Date:	Wed, 23 Dec 2009 07:07:51 -0500
From:	tytso@....edu
To:	Vyacheslav Dubeyko <Vyacheslav.Dubeyko@...onis.com>
Cc:	Andreas Dilger <adilger@....com>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: About strange behaviour of ext4 allocation algorithm

On Wed, Dec 23, 2009 at 01:52:48PM +0300, Vyacheslav Dubeyko wrote:
>  
> I use kernel: 2.6.29.4-167.fc11.i686.PAE #1 SMP Wed May 27 17:28:22
> EDT 2009 i686 i686 i386 GNU/Linux.

Yeah, that was before a massive number of changes to the ext4
allocator.  The changes to the allocators which speed up fsck
described here:

http://thunk.org/tytso/blog/2009/02/26/fast-ext4-fsck-times-revisited/

All went in *after* 2.6.29.  That is, how the block and inode
allocators worked change significantly between 2.6.29 and 2.6.31.

> > If you delete your file, without reformatting the filesystem, and
> > then re-run the test, does it produce the same results?  If not,
> > then it is likely you are seeing the problem with uninitialized
> > groups that was fixed a month or two ago.
> 
> After deletion of the file and re-run test (without reformatting the
> filesystem) I have slightly different extents' tree. Index block
> (depth of the tree = 1) has changed place and several extents has
> another sizes. But nature of the extents' sequence is the same.

The change which Andreas was referring to --- taking out the bias
against opening up uninitialized block groups for allocations until
absolutely necessary, which had a tendency to cause unnecessary
fragmentation --- was merged into mainline between 2.6.30 and 2.6.31.

Best regards,

						- Ted

--
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