-
Notifications
You must be signed in to change notification settings - Fork 113
Add Read-Only Btrfs Snapshots Option (issue #332) #373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Do we need a warning if someone tries to use |
The shell argument description already clarifies that this feature is specifically for
Btrfs, and I believe that users familiar with rsync will understand that
it doesn't have a "read-only" concept. However, if necessary, perhaps
consider changing the argument name to '--btrfs-readonly'?
|
Please do NOT make snapshots read-only, as this will basically break "grub-btrfs", and prevent the ability to boot into a snapshot. Or if you DO make them read-only, then there should be a separate set of snapshots that are read-write, but I think that would be over-complicating things. At best make this change optional please. |
i think having it optional would be ideal |
I agree with making it optional, but I still recommend keeping read-only as the default behavior, a "writable snapshot" contradicts the design purpose of snapshot (frozen disk state). |
One can always change the "read-only-nes" of a snapshot by either
I think having an option to set the value for all new snapshots (default to ro) and having the option to toggle a snapshot with the context menu would be the best option for everybody.
commit 797d8c2 makes it an option in the settings. |
Adds an option to create read-only Btrfs snapshots by default. Resolves #332