From b8a8bc917d2162827199341aa82d18b1dc826763 Mon Sep 17 00:00:00 2001 From: Axel Burri Date: Mon, 11 Sep 2017 19:37:09 +0200 Subject: [PATCH] documentation: FAQ.md: fix description for removing received_uuid on read-only subvolume --- doc/FAQ.md | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/doc/FAQ.md b/doc/FAQ.md index a1da6c2..76fbe82 100644 --- a/doc/FAQ.md +++ b/doc/FAQ.md @@ -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_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: +Either delete them (they won't be used for incremental send-receive +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 -complain any more. +Finally, don't forget to delete the broken source subvolume: + + # btrfs subvolume delete mysubvolume.broken + +You should now have a clean environment, and btrbk will not complain +any more.