On Fri, Feb 02, 2007 at 12:25:04AM +0100, Pawel Jakub Dawidek wrote: > On Thu, Feb 01, 2007 at 11:00:07AM +0000, Darren J Moffat wrote: > > Neil Perrin wrote: > > >No it's not the final version or even the latest! > > >The current on disk format version is 3. However, it hasn't > > >diverged much and the znode/acl stuff hasn't changed. > > > > and it will get updated as part of zfs-crypto, I just haven't done so yet > > because I'm not finished designing yet. > > Do you consider adding a new property type (next to readonly and > inherit) - a "oneway" property? Such propery could be only set if the > dataset has no children, no snapshots and no data, and once set can't be > modified. "oneway" would be the type of the "encryption" property. > On the other hand you may still want to support encryption algorithm > change and most likely key change.
I think you asking about some sort of magic property behaviour. I imagine magic properties like these: - all_ascii True if all filesystem object names are US-ASCII only (i.e., there are no bytes with the high bit set in such names). - all_utf8 True if all filesystem object names are UTF-8 only (in terms of encoding; the filesystem couldn't tell if there's any codeset/encoding aliasing going on, of course). - all_encrypted True if all contents is encrypted. - encryption_start Timestamp from which all new content is encrypted. and so on. These are all magical in that you can't set them, or if you can you can only set them to a subset of their possible values. Nico -- _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
