Disable copy-on-write for /home #925
Open
Conversation
This file contains 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
The rest of the system benefits from copy-on-write: snapshot that are restored (and can be checked) by frzr, compression that got enabled at creation-time, file checksums to ensure integrity. /home and /var do not benefit from CoW however, they might host frequently-written files, potentially even a VM disk: disable CoW for /home so that it can be mounted without nodatacow.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The rest of the system benefits from copy-on-write: snapshot that are restored (and can be checked) by frzr, compression that got enabled at creation-time, file checksums to ensure integrity.
/home and /var do not benefit from CoW however, they might host frequently-written files, potentially even a VM disk: disable CoW for /home so that it can be mounted without nodatacow.