From: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Andreas Dilger <adilger@dilger.ca>,
"<linux-ext4@vger.kernel.org>" <linux-ext4@vger.kernel.org>,
"<tytso@mit.edu>" <tytso@mit.edu>,
"<darrick.wong@oracle.com>" <darrick.wong@oracle.com>
Subject: Re: [PATCH] misc/e4defrag: output extent's status(written or unwritten)
Date: Mon, 6 Oct 2014 19:04:18 +0800 [thread overview]
Message-ID: <54327732.2050603@cn.fujitsu.com> (raw)
In-Reply-To: <5422CAC2.7080409@redhat.com>
Hi,
On 09/24/2014 09:44 PM, Eric Sandeen wrote:
> On 9/23/14 8:11 PM, Xiaoguang Wang wrote:
>> Hi,
>>
>> On 09/24/2014 03:02 AM, Andreas Dilger wrote:
>>> It would be nice if the output would match the format used by filefrag.
>> OK, will send a V2 version, thanks!
>
> And could they share code? I seem to remember that it's taken several
> iterations to get filefrag working properly, or some reason.
Sorry for much late response, I was away from the internet for some time.
Yes, we can pull some shared code together, but I found filefrag couldn't
work correctly when using FIBMAP, I'd like to fix it first. Please check
my next mail that fixes this bug, thanks!
Regards,
Xiaoguang Wang
>
> -Eric
>
>
>> Regards,
>> Xiaoguang Wang
>>
>
> .
>
next prev parent reply other threads:[~2014-10-06 11:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 10:41 [PATCH] misc/e4defrag: output extent's status(written or unwritten) Xiaoguang Wang
2014-09-23 19:02 ` Andreas Dilger
2014-09-24 1:11 ` Xiaoguang Wang
2014-09-24 13:44 ` Eric Sandeen
2014-10-06 11:04 ` Xiaoguang Wang [this message]
2014-10-06 11:05 ` [PATCH] filefrag: fix wrong extent count calculation when using FIBMAP Xiaoguang Wang
2014-10-06 22:29 ` Andreas Dilger
2014-10-07 1:43 ` Xiaoguang Wang
2014-10-07 2:43 ` Darrick J. Wong
2014-10-07 3:50 ` Xiaoguang Wang
2014-10-07 3:59 ` Darrick J. Wong
2014-10-07 4:12 ` Xiaoguang Wang
2014-10-07 8:31 ` [PATCH v2] " Xiaoguang Wang
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=54327732.2050603@cn.fujitsu.com \
--to=wangxg.fnst@cn.fujitsu.com \
--cc=adilger@dilger.ca \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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.