On Mon, 1 Aug 2005, Jeff Layton wrote:

> Hi All,
>   Below is the latest iteration of my mount_nfs.c overhaul patch. This
> one now passes the addr= option to the mount command when the NFS server
> is deemed to be "local" (which in my patch is different than a bind
> mount).
> 
> This patch, in conjunction with the patch to mount that I sent to the
> util-linux maintainer should give us the proper behavior when the NFS
> server is a multihomed host and has an interface on the same subnet as
> the client.
> 
> I've unfortunately still not heard back from Adrian Bunk on my mount
> patch, however, so I have no idea if that's going to go in or not.
> 
> Still though, passing the addr= option shouldn't be harmful since the
> current version of mount just ignores it. We just may not get the
> desired behavior without that.
> 
> Ian, are you still planning to consider this for inclusion in 4.1.5 or
> 5.x?

My plan is fairly simple.

Get a basic implementation that provides direct mounts and release as 
first alpha. I'm likely to label it 5.0.0 as the best way to support the 
needed change in the protocol between the kernel and the daemon is to bump 
the kernel module protocol version (to 5.00 as well).

Release 4.1.5 soon after, another bug fix release to have as stable a base 
as possible before starting work on 4.1.6 which will include analysis 
and possible merge of the LDAP rework , your mount rework and the run in 
forground patches.

Following that (and probably while working on the above) I will return to 
working on 5.0.0. Forward porting the patches from 4.1.6. New stuff 
that will actually be in 5.0.0 is not final yet. There are two critical 
areas that still require a lot of work. First is lazy mount/umount of 
multi-mount mount entries. This is really difficult. Second is 
implementing a utility to startup and shutdown autofs to get the 
complexity out of the init script.

Another issue is the patch for mount that's heading for util-linux 
some time (and has been in the FC mount) which causes no less than 7 
ports per mount to be opened. autofs opens 2 as well giving a total of 9 
per mount. Only one is needed for the actual mount. As I said on the NFS 
list, I'm wondering if it's possible to use the SO_LINGER option to help.

Ian

_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs

Reply via email to