public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] generic/081: hack around the lvm unmount race
Date: Mon, 9 Jan 2017 10:37:38 -0500	[thread overview]
Message-ID: <20170109153738.GB22368@bfoster.bfoster> (raw)
In-Reply-To: <1483969098-16653-1-git-send-email-hch@lst.de>

On Mon, Jan 09, 2017 at 02:38:18PM +0100, Christoph Hellwig wrote:
> This is butt ugly, but I see no better way than to wait a bit to
> work around the race between the weird umount in LVM, and the mount
> ismounted checks.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---

Yes please:

Reviewed-by: Brian Foster <bfoster@redhat.com>

I've had this test expunged from some setups simply because this failure
can cause the entire test run to go off the rails.

>  tests/generic/081 | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/tests/generic/081 b/tests/generic/081
> index 11755d4..426766d 100755
> --- a/tests/generic/081
> +++ b/tests/generic/081
> @@ -35,6 +35,8 @@ _cleanup()
>  	cd /
>  	rm -f $tmp.*
>  	# lvm may have umounted it on I/O error, but in case it does not
> +	# wait a bit for lvm to settle, sigh..
> +	sleep 2
>  	$UMOUNT_PROG $mnt >/dev/null 2>&1
>  	$LVM_PROG vgremove -f $vgname >>$seqres.full 2>&1
>  	$LVM_PROG pvremove -f $SCRATCH_DEV >>$seqres.full 2>&1
> -- 
> 2.1.4
> 
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2017-01-09 15:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09 13:38 [PATCH] generic/081: hack around the lvm unmount race Christoph Hellwig
2017-01-09 15:37 ` Brian Foster [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=20170109153738.GB22368@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    /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