Thanks. I guess this makes sense, now that I think about it, since this would
be the same behavior exporting nested ufs filesystems. It just took me by
surprise since I was testing by accessing these on my workstation, and then
when the jobs ran overnight on the server the behavior was different
On Thu, Feb 07, 2008 at 01:54:58PM -0800, Andrew Tefft wrote:
> Let's say I have a zfs called "pool/backups" and it contains two
> zfs'es, "pool/backups/server1" and "pool/backups/server2"
>
> I have sharenfs=on for pool/backups and it's inherited by the
> sub-zfs'es. I can then nfs mount pool/bac
Because of the mirror mount feature that integrated into that Solaris
Express, build 77.
You can read about here on page 20 of the ZFS Admin Guide:
http://opensolaris.org/os/community/zfs/docs/zfsadmin.pdf
Cindy
Andrew Tefft wrote:
> Let's say I have a zfs called "pool/backups" and it contains
Let's say I have a zfs called "pool/backups" and it contains two zfs'es,
"pool/backups/server1" and "pool/backups/server2"
I have sharenfs=on for pool/backups and it's inherited by the sub-zfs'es. I can
then nfs mount pool/backups/server1 or pool/backups/server2, no problem.
If I mount pool/bac
