From: Eryu Guan <eguan@redhat.com>
To: dsterba@suse.cz, Qu Wenruo <quwenruo@cn.fujitsu.com>,
Liu Bo <bo.li.liu@oracle.com>,
fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] fstests: introduce btrfs-map-logical
Date: Thu, 13 Apr 2017 11:40:46 +0800 [thread overview]
Message-ID: <20170413034046.GT22845@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170412125222.GI4781@twin.jikos.cz>
On Wed, Apr 12, 2017 at 02:52:23PM +0200, David Sterba wrote:
> > > I understand that we need to do corruption so that we can test if the
> > > repair works, but I'm not sure if the output format will change, or if
> > > the program will get replace by "btrfs inspect-internal" group.
> >
> > In the long-term it will be repleaced, but there's no ETA.
>
> Possibly, if fstests maintainer agrees, we can add btrfs-map-logical to
> fstests. It's small and uses headers from libbtrfs, so this would become
> a new dependency but I believe is still bearable.
IMHO, I think the ability to poke btrfs internal really should be
provided by btrfs-progs package and maintained by btrfs community.
fstests provides some fs-independent c helpers to assist testing, but
not necessarily needs to "understand" filesystem internals.
For historical reason, building fstests requires xfsprogs development
headers, we'd better not introduce new fs-specific dependencies.
Thanks,
Eryu
prev parent reply other threads:[~2017-04-13 3:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1491960463-28680-1-git-send-email-bo.li.liu@oracle.com>
[not found] ` <5d7f7d05-b7af-5d8d-93f6-0db2db4ade85@cn.fujitsu.com>
[not found] ` <20170412123201.GG4781@twin.jikos.cz>
[not found] ` <20170412125222.GI4781@twin.jikos.cz>
2017-04-13 0:42 ` [PATCH] fstests: introduce btrfs-map-logical Qu Wenruo
2017-04-13 3:40 ` Eryu Guan [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=20170413034046.GT22845@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=bo.li.liu@oracle.com \
--cc=dsterba@suse.cz \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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).