Anton B. Rang wrote:
The biggest problem I see with this is one of observability, if not all
of the data is encrypted yet what should the encryption property say ?
If it says encryption is on then the admin might think the data is
"safe", but if it says it is off that isn't the truth either because
some of it maybe still encrypted.
From a user interface perspective, I'd expect something like
Encryption: Being enabled, 75% complete
or
Encryption: Being disabled, 25% complete, about 2h23m remaining
and if we are still writing to the file systems at that time ?
Maybe this really does need to be done with the file system locked.
I'm not sure how you'd map this into a property (or several), but it seems like "on"/"off" ought to
be paired with "transitioning to on"/"transitioning to off" for any changes which aren't
instantaneous.
Agreed, and checksum and compression would have the same issue if there
was a mechanism to rewrite with the new checksums or compression settings.
--
Darren J Moffat
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
