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
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to