linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: tytso@mit.edu
Cc: Daniel Taylor <Daniel.Taylor@wdc.com>, linux-ext4@vger.kernel.org
Subject: Re: inconsistent file placement
Date: Tue, 06 Jul 2010 13:59:34 -0500	[thread overview]
Message-ID: <4C337D16.9000200@redhat.com> (raw)
In-Reply-To: <20100706185548.GA26677@thunk.org>

tytso@mit.edu wrote:
> On Mon, Jul 05, 2010 at 06:49:34PM -0700, Daniel Taylor 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"???).
> 
> In ext3, it really is random.  The randomness you're looking for can
> be found in fs/ext3/ialloc.c:find_group_orlov(), when it calls
> get_random_bytes().  This is responsible for "spreading" directories
> so they are spread across the block groups, to try to prevent
> fragmented files.  Yes, if all you care about is benchmarks which only
> use 10% of the entire file system, and for which the benchmarks don't
> adequately simulate file system aging, the algorithms in ext3 will
> cause a lot of variability.

However, from the test description it looks like it is writing
a file to the root dir, so there should be no parent-dir random spreading,
right?

-Eric


  reply	other threads:[~2010-07-06 18:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06  1:49 inconsistent file placement Daniel Taylor
2010-07-06  2:38 ` Eric Sandeen
2010-07-06  6:52 ` Amir G.
2010-07-06 18:55 ` tytso
2010-07-06 18:59   ` Eric Sandeen [this message]
2010-07-06 22:01     ` tytso
2010-07-06 22:15     ` Daniel Taylor
2010-07-06 23:14       ` tytso
2010-07-06 23:39         ` Eric Sandeen
2010-07-07  1:08         ` Daniel Taylor
2010-07-07  2:29           ` Eric Sandeen
2010-07-06 23:34       ` Eric Sandeen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C337D16.9000200@redhat.com \
    --to=sandeen@redhat.com \
    --cc=Daniel.Taylor@wdc.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).