Make it safe against wrong btrfs subvolumes on sles12 issue963 #966
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ection for normal subvolumes in disklayout.conf (issue963)
jsmeix
deleted the
make_it_safe_against_wrong_btrfs_subvolumes_on_sles12_issue963
branch
This was referenced Aug 16, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now snapper's own subvolumes are excluded from being
automatically recreated by listing them only as comments in
disklayout.conf during "rear mkbackup" (via 23_filesystem_layout.sh)
and furthermore if such subvolumes are active in disklayout.conf
they are skipped during "rear recover" plus LogPrint info for the user
(via 13_include_mount_subvolumes_code.sh).