From: Eric Sandeen <sandeen@sandeen.net>
To: Eryu Guan <eguan@redhat.com>, fstests@vger.kernel.org
Subject: Re: [PATCH 4/4] xfs/073: be quiet about mouting with nouuid option
Date: Wed, 11 Mar 2015 10:51:25 -0400 [thread overview]
Message-ID: <5500566D.5080401@sandeen.net> (raw)
In-Reply-To: <1426072534-12246-5-git-send-email-eguan@redhat.com>
On 3/11/15 7:15 AM, Eryu Guan wrote:
> v4 and v5 xfs generate different outputs because v4 xfs only retries
> mount with nouuid option once in the test, v5 xfs tries more times(with
> xfs_copy running with -d option).
>
> Just be quiet about mounting with nouuid option, it's much easier than
> preparing two different 073.outs and selecting the proper one at runtime
Ah, ok, I see now. Might have been better to swap the order of your patches
3 and 4 so things work after each patch application.
This does make the test slightly less useful, as we don't know whether we've
properly copied the UUID (if for some strange reason it changed when it
shouldn't) but that doesn't seem too likely or important, so:
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
> Signed-off-by: Eryu Guan <eguan@redhat.com>
> ---
> tests/xfs/073 | 2 +-
> tests/xfs/073.out | 1 -
> 2 files changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/tests/xfs/073 b/tests/xfs/073
> index f955771..508725f 100755
> --- a/tests/xfs/073
> +++ b/tests/xfs/073
> @@ -88,7 +88,7 @@ _verify_copy()
>
> mount -t xfs -o loop $target $target_dir 2>/dev/null
> if [ $? -ne 0 ]; then
> - echo retrying mount with nouuid option
> + echo retrying mount with nouuid option >>$seqres.full
> mount -t xfs -o loop -o nouuid $target $target_dir
> if [ $? -ne 0 ]; then
> echo mount failed - evil!
> diff --git a/tests/xfs/073.out b/tests/xfs/073.out
> index f3b147e..3f27467 100644
> --- a/tests/xfs/073.out
> +++ b/tests/xfs/073.out
> @@ -29,7 +29,6 @@ Creating file <FSIMAGE1>
> All copies completed.
> checking new image
> mounting new image on loopback
> -retrying mount with nouuid option
> comparing new image files to old
> comparing new image directories to old
> comparing new image geometry to old
>
prev parent reply other threads:[~2015-03-11 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 11:15 [PATCH 0/4] some random small fixes Eryu Guan
2015-03-11 11:15 ` [PATCH 1/4] new: fix template for new case to use a single tab not four spaces Eryu Guan
2015-03-11 13:59 ` Eric Sandeen
2015-03-11 11:15 ` [PATCH 2/4] generic/027: discard mkdir error message Eryu Guan
2015-03-11 14:08 ` Eric Sandeen
2015-03-11 11:15 ` [PATCH 3/4] common: append -d option to XFS_COPY_PROG when testing v5 xfs Eryu Guan
2015-03-11 14:48 ` Eric Sandeen
2015-03-11 14:52 ` Eric Sandeen
2015-03-12 5:57 ` Eryu Guan
2015-03-11 11:15 ` [PATCH 4/4] xfs/073: be quiet about mouting with nouuid option Eryu Guan
2015-03-11 14:51 ` Eric Sandeen [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=5500566D.5080401@sandeen.net \
--to=sandeen@sandeen.net \
--cc=eguan@redhat.com \
--cc=fstests@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