Re: Some clients can't see NFS after re-boot

From: Greg Beeker (gbeeker_at_gmail.com)
Date: 03/14/05 

Date: 14 Mar 2005 08:39:05 -0800

Peter Smithson wrote:
> Hi,
>
> I apologize in advance for not finding FAQ's etc. My excuse is that
I'm
> a developer and not an administrator and I don't have time to read up
on
> this issue properly.
>
> Our sys admin chap re-booted an NFS server on Friday and then went on

> holiday for 2 weeks and is not contactable. We have about 10 UNIX
> clients running different types of UNIX and some of them now can't
see
> the mounted directories.

I suspect that the mounts that aren't working are not set to automount.

>
> I tried re-booting one of them but that didn't work - that's almost
the
> end of my sysadmin knowledge!
>
> They can all ping the server and they can all see another nfs server.
>
> The machines that work are -
>
> 3 Solaris boxes (various revs)
> 2 AIX boxes
> 1 HPUX 11 PARISC box
>
> The ones that have a problem are
> 2 Linux boxes (2.4 and 2.3 kernels)
> 1 SCO Open Server Box
> 1 HPUX 11 Itanium (although rather oddly, this one's having a problem

> with only one mount point from the same server - other mount points
are
> fine)
> 1 Unixware 7.11 box

On the boxes that don't work - if you know the directories that aren't
mounted, try the mount command manually:
mount server:/remotmountpoint /localmountpoint

>
> There are a few others that I've not checked.
>
> They all use an automounter.
>
> The NFS server is a Red Hat Linux box running 2.4 kernel. There's
> another similar NFS server that's working OK.
>
> I logged into the server and had a look at /etc/exports but it
doesn't
> mention all the clients anyway. Just one of them infact. The others

> appear to be other nfs servers and two machines in another office - I

> thought you just listed the machines there but I only have a very
basic
> understanding.

If the manual mount works, you know that the mount point is exported
properly. If not, than make sure the system is listed in the
/etc/exports for that mount point.

If the manual mount does not work, post the error message here.
A likely cause could be that the NFS daemon is not running.

>
> I've not even used automount before so it might be something to do
with
> that for all I know - could it be a NIS problem if the automount list
is
> stored there? But our passwords are on NIS and they are working.
>
> Any help appreciated.

Google might help for the with the topic of NFS HOWTO and the specific
OS you are on.

>
> Cheers
>
> Peter
>
>
>
> --
> http://www.beluga.freeserve.co.uk

Relevant Pages

  • Re: Reboot > 1000 NFS clients
    ... have 8 NFS heads serving about 2000 clients. ... Automount is used extensively. ... Long term we see a static mount of this ... environment we want to avoid swamping the NFS server with mount requests. ...
    (comp.protocols.nfs)
  • Re: NFS client , automount and protection problem
    ... Since you're having problems with non-root automount, ... This creates the "disk2" alias in the root. ... WORKS PERFECTLY (aka lists the files on the remote server). ... bother asking the remote server to mount it. ...
    (comp.sys.mac.system)
  • Re: Managing /service for SMP/E
    ... the same name in the mount point and the dsname. ... The problem with Automount comes when AJVSCRPT is run and it expects ... the J1.4 directory that is in the root of the Java HFS to be located ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
    (bit.listserv.ibm-main)
  • Re: Duplicate/False Mount Points
    ... DMA3 isn't really mounted it was a disk I out as automount for my old ... If you type the "mount" command alone, you get the true list of what the ... map auto_home on /home (autofs, ...
    (comp.sys.mac.system)
  • Re: FC3 hotplugging philosophy?
    ... >>have some silly automount thing set up. ... But doing a mount command doesn't show ... checks on the contents of fstab to determine whether the user executing ... mount is allowed to mount that filesystem. ...
    (comp.os.linux.misc)