From: Eric Sandeen <sandeen@sandeen.net>
To: Josef Bacik <jbacik@fusionio.com>
Cc: linux-btrfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: btrfs/003: stat the dev we're removing to make sure its' really gone
Date: Wed, 21 Aug 2013 11:44:47 -0500 [thread overview]
Message-ID: <5214EE7F.8090507@sandeen.net> (raw)
In-Reply-To: <1377101015-3070-1-git-send-email-jbacik@fusionio.com>
On 8/21/13 11:03 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>
> ---
> tests/btrfs/003 | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/tests/btrfs/003 b/tests/btrfs/003
> index 5c88651..dba1a32 100755
> --- a/tests/btrfs/003
> +++ b/tests/btrfs/003
> @@ -145,6 +145,12 @@ _test_replace()
> _devmgt_remove ${DEVHTL}
> dev_removed=1
>
This should probably go into _devmgt_remove,
and possibly the reverse in _devmgmt_add as well, with
a comment explaining what it's doing?
Otherwise someone else will run into the same problem down the line.
-Eric
> + stat $ds >> $seqres.full 2>&1
> + while [ $? -eq 0 ]; do
> + sleep 1
> + stat $ds >> $seqres.full 2>&1
> + done
> +
> $BTRFS_UTIL_PROG fi show $SCRATCH_DEV | grep "Some devices missing" >> $seqres.full || _fail \
> "btrfs did not report device missing"
>
next prev parent reply other threads:[~2013-08-21 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 16:03 [PATCH] xfstests: btrfs/003: stat the dev we're removing to make sure its' really gone Josef Bacik
2013-08-21 16:44 ` Eric Sandeen [this message]
2013-08-21 17:31 ` Josef Bacik
2013-08-22 18:19 ` Josef Bacik
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=5214EE7F.8090507@sandeen.net \
--to=sandeen@sandeen.net \
--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).