From: Zorro Lang <zlang@redhat.com>
To: Jan Tulak <jtulak@redhat.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: xfsdump usecases
Date: Thu, 1 Nov 2018 01:35:49 +0800 [thread overview]
Message-ID: <20181031173549.GI2279@dhcp-12-117.nay.redhat.com> (raw)
In-Reply-To: <CACj3i70vGdyPVytPV_mpF5TnPX9q8jr=1td=1xm3KsW7_jEFwA@mail.gmail.com>
On Wed, Oct 31, 2018 at 04:42:54PM +0100, Jan Tulak wrote:
> Hi guys
>
> I'm doing some cleanup of xfsdump code and the testing infrastructure
> for it in xfstests is rather small, for the number of options and
> modes xfsdump has. So, I'm asking you if you have any scripts using
> xfsdump and xfsrestore, or some custom test suite, can you share it? I
> will polish it and put into xfstests.
Hi Jan,
Unfortunately, we don't have more internal test cases (than xfstests) about
xfsdump/xfsrestore. There's not much bugs(from customers/partners) about
xfsdump, and it keeps stable(no big changes) long time, so writing cases for
it always be low priority jobs for us.
I can help to write some cases or do some tests if you need.
Thanks,
Zorro
>
>
> Thanks,
> Jan
prev parent reply other threads:[~2018-11-01 2:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 15:42 xfsdump usecases Jan Tulak
2018-10-31 17:35 ` Zorro Lang [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=20181031173549.GI2279@dhcp-12-117.nay.redhat.com \
--to=zlang@redhat.com \
--cc=jtulak@redhat.com \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).