linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Behrens <sbehrens@giantdisaster.de>
To: Joshua Varghese <jvarghese@ocztechnology.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Receive fails (Could not find parent subvolume)
Date: Fri, 22 Nov 2013 11:34:08 +0100	[thread overview]
Message-ID: <528F3320.8040800@giantdisaster.de> (raw)
In-Reply-To: <528F283F.5060903@ocztechnology.com>

On Fri, 22 Nov 2013 01:47:43 -0800, Joshua Varghese wrote:
> Hi,
> 
> I'm trying to implement a mechanism for incremental backup using btrfs.
> I have two hardisks and each has a btrfs partition on it. I am able to
> take a snapshot of the source partition and send it to the backup disk
> using the send-recieve mechanism. When I try to send an incremental
> backup of a new snapshot with the previous snapshot as the parent btrfs
> command complains (ERROR: could not find parent subvolume). The kernel
> logs also record a error (kernel: could not find root 9). I've listed
> the actual commands and their outputs below. Please let me know if you
> need any more information.
> 
> # btrfs sub create check_backup
> /Create subvolume './check_backup/
> # touch check_backup/before_first_snap
> # btrfs sub snapshot -r check_backup/ first_snap
> /Create a readonly snapshot of 'check_backup/' in './first_snap'/
> # btrfs sub snapshot -r check_backup/ second_snap
> /Create a readonly snapshot of 'check_backup/' in './second_snap'/
> 
> <second volume mounted at /mnt/gentoo/>
> # btrfs send  first_snap | btrfs receive /mnt/gentoo/backup/test/
> /At subvol first_snap//
> //At subvol first_snap//
> /# btrfs send  -p first_snap second_snap/ | btrfs receive
> /mnt/gentoo/backup/test/
> /At subvol second_snap///
> //At snapshot second_snap//
> //ioctl(BTRFS_IOC_TREE_SEARCH, uuid, key 40e9283cdf98a796, UUID_KEY,
> 0fc9a258f8cd8da7) ret=-1, //error: No such file or directory//
> //ERROR: could not find parent subvolume//
> /
> /(kernel log): kernel: could not find root 9/

Works for me.

How old is your kernel (which version)? You need 3.12 or better if you
use the most recent btrfs-progs. New progs and old kernel doesn't work
in this case, new kernel and old progs would work.


> As I understand the send command would take a difference between the two
> snapshots and the send it to the receive. I used the file mechanism
> instead of the pipe and realized that the receive is the one that complains.
> I'd also read in the documentation
> (http://docs.oracle.com/cd/E37670_01/E37355/html/ol_sendrecv_btrfs.hml)
> about clone source. I don't understand its implication in incremental
> backup.
> 
> Regards,
> Josh


  reply	other threads:[~2013-11-22 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <528E467B.40002@ocztechnology.com>
2013-11-22  9:47 ` Receive fails (Could not find parent subvolume) Joshua Varghese
2013-11-22 10:34   ` Stefan Behrens [this message]
2013-11-22 10:44     ` Joshua Varghese
2013-11-22 12:09       ` Joshua Varghese

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=528F3320.8040800@giantdisaster.de \
    --to=sbehrens@giantdisaster.de \
    --cc=jvarghese@ocztechnology.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).