On Fri, Aug 11, 2006 at 01:50:05AM +0100, Darren J Moffat wrote: > > I'm assuming since you don't use that syntax in your examples that > there will be a separate proposal/ARC case for the set at create time.
Yes. I have a prototype almost done and will send out a similar proposal, probably tomorrow. I'll try to schedule the ARC cases so that they can refer to one another where appropriate. > I assume even though it can't be inherited it can be set at any > level in the filesytem hierarchy and isn't restricted to the "top" ? Yep. I'll make that clear in the next draft. > This is very cool, it wasn't obvious to me until I read this that > this usage style would be possible. I assume this would be possible > even with multiple pools eg. > > # zfs create acctpool/home > # zfs set canmount=off acttpool/home > # zfs set mountpoint=/export/home acctpool/home > > # zfs create engpool/dev/home > # zfs create engpool/qa/home > # zfs set canmount=off engpool/dev/home > # zfs set canmount=off engpool/qa/home > # zfs set mountpoint=/export/home engpool/dev/home > # zfs set mountpoint=/export/home engpool/qa/home > > # zfs create acctpool/home/bob > # zfs create engpool/dev/home/anne > # zfs create engpool/qa/home/alice > # ls /export/home > anne bob alice > > Right ? > > The difference between your example and mine is that in mine > you can also have different data replication requirements between the > accounting and engineering departments and different quota etc between > the dev and qa subgroups of engineering. Yep, this is all possible. Of course once you do this, you have to be more careful that you don't select overlapping names, since it's only enforceable at mount time ;-) - Eric -- 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
