From: Curt Wohlgemuth <curtw@google.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Andreas Dilger <adilger@sun.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Question on block group allocation
Date: Mon, 4 May 2009 08:52:05 -0700 [thread overview]
Message-ID: <6601abe90905040852w3846b3bened28369dd4ce6f49@mail.gmail.com> (raw)
In-Reply-To: <20090429212043.GB24749@mit.edu>
Hi Ted:
On Wed, Apr 29, 2009 at 2:20 PM, Theodore Tso <tytso@mit.edu> wrote:
> 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.
Although it might seem like I've been ignoring this request, in fact
I'm having trouble recreating the problem now. Both the "three dd"
commands above, and the performance problem I was seeing in the
original posting seem to have mysteriously disappeared. I'll keep
trying and let the list know what I find.
Thanks,
Curt
>
> Thanks,
>
> - Ted
>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-05-04 15:52 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
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 [this message]
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=6601abe90905040852w3846b3bened28369dd4ce6f49@mail.gmail.com \
--to=curtw@google.com \
--cc=adilger@sun.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).