linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Curt Wohlgemuth <curtw@google.com>
Cc: Andreas Dilger <adilger@sun.com>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Question on block group allocation
Date: Wed, 29 Apr 2009 17:20:43 -0400	[thread overview]
Message-ID: <20090429212043.GB24749@mit.edu> (raw)
In-Reply-To: <6601abe90904291321u3f13d8b0p88b9a9eba5bc03a1@mail.gmail.com>

On Wed, Apr 29, 2009 at 01:21:09PM -0700, Curt Wohlgemuth wrote:
> 
> Hmm, I thought I attached the output from "e2fsck -E fragcheck"; yes,
> I did: one simple line:
> 
>         /dev/hdm3: clean, 14/45760512 files, 7608255/183010471 blocks

Sorry, I should have been more explicit.   You need to do

"e2fsck -f -E fragcheck", and you will get a *heck* of a lot more than
a single line.  :-)

> And actually, I created the files sequentially:
> 
> dd if=/dev/zero of=$MNT_PT/4g bs=1G count=4
> dd if=/dev/zero of=$MNT_PT/4g-2 bs=1G count=4
> dd if=/dev/zero of=$MNT_PT/10g bs=1G count=10

Really?  Hmm, I wouldn't have expected that.  So now I'd really love
to see the fragcheck results (both with and without the patch), and/or
the results of debugfs stat'ing all three files, both with and without
the patch.

Thanks,

						- Ted

  reply	other threads:[~2009-04-29 21:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 16:41 Question on block group allocation Curt Wohlgemuth
2009-04-23 19:08 ` Andreas Dilger
2009-04-23 22:02   ` Curt Wohlgemuth
2009-04-27  2:14     ` Theodore Tso
2009-04-27  5:29       ` Curt Wohlgemuth
2009-04-27 10:42         ` Theodore Tso
2009-04-27 22:40         ` Theodore Tso
2009-04-29 18:38           ` Curt Wohlgemuth
2009-04-29 19:37             ` Theodore Tso
2009-04-29 20:21               ` Curt Wohlgemuth
2009-04-29 21:20                 ` Theodore Tso [this message]
2009-04-29 21:50                   ` Theodore Tso
2009-04-29 22:29                     ` Curt Wohlgemuth
2009-05-01  4:39                       ` Theodore Tso
2009-05-04 15:52                   ` Curt Wohlgemuth
2009-04-29 19:16         ` Theodore Tso
2009-04-27 23:12   ` Andreas Dilger

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=20090429212043.GB24749@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger@sun.com \
    --cc=curtw@google.com \
    --cc=linux-ext4@vger.kernel.org \
    /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).