public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@MIT.EDU>
To: Andreas Dilger <adilger@sun.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext* free space fragmentation reporting
Date: Mon, 21 Jul 2008 22:59:35 -0400	[thread overview]
Message-ID: <20080722025935.GL28839@mit.edu> (raw)
In-Reply-To: <20080721211334.GP3370@webber.adilger.int>

On Mon, Jul 21, 2008 at 03:13:34PM -0600, Andreas Dilger wrote:
> We wrote a tool for Lustre which reports the free space fragmentation in
> ext* filesystems.  There was a request on linuxfs to get a copy of this
> patch, and I thought it would be potentially useful for others as well.
> The patch is against 1.40.11, but I don't think it would need to change
> much (if any) for 1.40.1 because it only uses public libext2fs interfaces.

Thanks, I'll look at this.  Speaking of which, a week or two ago I was
going through the clusterfs patches to see if there was anything I had
missed for 1.41.0 that should either go into 1.42 or 1.41.1, and I
noticed there were a number of extra tools, of which freefrag was but
one.

Can I assume a signed-off by "Andreas Dilger <adilger@sun.com>" for
any of the Clusterfs/Sun e2fsprogs patches in the public patches
directory?  Are there any other user programs in particular that
should be included?

						- Ted

  reply	other threads:[~2008-07-22  2:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21 21:13 [PATCH] ext* free space fragmentation reporting Andreas Dilger
2008-07-22  2:59 ` Theodore Tso [this message]
2008-07-22  7:05   ` 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=20080722025935.GL28839@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger@sun.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