From: Josef Bacik <jbacik@fusionio.com>
To: "Miguel Negrão" <miguel.negrao-lists@friendlyvirus.org>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs send/receive issues
Date: Mon, 24 Jun 2013 12:21:39 -0400 [thread overview]
Message-ID: <20130624162139.GI4288@localhost.localdomain> (raw)
In-Reply-To: <1372027293.1052.12.camel@miguel-MacBookPro>
On Sun, Jun 23, 2013 at 11:41:33PM +0100, Miguel Negrão wrote:
> Hi,
>
> I want to do a backup of a btrfs subvolume from one disk to another
> disk, both with btrfs filesystems, using the btrfs send receive
> functionality. I do
>
> cd /media/miguel/btrfs_backup/
> mkdir backups
> sudo btrfs send /mnt/@backup2 | sudo btrfs receive /media/miguel/btrfs_backup/backups/
>
> and this works fine, the @backup2 subvolume is created
> at /media/miguel/btrfs_backup/backups/. Then I try to send a second
> snapshot taken after @backup2 :
>
> sudo btrfs send -p /mnt/@backup2 /mnt/@backup3 | sudo btrfs receive /media/miguel/btrfs_backup/backups/
>
> And I get:
>
> At subvol /mnt/@backup3
> At snapshot @backup3
> ERROR: open backups/@backup2 failed. No such file or directory
>
> But @backup2 is a subvolume in /media/miguel/btrfs_backup/backups/
>
> I'm I doing something wrong ?
>
I'm not sure, I just did it and it worked fine for me. Could you file a
bugzilla at bugzilla.kernel.org and make sure the component is set to btrfs?
Also could you do the send to a file, and then receive from the file so we can
see if its send or receive that's giving you the error and put that in the
bugzilla? Thanks,
Josef
next prev parent reply other threads:[~2013-06-24 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-23 22:41 btrfs send/receive issues Miguel Negrão
2013-06-24 16:21 ` Josef Bacik [this message]
2013-06-26 10:03 ` Miguel Negrão
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=20130624162139.GI4288@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miguel.negrao-lists@friendlyvirus.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).