All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Cc: Hugo Mills <hugo@carfax.org.uk>
Subject: How to recover from failing btrffs send | btrfs receive?
Date: Wed, 12 Feb 2014 06:22:07 -0800	[thread overview]
Message-ID: <20140212142207.GX27097@merlins.org> (raw)

So, I've veen running this for a few weeks, and soon should have
something half decent to share for others to use.

Unfortunately, one of my backups is now failing like so:

btrfs send -p "$src_snap" "$src_newsnap" | btrfs receive "$dest_pool/"
+ btrfs send -p /mnt/btrfs_pool1/home_ro.20140209_12:00:01 home_ro.20140212_05:37:49
+ btrfs receive /mnt/btrfs_pool2//
At subvol home_ro.20140212_05:37:49
At snapshot home_ro.20140212_05:37:49
ERROR: rmdir o1845158-142-0 failed. No such file or directory

This looks like it got in an unfinished state it can't recover from.

This was with kernel 3.12.7.

Can I self fix this somehow, I know I can use rsync to make both sides
the sames, but incremental send/receive will not work anymore after
that, correct?

Except, not really. Now I'm confused.
legolas:/mnt/btrfs_pool1# rsync -avSH --delete --dry-run  /mnt/btrfs_pool1/home_ro.20140209_12:00:01/. /mnt/btrfs_pool2/home_ro.20140209_12\:00\:01/.
sending incremental file list
./

sent 116867233 bytes  received 265427 bytes  92194.14 bytes/sec
total size is 129135042766  speedup is 1102.47 (DRY RUN)
legolas:/mnt/btrfs_pool1# 

(I know I start the entire backup over from scratch, but for obvious
reasons, restarting an entire backup from scratch each time I get an
error isn't great since it could take hours or days to backup that much
data)

Suggestions welcome :)

Thanks,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

             reply	other threads:[~2014-02-12 14:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 14:22 Marc MERLIN [this message]
2014-02-14  1:54 ` How to recover from failing btrffs send | btrfs receive? Marc MERLIN
2014-02-16 14:23   ` How to recover from failing btrfs " Marc MERLIN
2014-02-16 15:38     ` Filipe David Manana
2014-02-16 17:23       ` Marc MERLIN
2014-02-16 21:08         ` Filipe David Manana
2014-02-17  5:32           ` Marc MERLIN
2014-02-22 19:22             ` btrfs send ioctl failed with -25: Inappropriate ioctl for device Marc MERLIN
  -- strict thread matches above, loose matches on Subject: below --
2014-02-16 13:43 [PATCH] Btrfs: incremental send, fix invalid path after dir rename Filipe David Borba Manana

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=20140212142207.GX27097@merlins.org \
    --to=marc@merlins.org \
    --cc=hugo@carfax.org.uk \
    --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 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.