Given that it will be some time before NFSv4 support, let alone NFSv4 support for mount point crossing, in most client operating systems ... what obstacles are in the way of constructing an NFSv3 server which would 'do the right thing' transparently to clients so long as the file systems involved were within a single ZFS pool?
So far I can think of (a) clients expect inode numbers to be unique -- this could be solved by making them (optionally) unique within a pool; (b) rename and link semantics depend on the file system -- for rename this is easy, for link it might require a cross-file-system hard link object, which is certainly doable. This would go a long way towards making ZFS-with-many-filesystems approaches more palatable. (Hmmm, how does CIFS support deal with the many-filesystems problem today?) This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
