From: Eric Sandeen <sandeen@sandeen.net>
To: Peter Watkins <treestem@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_db: bug in bmap command?
Date: Thu, 02 Aug 2012 17:26:08 -0500 [thread overview]
Message-ID: <501AFE80.40709@sandeen.net> (raw)
In-Reply-To: <501AFCF1.70804@sandeen.net>
On 8/2/12 5:19 PM, Eric Sandeen wrote:
> On 8/1/12 10:17 AM, Peter Watkins wrote:
>> Hello,
>>
>> If you have a moment would you be kind enough to review the test case
>> and patch below?
>>
>> I ran into this while using xfs_db to dump extents for a large,
>> fragmented file. The extents were stored in btree form.
>
> The xfs_db change looks right.
(and I'll merge it, Reviewed-by: Eric Sandeen <sandeen@sandeen.net> )
Thanks!
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-08-02 22:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 15:17 xfs_db: bug in bmap command? Peter Watkins
2012-08-02 22:19 ` Eric Sandeen
2012-08-02 22:26 ` Eric Sandeen [this message]
2012-08-02 23:31 ` Dave Chinner
2012-08-02 23:30 ` Dave Chinner
2012-08-03 2:37 ` Dave Chinner
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=501AFE80.40709@sandeen.net \
--to=sandeen@sandeen.net \
--cc=treestem@gmail.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