Skip to contentSkip to conversation

Thoughts on dynamic networking with AutoFS/NFS

DISCUSSION Chuck Lever 1 participant 1 message Jun 20, 2011 1 message not in the archive Kernel automounter

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive
Quoted 40 lines

From: Ian Kent <[email protected]>

Quoted 5 lines · Colin Simpson

Hi

I was just wondering what the thoughts (maybe plans) are for making autofs/nfs more dynamic in the new world of dynamic networking with the likes of Network Manager now being the default.

I've read this a couple of times now and I'm still not sure what to say because the mail is so open ended. But here are a few comments anyway.

That might mean dbus integration which I've tried to avoid because, to me, that looks really painful and AFAICT the documentation is lousy so working out what the hell to do is difficult and frustrating.

But that's not really the largest part of the work either, which I won't try and go into now, because of the main difficulty described below.

Quoted 5 lines

We now have quite a few users with linux laptops and they want to see the standard automounts on these. But being laptops they frequently switch subnet, jump on WiFi and VPN etc.

Quoted 7 lines

Most subsystems seem to play pretty well with this dynamic network environment and are hooked into NM (with SSSD doing a good job with off net credentials and directory services caching)

Now I know that autofs/nfs is a much harder nut to crack given its heavy in kernel component, but I'd have thought the present non-dynamic behaviour is a bit of an anomaly.

The issue is NFS.

Dynamic fail-over for mounts has been on the NFS list of things to do for over five years and is not done yet. I'm not even sure anything is being done or has been done toward it. And that's just for the simpler case of read-only mounts.

Quoted 6 lines

I'm not sure that is what your after either but the difficulty would be considerably more for read-write mounts. For example, although nfs mounts are stateless (nfs4 is another matter entirely), they rely on a file handle that is constructed based on server dependent information so moving from one network to another and expecting mounts to just continue to work is not going to be simple, if it is even possible.

For more information on NFS plans in this area, Colin, you could post your questions to [email protected]. The NFS version 4 protocol provides lots of opportunities for client-side fail-over support, even for read/write mounts. We're working on some of these pieces now, but it will be a while.

The question of NFSv3 client-side fail-over support is more sticky, as Ian has pointed out.

Signature · 2 lines
Chuck Lever
chuck[dot]lever[at]oracle[dot]com