From: Eric Sandeen <sandeen@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>,
Alex Tomas <bzzz.tomas@gmail.com>,
ext4 development <linux-ext4@vger.kernel.org>,
Kalpak Shah <Kalpak.Shah@Sun.COM>
Subject: Re: delalloc fragmenting files?
Date: Mon, 05 Nov 2007 12:54:34 -0600 [thread overview]
Message-ID: <472F66EA.9080908@redhat.com> (raw)
In-Reply-To: <20071105185133.GA3900@webber.adilger.int>
Andreas Dilger wrote:
> On a related note - the FIEMAP patches to filefrag also include a new
> output format that is much more useful, IMHO. The new format is like:
>
> {filename}
> ext: [logical start.. end kB]: phys start..end kB : kB:lun: flags
> 0: [ 0.. 30207]: 401416.. 522251: 120828: 0 :
> 1: [ 30208.. 60927]: 532480.. 655359: 122880: 0 :
> 2: [ 60928.. 121855]: 790536.. 916484: 125948: 0 :
>
> Hopefully Kalpak will be able to post the updated patches here soon.
yep, I hacked existing filefrag to do something like this, the existing
format is pretty hard to glance over :)
One thing I like about xfs_bmap is that it can tell you which Allocation
Group the blocks are in; most filesystems have some concept of
sub-regions of the filesystem, such as BGs or resource groups or whatnot
- do you think there is room for this in the FIEMAP interface? Hm, or
should this just be calculated from knowing the size of the sub-regions...
-Eric
next prev parent reply other threads:[~2007-11-05 18:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 21:24 delalloc fragmenting files? Eric Sandeen
2007-10-26 22:19 ` Andreas Dilger
2007-10-27 2:54 ` Eric Sandeen
2007-10-27 3:08 ` Eric Sandeen
2007-10-31 21:01 ` Eric Sandeen
2007-11-01 0:35 ` Alex Tomas
2007-11-01 15:20 ` Eric Sandeen
2007-11-01 19:05 ` Eric Sandeen
2007-11-02 8:56 ` Alex Tomas
2007-11-02 15:41 ` Eric Sandeen
2007-11-04 18:36 ` Alex Tomas
2007-11-05 17:37 ` Eric Sandeen
2007-11-05 17:39 ` Eric Sandeen
2007-11-05 17:45 ` Alex Tomas
2007-11-05 18:51 ` Andreas Dilger
2007-11-05 18:54 ` Eric Sandeen [this message]
2007-11-06 19:54 ` Eric Sandeen
2007-11-07 20:37 ` Andreas Dilger
2007-11-07 20:53 ` Eric Sandeen
2007-10-29 19:13 ` 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=472F66EA.9080908@redhat.com \
--to=sandeen@redhat.com \
--cc=Kalpak.Shah@Sun.COM \
--cc=bzzz.tomas@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.