-
-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
btrbk fails on empty target subvolume #4
Comments
Is If it is already present, you might have found a bug. Could you please re-run btrbk with debug output enabled:
|
haha i was already running with debug on when you posted your reply. Here is the output: btrbk -c /etc/btrbk/btrbk.conf.example -l debug dryrun /sbin/btrfs subvolume show /mnt/btrfsroot 2>/dev/nullCommand execution successful /sbin/btrfs subvolume list -a -c -u -q -R /mnt/btrfsrootCommand execution successful /sbin/btrfs subvolume show /media/Storage3/@HomeSnaps 2>/dev/nullCommand execution successful /sbin/btrfs subvolume list -a -c -u -q -R /media/Storage3/@HomeSnapsCommand execution successful
/mnt/btrfsroot/@Home NOTE: Some errors occurred, which may result in missing backups! NOTE: Dryrun was active, none of the operations above were actually executed! And the output of the command that executes just before the failure in case it is to blame... Had to put it in pasetbin since git was removing part of the output... |
Thanks, I identified a bug introduced in commit: 14e675b btrbk now has problems with empty backup subvolumes. As a workaround, simply create a dummy subvolume:
...while I'm fixing... |
great thank you |
fixed in d17d0ab |
fixed in btrbk v0.14 |
Thank you for moving so quick on this. |
It's always nice to see that other people are also using btrbk. I hope it turns out to be useful for you as it is for me! Don't hesitate to create feature requests or ask for help, every feedback helps me improving this project. |
I'm pretty sure i have everything setup right so here is the problem:
config file:
cat /etc/btrbk/btrbk.conf.example
snapshot_dir @BackuPs
snapshot_create_always yes
incremental no
preserve_day_of_week sunday
snapshot_preserve_daily all
snapshot_preserve_weekly 4
snapshot_preserve_monthly 1
target_preserve_daily all
target_preserve_weekly 4
target_preserve_monthly 1
btrfs_commit_delete after
receive_log no
volume /mnt/btrfsroot
subvolume @Home
target send-receive /media/Storage3/@HomeSnaps
btrfs subvolume list /media/Storage3/@HomeSnaps
ID 5683 gen 51069 top level 5 path @HomeSnaps
btrfs subvolume show /media/Storage3/@HomeSnaps
/media/Storage3/@HomeSnaps
Name: @HomeSnaps
uuid: 1bb1ed43-5c5d-7542-9a6e-87b36eae5f48
Parent uuid: -
Creation time: 2015-03-19 17:43:48
Object ID: 5683
Generation (Gen): 51069
Gen at creation: 51069
Parent: 5
Top Level: 5
Flags: -
Snapshot(s):
btrbk -c /etc/btrbk/btrbk.conf.example dryrun
WARNING: Skipping target: Failed to read btrfs subvolume list for "/media/Storage3/@HomeSnaps"
WARNING: Skipping cleanup of snapshots for subvolume "/mnt/btrfsroot/@Home", as at least one target aborted earlier
Backup Summary (btrbk command line client, version 0.13)
/mnt/btrfsroot/@Home
+++ /mnt/btrfsroot/@Backups/@Home.20150320
!!! Target "/media/Storage3/@HomeSnaps" aborted: Failed to read btrfs subvolume list for "/media/Storage3/@HomeSnaps"
NOTE: Some errors occurred, which may result in missing backups!
Please check warning and error messages above.
NOTE: Dryrun was active, none of the operations above were actually executed!
i've tried creating the subvol with and without @. At first i was creating it at /media/Storage3/Backup/HomeSnaps but even moving it to the root of the FS i have the same problem. I am using arch linux with kernel 3.19.1-1-ck and btrfs-progs v3.19. Is it something i am doing wrong or a bug?
The text was updated successfully, but these errors were encountered: