public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] xfs/065: make sure SCRATCH_DEV is unmount before mkfs
Date: Wed, 27 Mar 2019 07:41:10 -0700	[thread overview]
Message-ID: <20190327144110.GD6537@magnolia> (raw)
In-Reply-To: <20190327074509.27770-1-zlang@redhat.com>

On Wed, Mar 27, 2019 at 03:45:09PM +0800, Zorro Lang wrote:
> Commit "8309b39a fstests: fix broken _require_scratch usage" did
> below change on xfs/065:
> 
>   -_scratch_unmount 2>/dev/null
>   +_scratch_mkfs_xfs >> $seqres.full
> 
> It cause xfs/065 always fails now, as:
>   QA output created by 065
>   mkfs.xfs: /dev/sdb2 contains a mounted filesystem
>   ...
> 
> So use _require_scratch, to make sure the SCRATCH_DEV is unmounted
> before mkfs.
> 
> Signed-off-by: Zorro Lang <zlang@redhat.com>

DOH, stupid editor... <grumble>

Sorry about that.

Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>

--D

> ---
>  tests/xfs/065 | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/tests/xfs/065 b/tests/xfs/065
> index c0d1ee93..f09bd947 100755
> --- a/tests/xfs/065
> +++ b/tests/xfs/065
> @@ -50,6 +50,7 @@ _list_dir()
>  # real QA test starts here
>  _supported_fs xfs
>  _supported_os Linux
> +_require_scratch
>  
>  #
>  # too much hassle to get output matching with quotas turned on
> -- 
> 2.17.2
> 

      reply	other threads:[~2019-03-27 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27  7:45 [PATCH] xfs/065: make sure SCRATCH_DEV is unmount before mkfs Zorro Lang
2019-03-27 14:41 ` Darrick J. Wong [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=20190327144110.GD6537@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=zlang@redhat.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