From: Stefan Behrens <sbehrens@giantdisaster.de>
To: Josef Bacik <jbacik@fusionio.com>
Cc: Emil Karlson <jekarlson@gmail.com>,
Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Possible bug in send/receive with simple reproducer
Date: Mon, 12 Aug 2013 17:16:04 +0200 [thread overview]
Message-ID: <5208FC34.4080705@giantdisaster.de> (raw)
In-Reply-To: <20130812145952.GC2150@localhost.localdomain>
On Mon, 12 Aug 2013 10:59:52 -0400, Josef Bacik wrote:
> On Sun, Aug 11, 2013 at 09:53:01PM +0300, Emil Karlson wrote:
>> Greetings
>>
>> Send fails for me unexpectedly:
>>
>> I get:
>> ERROR: rename o262-5-0 -> snapshots failed. No such file or directory
>>
>> reproducer ( http://users.tkk.fi/~jkarlson/files/test4.txt ):
>>
>> for i in 1 2; do
>> mkdir /mnt/$i
>> truncate -s 4G /mnt/$i.img
>> mkfs.btrfs /mnt/$i.img
>> mount -o loop /mnt/$i.img /mnt/$i
>> done
>>
>> mkdir /mnt/1/testdir
>> mkdir /mnt/1/testdir/1/
>> mkdir /mnt/1/testdir/2/
>> dd if=/dev/urandom of=/mnt/1/testdir/aa count=16
>> dd if=/dev/urandom of=/mnt/1/testdir/bb count=16
>>
>> mkdir /mnt/1/snapshots
>> btrfs sub snap -r /mnt/1/ /mnt/1/snapshots/backup2
>> btrfs sub snap -r /mnt/1/ /mnt/1/snapshots/backup3
>> btrfs send /mnt/1/snapshots/backup3/ | btrfs receive /mnt/2/
>>
>> umount /mnt/{1,2}; rm /mnt/{1,2}.img; rmdir /mnt/{1,2}
>
> This was perfect, thank you for that. I've posted a fix and I'll turn this into
> an xfstest to make sure we don't ever regress. Thanks again,
>
If you create a subvolume below /mnt/[12] and run the test there, you
have the problem reproduced again :)
for i in 1 2; do
mkdir /mnt/$i
truncate -s 4G /mnt/$i.img
mkfs.btrfs /mnt/$i.img
mount -o loop /mnt/$i.img /mnt/$i
done
btrfs subv create /mnt/1/sub
btrfs subv create /mnt/2/sub
mkdir /mnt/1/sub/testdir
mkdir /mnt/1/sub/testdir/1/
mkdir /mnt/1/sub/testdir/2/
dd if=/dev/urandom of=/mnt/1/sub/testdir/aa count=16
dd if=/dev/urandom of=/mnt/1/sub/testdir/bb count=16
mkdir /mnt/1/sub/snapshots
btrfs sub snap -r /mnt/1/sub/ /mnt/1/sub/snapshots/backup2
btrfs sub snap -r /mnt/1/sub/ /mnt/1/sub/snapshots/backup3
btrfs send /mnt/1/sub/snapshots/backup3/ | btrfs receive /mnt/2/sub/
umount /mnt/[12]; rm /mnt/[12].img; rmdir /mnt/[12]
next prev parent reply other threads:[~2013-08-12 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 18:53 Possible bug in send/receive with simple reproducer Emil Karlson
2013-08-11 19:08 ` Emil Karlson
2013-08-12 14:59 ` Josef Bacik
2013-08-12 15:16 ` Stefan Behrens [this message]
2013-08-12 18:12 ` 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=5208FC34.4080705@giantdisaster.de \
--to=sbehrens@giantdisaster.de \
--cc=jbacik@fusionio.com \
--cc=jekarlson@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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).