From: Eric Sandeen <sandeen@redhat.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: linux-btrfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: stat the dev we're removing to make sure its' really gone V3
Date: Mon, 21 Oct 2013 11:15:42 -0500 [thread overview]
Message-ID: <5265532E.1060208@redhat.com> (raw)
In-Reply-To: <1382372033-2742-1-git-send-email-jbacik@fusionio.com>
On 10/21/13 11:13 AM, Josef Bacik wrote:
> I've been periodically failing btrfs/003 because my box sometimes takes a little
> longer to unregister the device when we remove it and so the output from btrfs
> dev show doesn't match what we are wanting since it still sees the device. To
> fix this just stat and sleep if we still see the device node and only continue
> once udev or whatever actually removes the device node so that we don't get
> random failures. Thanks,
>
> Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
> ---
> V2->V3: actually use the lun local variable.
>
> common/rc | 11 ++++++++++-
> tests/btrfs/003 | 2 +-
> 2 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/common/rc b/common/rc
> index b253948..b5eb582 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -2093,7 +2093,16 @@ _require_freeze()
> # ls -l /sys/class/block/sdd | rev | cut -d "/" -f 3 | rev
> _devmgt_remove()
> {
> - echo 1 > /sys/class/scsi_device/${1}/device/delete || _fail "Remove disk failed"
> + local lun=$1
> + local disk=$2
> +
> + echo 1 > /sys/class/scsi_device/${lun}/device/delete || _fail "Remove disk failed"
> +
> + stat $disk > /dev/null 2>&1
> + while [ $? -eq 0 ]; do
> + sleep 1
> + stat $disk > /dev/null 2>&1
> + done
> }
>
> # arg 1 is dev to add and is output of the below eg.
> diff --git a/tests/btrfs/003 b/tests/btrfs/003
> index 262b1d5..15c2cc7 100755
> --- a/tests/btrfs/003
> +++ b/tests/btrfs/003
> @@ -142,7 +142,7 @@ _test_replace()
> DEVHTL=`ls -l /sys/class/block/${d} | rev | cut -d "/" -f 3 | rev`
>
> #fail disk
> - _devmgt_remove ${DEVHTL}
> + _devmgt_remove ${DEVHTL} $ds
> dev_removed=1
>
> $BTRFS_UTIL_PROG fi show $SCRATCH_DEV | grep "Some devices missing" >> $seqres.full || _fail \
>
next prev parent reply other threads:[~2013-10-21 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 16:13 [PATCH] xfstests: stat the dev we're removing to make sure its' really gone V3 Josef Bacik
2013-10-21 16:15 ` Eric Sandeen [this message]
2013-10-22 21:26 ` Rich Johnston
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=5265532E.1060208@redhat.com \
--to=sandeen@redhat.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=xfs@oss.sgi.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).