Re: NFS problems across reboot

[James Pearson <james-p@moving-picture.com>]

Can't offer any solutions, but I've had the same problem - (see
http://marc.theaimsgroup.com/?l=linux-nfs&m=101610950230938&w=2 )

In my case, one particular application (accessing files via NFS on the
server at the time) was causing the server machine to crash, when the
server rebooted, Linux clients got "Permission denied" problems on the
mount points from the server (IRIX clients reported "I/O Error" on the
same mount points).

I thought I had fixed the problem by using a newer kernel on the server
- but all this fixed was the application in question crashing the
machine ... I still see the "Permission denied" problem from time to
time (df reports a similar output to yours as well) - however I don't
see it every time a 'server' reboots - most of our Linux workstations
NFS export local disks - which can be automounted by other workstations
- the workstations tend to get rebooted 'fairly' frequently.

The workaround is to umount/mount ...

I'm using kernels 2.4.7 and 2.4.14 (both with XFS).

It doesn't seem to be a Linux NFS client problem - as I mentioned above,
SGI IRIX clients have a similar problem if the Linux server
crashes/reboots.

James Pearson

David Ford wrote:
> 
> After rebooting my NFS server, the clients can no longer access the mounts.
> 
> A trimmed df shows:
> 
> james:/home/james            0         1         0   0% /home/james
> james:/home/hnc              0         1         0   0% /home/hnc
> 
> # su - xyz
> su: warning: cannot change directory to /home/james/x/xyz: Permission denied
> bash: /home/james/x/xyz/.bash_profile: Permission denied
> 
> However:
> 
> # rpcinfo -p james
>    program vers proto   port
>     100000    2   tcp    111  portmapper
>     100000    2   udp    111  portmapper
>     100005    1   udp  10000  mountd
>     100005    1   tcp  10000  mountd
>     100005    2   udp  10000  mountd
>     100005    2   tcp  10000  mountd
>     100005    3   udp  10000  mountd
>     100005    3   tcp  10000  mountd
>     100003    2   udp   2049  nfs
>     100003    3   udp   2049  nfs
>     100021    1   udp  10001  nlockmgr
>     100021    3   udp  10001  nlockmgr
>     100021    4   udp  10001  nlockmgr
>     100024    1   udp  10002  status
>     100024    1   tcp  10001  status
> 
> # umount /home/hnc
> # mount /home/hnc
> 
> And the hnc mount is fine again.  After repeating with /home/james, that
> mount is also fine.
> 
> Why do I need to umount and remount?  This is pretty brutal when I need
> to shutdown services so the mounts aren't in use.
> 
> These are 2.4.18+ kernels with nfs utils from about a month ago.
> 
> David
> 
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs