This was part of my original (unpublished) proposal, but deferred it for a few reasons:
- We have discussed the possiblity of introducing pool-wide properties for a variety of reasons (such as background scrubbing intervals). I thought it best to delay dealing with the confluence of these options until a later date. - The functionality is trivial to extend at a later date. It's introduction is a logical conclusion, but doesn't seem a requirement at the moment. - It's only really useful for pools on removable devices, where you want a one-to-one correspondence between the pool and a single filesystem. There are a number of other technical hurdles to overcome before this becomes an attractive option, so I don't view the lack of this functionality as relevant in the enterprise space. Hope that helps, Eric On Wed, Aug 16, 2006 at 02:08:18AM +0200, Daniel Rock wrote: > > Ok, > > but what about the toplevel FS in each pool? Then we need a -o option for > "zpool create" also: > > zpool create pool .... > zfs set compression=on pool > > Or will it be impossible to set encryption on directly on "pool" as opposed > to "pool/fs"? > > > Daniel -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
