Yorick
Wizard
- Joined
- Nov 4, 2018
- Messages
- 1,912
I'm going through it and will edit as I go.
man zfs-redact may help. It certainly is a feature that will need some reading to fully get.
Encryption: That's what the man page says, worth testing. I can do that in roughly a week or so, I'll have a test system ready then.
large_dnode: Definitely warn.
project_quota: Really good question. You'd expect software "above" that handles the project IDs.
allocation classes: Not sure I get the question about "generic metadata". As opposed to?
General read-only compatible notes in the list: Maybe add and note that read-only feature works when active, but "can't be read at all" needs to be enabled to remove that restriction, not active.
man zfs-redact may help. It certainly is a feature that will need some reading to fully get.
This feature can be used to allow clones of a filesystem to be made
available on a remote system, in the case where their parent need not
(or needs to not) be usable. For example, if a filesystem contains
sensitive data, and it has clones where that sensitive data has been
secured or replaced with dummy data, redacted sends can be used to
replicate the secured data without replicating the original sensitive
data, while still sharing all possible blocks.
Encryption: That's what the man page says, worth testing. I can do that in roughly a week or so, I'll have a test system ready then.
large_dnode: Definitely warn.
project_quota: Really good question. You'd expect software "above" that handles the project IDs.
allocation classes: Not sure I get the question about "generic metadata". As opposed to?
General read-only compatible notes in the list: Maybe add and note that read-only feature works when active, but "can't be read at all" needs to be enabled to remove that restriction, not active.
Last edited: