Use of automounter for permanent mounts?
- From: Mike <mike@xxxxxxxxxxxx>
- Date: Mon, 04 Jun 2007 21:10:44 +0100
One of my customers has a Web-based application on Solaris 9 with
several back-end NFS-mounted file libraries, which are (hard) mounted
in the usual way via /etc/vfstab.
Occasionally, one of the network links goes down or one of the NFS
servers fails. This results in processes that are using the NFS mount
hanging until the NFS server comes back. That isn't a problem except
that the failed mount has other side-effects such as a delay in
logging in to the system (I'm not sure why but something waits for a
time-out) and processes like "df -h" hang.
To avoid these issues, the customer has suggested that we replace all
these hard NFS mounts with NFS mounts controlled by the automounter.
The idea is that each mount will be set up with a symbolic link of the
ln -s /net/host/path-to-library /mountpoint
and that a network or NFS server failure will affect only those
processes that are accessing the NFS mount without any unwanted
I'm dubious about this but I'm not sure why I feel that way. It may
just be that I remember that the automounter tended to be unreliable
some time ago and there's also the fact that it's (presumably)
intended to be used for occasional transient access to remote NFS
servers, not for permanent mounts.
Can anyone please comment on whether this proposal is sensible or
suggest good technical reasons why it isn't?
- Prev by Date: Re: What does p mean in c0t0d0p0
- Next by Date: Re: Sun Studio 12 released
- Previous by thread: Sun Blade 1000 and USB cd / dvd burner
- Next by thread: Re: Use of automounter for permanent mounts?