The reason that soft mounts can cause problems is that, if a client
is brought up while the server is down, you can have constant network
traffic from the client trying to connect to the server; same if the server
is lost for a while in a dropout. However, the connection is not reset
on a hardmount... that means if the client is connected to the server,
and you are in a directory being served, when the server dies (or loses
networking or....) then you run the risk of locking up the client machine
(you have open file handles on an inaccessible system) while you WILL lock
and kill your tty. Beyond that, you will have a bit of difficulty in
reconnecting that NFS mount... it won't reconnect automatically.
Problems can occur with soft mounts, too, though... for example, if I
have a softmount to /foo and have a cron job that moves everything in
/foo2 to /foo such as
mv -Rf /foo2 /foo &
I can run into some problems where I will "move" the file to a dead handle
(which would point to /dev/null under some conditions.....)
I'm not being super clear, I know... but it's the easiest way I can explain
it.
As for your fstab entry.... if you want it to automatically mount, why are
you
running with noauto?
Try doing
mount server:/var/remotedir /net/server/var/remotedir
and see what happens. If it mounts cleanly, then remove the noauto from
your
fstab, and voila, you should have it. BTW, if you are doing nosuid, why
mount it rw? Wouldn't it be better in that case to mount it ro?
Bill Ward
-----Original Message-----
From: Matthew Saltzman [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 09, 2000 11:38 PM
To: [EMAIL PROTECTED]
Cc: recipient.list.not.shown; @nswcphdn.navy.mil
Subject: RE: Automounting a volume to a subdirectory
I asked about configuring autofs to mount a subdirectory, and
Ward William E PHDN <[EMAIL PROTECTED]> replied:
>As an aside answer to your question, change the hard to soft
>on your auto.net line. You REALLY shouldn't do hard mounts if you
>can help it. You can hose your NFS mounts, requiring a reboot, if the
>server goes down or you somehow break your network connection.
Interesting. The mount man page suggests that hard,intr is the way
to go. It says about soft: "Usually it just causes lots of trouble."
>The answer to your question, though, is that your link needs to be
>in /etc/fstab.
>
>For example, I have lines similar to this that gets done everytime.
>
>server:/far/directory /local/directory nfs
>user,exec,dev,suid,rw,bg,soft 1 1
>server:/different/directory /different/directory nfs
>user,exec,dev,suid,rw,bg,soft 1 1
OK, I added something. I now have:
auto.master contains
/net /etc/auto.net --timeout 60
auto.net contains
server/var/remotedir -rw,hard,intr server:/var/remotedir
and fstab contains
server:/var/remotedir /net/server/var/remotedir nfs \
noexec,dev,nosuid,rw,noauto 0 0
Still nothing.
I added an entry in auto.net for
server1 -rw,hard,intr server:/var/remotedir
Now, *that* succeeds in automounting server:/var/remotedir on
/net/server1, even without an entry in fstab. So I ask again: what do
I need to do to mount the same directory on /net/server/remotedir? I
need to have it in the right place because it contains a license file
that knows where it should be mounted and won't run if it's not
mounted in the right place.
Thanks again.
Matthew Saltzman
Clemson University Math Sciences
[EMAIL PROTECTED]
http://www.math.clemson.edu/~mjs
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
