Thanks for the comments... I won't repeat everything, if you want the
emails, contact me.
But in short:
The main reason for both of these warnings is that a crashed or halted NFS
server can easily cause major problems with a disk hard mounted and/or at
the / (root) level
Quite a few programs traverse filesystems starting at /, and if they
happen upon a NFS mounted filesystem there, they will (in the default NFS
option set up) wait "forever" for an inaccessible server.
That's why automounting is preferred. And at a minimum, if you do have
hard mounts, suggested to use the "soft" and "intr" options when
mounting. This will enable the system and processes to timeout and
continue with error (or can be interruptable) if a disk/host is unavailable.
>Ok... I've heard of warnings not to mount NFS disks at the root level...
>can someone explain why? We currently have a dozen or so disks
>automounted to /A/<disk> then linked to /<disk>
>
>2nd... I've always thought it was unsuggested to "hard" mount (through
>fstab) a dozen or more NFS disks... much more preferred to use
>automount. I'm being pushed against the wall to mount a dozen disks since
>I can't get the time to get automount (autofs) working under Linux (i386 &
>alpha). Comments on having this many "hard" mounts?
>
>Thanks
>--Dan
--------------------------------------------------------------------------
Dan Kirkpatrick dkirk_at_phy.syr.edu
Computer Systems Manager
Department of Physics
Syracuse University, Syracuse, NY
http://www.phy.syr.edu/~dkirk Fax: (315) 443-9103
--------------------------------------------------------------------------
Received on Mon Apr 03 2000 - 20:08:56 NZST