linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Wang Shilong <wangshilong1991@gmail.com>
Cc: xfs@oss.sgi.com, jbacik@fb.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: add regression test for running snapshot and send concurrently
Date: Fri, 7 Feb 2014 09:49:08 +1100	[thread overview]
Message-ID: <20140206224908.GD13647@dastard> (raw)
In-Reply-To: <9BC2AB41-F187-4A1A-89D6-743C72446293@gmail.com>

On Thu, Feb 06, 2014 at 09:12:51PM +0800, Wang Shilong wrote:
> Hi Dave,
> 
> > On Mon, Feb 03, 2014 at 11:22:36PM +0800, Wang Shilong wrote:
> >> From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
> >> 
> >> Btrfs would fail to send if snapshot run concurrently, this test is to make
> >> sure we have fixed the bug.
> >> 
> > Couple of comments below.
> > 
> >> +_scratch_mkfs > /dev/null 2>&1
> >> +_scratch_mount
> >> +
> >> +
> >> +touch $SCRATCH_MNT/foo
> >> +
> >> +# get file with fragments by using backwards writes.
> >> +for i in `seq 10240 -1 1`; do
> >> +	$XFS_IO_PROG -f -d -c "pwrite $(($i * 4096)) 4096" \
> >> +	$SCRATCH_MNT/foo > /dev/null | _filter_xfs_io
> > 
> > Indentation.
> > 
> >> +done
> >> +
> >> +$BTRFS_UTIL_PROG subvolume snapshot -r $SCRATCH_MNT \
> >> +	$SCRATCH_MNT/snap_1 >> $seqres.full 2>&1
> >> +
> >> +$BTRFS_UTIL_PROG send -f $SCRATCH_MNT/send_file \
> >> +	$SCRATCH_MNT/snap_1 >> $seqres.full 2>&1 &
> >> +
> >> +pid=$!
> >> +
> >> +$BTRFS_UTIL_PROG subvolume snapshot -r $SCRATCH_MNT/snap_1 \
> >> +	$SCRATCH_MNT/snap_2 >> $seqres.full 2>&1
> >> +
> >> +wait $pid || echo "Failed to send, see dmesg"
> > 
> > This seems kind of racy. It assumes that the send command
> > doesn't complete before the wait $pid call is made. If $pid doesn't
> > exist at this time because it has completed, wait will return 127
> > and the test will fail….
> 
> Sorry for delay reply!
> 
> Maybe a better idea for this will be:
> 
> Opposite to previous way, we do snapshots background while at the
> same time we do sending.
> 
> And btrfs-progs should output meaningful information on send failure, i will
> make a tiny patch to address this issue. but to make this test more friendly, i
> think we can still do something like:
> 
> btrfs send <..>  || echo "Failed to send"

If send is emitting error messages on failures, then the
"|| echo..." is redundant and not necessary to cause a golden image
mismatch. If send is not emitting error messages on failure, then it
needs fixing because users are going to hate you for silently
failing to send the data they asked to be sent.

Either way, the echo command on error in the test is not needed.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

      reply	other threads:[~2014-02-06 22:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 15:22 [PATCH] Btrfs: add regression test for running snapshot and send concurrently Wang Shilong
2014-02-03 23:42 ` Dave Chinner
2014-02-06 13:12   ` Wang Shilong
2014-02-06 22:49     ` Dave Chinner [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=20140206224908.GD13647@dastard \
    --to=david@fromorbit.com \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wangshilong1991@gmail.com \
    --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).