linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@sun.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: 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: Tue, 6 Nov 2007 02:51:33 +0800	[thread overview]
Message-ID: <20071105185133.GA3900@webber.adilger.int> (raw)
In-Reply-To: <472F54EE.9030904@redhat.com>

On Nov 05, 2007  11:37 -0600, Eric Sandeen wrote:
> Alex Tomas wrote:
> > thanks for the data. the attached patch should fix couple issues:
> > broken history output and policy in that smaller usable chunk to
> > be used. can you give it a spin, please?
> 
> This looks *much* better:
> 
> First block: 100355
> Last block: 2342657
> Discontinuity: Block 30208 is at 133120 (was 130562)
> Discontinuity: Block 60928 is at 165891 (was 163839)
> Discontinuity: Block 90368 is at 197634 (was 195330)
> Discontinuity: Block 121856 is at 232448 (was 229121)
> Discontinuity: Block 150528 is at 263170 (was 261119)
> Discontinuity: Block 181504 is at 296963 (was 294145)
> Discontinuity: Block 210944 is at 328706 (was 326402)
> Discontinuity: Block 241664 is at 361474 (was 359425)
> Discontinuity: Block 272896 is at 395264 (was 392705)
> Discontinuity: Block 303360 is at 427010 (was 425727)
> Discontinuity: Block 334080 is at 459778 (was 457729)
> Discontinuity: Block 365568 is at 493568 (was 491265)
> Discontinuity: Block 395264 is at 525314 (was 523263)
> Discontinuity: Block 426240 is at 558082 (was 556289)
> ....

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.

Cheers, Andreas
--
Andreas Dilger
Sr. Software Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

  parent reply	other threads:[~2007-11-05 18:51 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 [this message]
2007-11-05 18:54                     ` Eric Sandeen
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=20071105185133.GA3900@webber.adilger.int \
    --to=adilger@sun.com \
    --cc=Kalpak.Shah@Sun.COM \
    --cc=bzzz.tomas@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /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).