linux-ext4 - Re: inconsistent file placement

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: <AANLkTilxmM6mxH23pAjTeVIaM3mjilY8H3oJLfAhw0cp@mail.gmail.com>
Date:	Tue, 6 Jul 2010 08:52:48 +0200
From:	"Amir G." <amir73il@...rs.sourceforge.net>
To:	Daniel Taylor <Daniel.Taylor@....com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: inconsistent file placement

On Tue, Jul 6, 2010 at 3:49 AM, Daniel Taylor <Daniel.Taylor@....com> wrote:
> I realize that it is enerally not a good idea to tune
> an operating system, or subsystem, for benchmarking, but
> there's something that I don't understand about ext[234]
> that is badly affecting our product.  File placement on
> newly-created file systems is inconsistent.  I can't,
> yet, call it a bug, but I really need to understand what
> is happening, and I cannot find, in the source code, the
> source of the randomization (related to "goal"???).
>
> Disk drive performance for writing/reading large files
> is rather sensitive to outer-/inner-diameter cylinder
> placement.  When I create the same file multiple times
> on newly-created ext[234] file systems on the same disk
> partition, I find that it does not consistently occupy
> the same blocks.  In fact, there is enough difference in
> location to cause real differences in performance from
> test to test, which I cannot justify to management.
>

The ext[23] (and I suppose 4 as well) uses the process pid % 16 to
define a 'color' for the process.
New files first block goal depends on that 'color' - the goal is one
of 16 different offsets in the block group
where the new file's inode was allocated (usually the block group of
its parent directory).

The logic behind this allocator is that multiple files created
concurrently in the same directory would
have less chance of stepping over each other's allocations.

I am not sure what you are trying to test or how this behavior badly
affects your product.
If you specify your needs maybe someone can help you solve your problem.
I think that ext4 has some advanced features, like pre-allocation,
that may be able to help you.

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