ambiser
/
btrbk
mirror of https://github.com/digint/btrbk
9
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

documentation: add more instructions for faulty received_uuid

pull/175/head
Axel Burri 2017-07-29 20:54:43 +02:00
parent 356231bc2a
commit 7b50846957
1 changed files with 18 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/FAQ.md
View File

@ -276,5 +276,21 @@ To fix this, create a "proper" snapshot:
# mv mysubvolume mysubvolume.broken # mv mysubvolume mysubvolume.broken
# btrfs subvolume snapshot mysubvolume.broken mysubvolume # btrfs subvolume snapshot mysubvolume.broken mysubvolume
Now, `mysubvolume` should have an empty "Received UUID", and btrbk Now, `mysubvolume` should have an empty "Received UUID". Note that in
will not complain any more. order to have a clean environment, you also need to fix all subvolumes
(snapshots as well as backups) that you created with the broken
subvolume.
Check if there are more broken subvolumes:
# btrfs subvolume show mysubvolume.broken
# btrfs subvolume list -a -R /mnt/btr_pool | grep <"Received UUID" from above>
# btrfs subvolume list -a -R /mnt/btr_backup | grep <"Received UUID" from above>
Now clean all subvolume listed (same as above, but using `btrfs
subvolume snapshot -r` now). Then delete all the broken subvolumes:
# btrfs subvolume delete *.broken
Finally, you should have a clean environment, and btrbk will not
complain any more.