From: Arne Jansen <sensille@gmx.net>
To: Rory Campbell-Lange <rory@campbell-lange.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs receive to subdirectory
Date: Mon, 08 Oct 2012 22:53:58 +0200 [thread overview]
Message-ID: <50733D66.5020600@gmx.net> (raw)
In-Reply-To: <20121008163010.GA22763@campbell-lange.net>
On 10/08/12 18:30, Rory Campbell-Lange wrote:
> I can send snapshots to <volume>, but not <volume>/<dir>. Please advise
> if what I am doing is incorrect.
>
> Rory
>
> Format usb3 disk and mount
> root@orchard:/bkp# mkfs.btrfs /dev/sdb1
> > WARNING! - Btrfs v0.20-rc1-37-g91d9eec IS EXPERIMENTAL
> > WARNING! - see http://btrfs.wiki.kernel.org before using
> > fs created label (null) on /dev/sdb1
> > nodesize 4096 leafsize 4096 sectorsize 4096 size 698.64GB
> > Btrfs v0.20-rc1-37-g91d9eec
> mount /dev/sdb1 /mnt
>
>
> Create snapshots on /bkp share
> root@orchard:/bkp# btrfs subvolume snapshot -r subvol snaps/snap_081012_1715
> > Create a readonly snapshot of 'subvol' in 'snaps/snap_081012_1715'
> root@orchard:/bkp# mutt -f subvol/INBOX/
> > 1561 kept, 18 deleted.
> root@orchard:/bkp# btrfs subvolume snapshot -r subvol snaps/snap_081012_1716
> > Create a readonly snapshot of 'subvol' in 'snaps/snap_081012_1716'
>
> Send base backup to /mnt
> root@orchard:/bkp# btrfs send snaps/snap_081012_1715 | btrfs receive /mnt
> > At subvol snaps/snap_081012_1715
> > At subvol snap_081012_1715
>
> Send incremental backup to /mnt
> root@orchard:/bkp# btrfs send -p snaps/snap_081012_1715 \
> snaps/snap_081012_1716 | btrfs receive /mnt
> > At subvol snaps/snap_081012_1716
> > At snapshot snap_081012_1716
>
> root@orchard:/bkp# ls /mnt
> snap_081012_1715 snap_081012_1716
>
> Results:
> root@orchard:/bkp# btrfs subvolume list /bkp
> > ID 259 gen 62 top level 5 path subvol
> > ID 278 gen 60 top level 5 path snaps/snap_081012_1715
> > ID 279 gen 62 top level 5 path snaps/snap_081012_1716
> root@orchard:/bkp# btrfs subvolume list /mnt
> > ID 256 gen 8 top level 5 path snap_081012_1715
> > ID 259 gen 9 top level 5 path snap_081012_1716
>
> Restart:
> root@orchard:/bkp# btrfs subvolume del /mnt/snap_081012_171*
> > Delete subvolume '/mnt/snap_081012_1715'
> > Delete subvolume '/mnt/snap_081012_1716'
>
> Try and snap to /mnt/<subdir>
> root@orchard:/bkp# mkdir /mnt/snaps
> root@orchard:/bkp# btrfs send snaps/snap_081012_1715 | btrfs receive /mnt/snaps
> > At subvol snaps/snap_081012_1715
> > At subvol snap_081012_1715
> root@orchard:/bkp# btrfs send -p snaps/snap_081012_1715 \
> snaps/snap_081012_1716 | btrfs receive /mnt/snaps
> > At subvol snaps/snap_081012_1716
> > At snapshot snap_081012_1716
> > ERROR: open snaps/snap_081012_1715 failed. No such file or directory
> root@orchard:/bkp# ls /mnt/snaps
> > snap_081012_1715
The target has to be a subvol also. But interestingly enough, it also
fails for a subvol. The base send works, the incremental fails, because
btrfs receive can't find snaps/snap_081012_1715. If you give /mnt/snaps
as the target for the base and just /mnt for the incremental, it works.
There's clearly something broken there...
-arne
>
>
>
next prev parent reply other threads:[~2012-10-08 20:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 16:30 btrfs receive to subdirectory Rory Campbell-Lange
2012-10-08 20:53 ` Arne Jansen [this message]
2012-10-09 11:18 ` Rory Campbell-Lange
2012-10-09 13:25 ` Alex Lyakas
2012-10-10 22:11 ` Rory Campbell-Lange
2012-10-11 9:10 ` Alex Lyakas
2012-10-11 11:33 ` Rory Campbell-Lange
2012-10-11 12:51 ` Alex Lyakas
2012-10-11 14:56 ` Rory Campbell-Lange
2012-10-11 18:38 ` Alex Lyakas
2012-10-12 11:26 ` Alex Lyakas
2012-10-12 16:10 ` Rory Campbell-Lange
2012-10-13 17:00 ` Alex Lyakas
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=50733D66.5020600@gmx.net \
--to=sensille@gmx.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=rory@campbell-lange.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.