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

documentation: FAQ.md: fix description for removing received_uuid on read-only subvolume

pull/185/head
Axel Burri 2017-09-11 19:37:09 +02:00
parent f113436626
commit b8a8bc917d
1 changed files with 12 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/FAQ.md
View File

@ -287,10 +287,17 @@ Check if there are more broken subvolumes:
# btrfs subvolume list -a -R /mnt/btr_pool | grep <"Received UUID" from above> # 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> # btrfs subvolume list -a -R /mnt/btr_backup | grep <"Received UUID" from above>
Now clean all subvolume listed (same as above, but using `btrfs Either delete them (they won't be used for incremental send-receive
subvolume snapshot -r` now). Then delete all the broken subvolumes: anyways), or clean them as follows:
# btrfs subvolume delete *.broken # btrfs subvolume snapshot listed_ro_subvol listed_ro_subvol.rw
# btrfs subvolume delete listed_ro_subvol
# btrfs subvolume snapshot -r listed_ro_subvol.rw listed_ro_subvol
# btrfs subvolume delete listed_ro_subvol.rw
Finally, you should have a clean environment, and btrbk will not Finally, don't forget to delete the broken source subvolume:
complain any more.
# btrfs subvolume delete mysubvolume.broken
You should now have a clean environment, and btrbk will not complain
any more.