From: Christoph Hellwig <hch@infradead.org>
To: Barry Naujok <bnaujok@sgi.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: REVIEW: xfs_metadump improvements
Date: Tue, 26 Aug 2008 15:12:08 -0400 [thread overview]
Message-ID: <20080826191208.GA2788@infradead.org> (raw)
In-Reply-To: <op.udjxj3hm3jf8g2@pc-bnaujok.melbourne.sgi.com>
On Mon, Jun 30, 2008 at 05:53:53PM +1000, Barry Naujok wrote:
> Based on what I found in xfs_check, I fixed up xfs_metadump in the
> same way.
That's the pop_cur bits and they look sane to me.
>
> Also, I've increased the default maximum expected extent size for
> a directory, as in practice, 400 block extents for directory
> structures is not rare.
Also looks good, but mixing these two up in the same commit doesn't
seem like a good idea.
prev parent reply other threads:[~2008-08-26 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 7:53 REVIEW: xfs_metadump improvements Barry Naujok
2008-08-26 2:07 ` Barry Naujok
2008-08-26 19:12 ` Christoph Hellwig [this message]
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=20080826191208.GA2788@infradead.org \
--to=hch@infradead.org \
--cc=bnaujok@sgi.com \
--cc=xfs@oss.sgi.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