On Sep 9, 2007, at 5:14 AM, Casper.Dik@xxxxxxx wrote:
>> Mounts under /net are derived from the filesystems actually shared
>> from the servers; the automount daemon uses the MOUNT protocol to
>> determine this. If you're looking at a path not already seen, the
>> information will be fresh, but that's where the good news ends.
>> We don't refresh this information reliably, so if you add a new
>> share in a directory we've already scanned, you won't see it until
>> the mounts time out and are removed. We should refresh this data
>> more readily and no matter what the source of data.
> I know that, yes, but why can't we put such an abstraction
> elsewhere in
> the name space? One thing I have always disliked about /net mounts is
> that they're too magical; it should be possible to replicate them
> in some form in other mount maps.
There is nothing that would get in the way of this type of approach.
A simple migration of the -hosts map (/net) functionality would be
to take the prefix used for a regular mount (e.g. server:/a/b) and
any share/export found at the server with the same prefix would
be available at the client's mount point (e.g. /a/b/c -and- /a/b/d).
This would allow the client to mount server:/export/home and
all subordinate shares/exports under that single mount.
The upcoming NFSv4 client mirror-mounts project will provide this
functionality exactly without the need for automount changes (as has
zfs-discuss mailing list