From: Mingming Cao <cmm@us.ibm.com>
To: Eric <erpo41@gmail.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: files mapped funny? (related to online defragmentation)
Date: Mon, 21 May 2007 11:00:59 -0700 [thread overview]
Message-ID: <1179770459.23003.7.camel@localhost.localdomain> (raw)
In-Reply-To: <1179755398.389.24.camel@eric-laptop>
On Mon, 2007-05-21 at 06:49 -0700, Eric wrote:
> Hi,
>
> I'm getting strange results when I map out the blocks used in files
> larger than a several thousand KB. I never seem to get any more than
> 1024 contiguous data blocks in a row.
>
> Here's a portion of the output of my script when I run it on a 176MB
> file in my home directory:
> ...
> Contiguous chunk 67: 2385568 - 2385591 (24 blocks)
> Contiguous chunk 68: 2385608 - 2386448 (841 blocks)
> Contiguous chunk 69: 2386450 - 2387473 (1024 blocks)
> Contiguous chunk 70: 2387475 - 2388498 (1024 blocks)
> Contiguous chunk 71: 2388500 - 2389523 (1024 blocks)
> ...
>
> Maybe this is a bug in my script? Can anyone explain why this would
> happen?
>
filefrag command comes with e2fsprogs will print the file fragmentation
info. I guess you can try filefrag -v command and see if that matches
what your scripts reported.
Mingming
> I'm attaching my script in case other ext2/3/4 newbies can get any use
> out of it, and in case anyone needs to see it in order to answer my
> question. It's pretty self-explanatory, though.
>
> Cheers,
>
> Eric
>
next prev parent reply other threads:[~2007-05-21 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 13:49 files mapped funny? (related to online defragmentation) Eric
2007-05-21 18:00 ` Mingming Cao [this message]
2007-05-22 2:08 ` SOLVED: " Eric
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=1179770459.23003.7.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=erpo41@gmail.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