linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elliot Wolk <elliot.wolk@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: restore breaks incremental backup
Date: Mon, 15 Sep 2014 12:36:27 -0400	[thread overview]
Message-ID: <5417158B.4010700@gmail.com> (raw)

restoring from an incremental backup breaks the parent UUIDs, making it 
impossible to continue doing incremental backup.

1) assume you do incremental backup from "home" to "BACKUP":
btrfs subvol snapshot -r /home /home/backup1
btrfs send /home/backup1 | btrfs receive /BACKUP
btrfs subvol snapshot -r /home /home/backup2
btrfs send /home/backup2 -p /home/backup1 | btrfs receive /BACKUP


2) then you delete "home", mkfs.btrfs, and attempt to restore:
btrfs send /BACKUP/backup2 | btrfs receive /home
btrfs subvol snapshot /home /home/home-rw
btrfs subvol snapshot -r /home/home-rw /home/home-rw/backup3
btrfs send /home/home-rw/backup3 -p /home/backup2 | btrfs receive /BACKUP
#send|receive fails with "parent not found"
#the next step would be to set-default to home-rw, remount, and continue 
inc backup as above

receive fails with "parent not found", which makes sense since the 
parent UUIDs are not the same, but is highly undesirable. i need to 
delete my backup drive and reseed which is mucho scary. perhaps there is 
some obvious way to do this that im missing?

thanks, and sorry if this is too vague or is not actually a misfeature. 
let me know if theres anything i can do to help. {please CC me for 
replies, im not subscribed}


                 reply	other threads:[~2014-09-15 16:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5417158B.4010700@gmail.com \
    --to=elliot.wolk@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).