linuxgeek: [nslu2-linux] Re: NFSD: unable to find recovery directory /var/lib/nfs/v4recovery

--- In nslu2-linux@yahoogroups.com, "Mike Westerhof (mwester)" <mwester@...> wrote:
>
> slackline wrote:
> > # rpcinfo -p slug
> > program vers proto port
> > 100000 2 tcp 111 portmapper
> > 100021 1 udp 47279 nlockmgr
> > 100021 3 udp 47279 nlockmgr
> > 100021 4 udp 47279 nlockmgr
> > 100003 2 udp 2049 nfs
> > 100003 3 udp 2049 nfs
> > 100003 4 udp 2049 nfs
> > 100021 1 tcp 48775 nlockmgr
> > 100021 3 tcp 48775 nlockmgr
> > 100021 4 tcp 48775 nlockmgr
> > 100003 2 tcp 2049 nfs
> > 100003 3 tcp 2049 nfs
> > 100003 4 tcp 2049 nfs
> > 100000 2 udp 111 portmapper
> >
> > Which suggests to me that things can be seen on the slug server fine. I've tried restarting the nfs mounts on the clients and server in turn, but no joy at all.
> I don't think they can be seen fine -- where's your mountd? The
> nfsserver startup script (in /etc/init.d) starts the /usr/sbin/mountd
> daemon -- your's isn't there in the rpc listing. If you can figure out
> where it went, or why it isn't starting, you'll have a good idea what's
> going on.
>

Nail hit on the head!

I've no idea why, as I'd restarted it several times, but this time I got...

# /etc/init.d/nfsserver restart
stopping mountd: done
stopping statd: done
starting mountd: done
starting statd: done
# rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100021 1 udp 47279 nlockmgr
100021 3 udp 47279 nlockmgr
100021 4 udp 47279 nlockmgr
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100021 1 tcp 48775 nlockmgr
100021 3 tcp 48775 nlockmgr
100021 4 tcp 48775 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100000 2 udp 111 portmapper
100005 1 udp 44299 mountd
100005 1 tcp 52699 mountd
100005 2 udp 44299 mountd
100005 2 tcp 52699 mountd
100005 3 udp 44299 mountd
100005 3 tcp 52699 mountd
100024 1 udp 36316 status
100024 1 tcp 48092 status

I can now mount from the laptop where I was getting "RPC Error: Program not registered", but strangely still get the permission denied error from my desktop despite being able to see the slug running with mountd...

# /etc/init.d/netmount restart
* Caching service dependencies ... [ ok ]
* Unmounting network filesystems ... [ ok ]
* Mounting network filesystems ...
mount.nfs: access denied by server while mounting slug:/mnt/torrents
mount.nfs: access denied by server while mounting slug:/mnt/albums
mount.nfs: access denied by server while mounting slug:/mnt/music
mount.nfs: access denied by server while mounting slug:/mnt/video
mount.nfs: access denied by server while mounting slug:/mnt/pics
mount.nfs: access denied by server while mounting slug:/mnt/doc
mount.nfs: access denied by server while mounting slug:/mnt/work1
mount.nfs: access denied by server while mounting slug:/mnt/work2
mount.nfs: access denied by server while mounting slug:/mnt/ref
* Could not mount all network filesystems [ !! ]
darwin pics # rpcinfo -p slug
program vers proto port service
100000 2 tcp 111 portmapper
100021 1 udp 47279 nlockmgr
100021 3 udp 47279 nlockmgr
100021 4 udp 47279 nlockmgr
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100021 1 tcp 48775 nlockmgr
100021 3 tcp 48775 nlockmgr
100021 4 tcp 48775 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100000 2 udp 111 portmapper
100005 1 udp 44299 mountd
100005 1 tcp 52699 mountd
100005 2 udp 44299 mountd
100005 2 tcp 52699 mountd
100005 3 udp 44299 mountd
100005 3 tcp 52699 mountd
100024 1 udp 36316 status
100024 1 tcp 48092 status

The /etc/fstab entries are identical between the two....

### NSLU2 under SlugOSBE
## /media/sda (250Gb)
#slug:/mnt/portage /usr/portage nfs auto,rw,users 0 0
slug:/mnt/torrents /mnt/slug/torrents nfs auto,rw,users 0 0
slug:/mnt/albums /mnt/slug/albums nfs auto,rw,users 0 0
## /mnt/sdb (500Gb)
slug:/mnt/music /mnt/slug/music nfs auto,rw,users 0 0
slug:/mnt/video /mnt/slug/video nfs auto,rw,users 0 0
slug:/mnt/pics /mnt/slug/pics2 nfs auto,rw,users 0 0
slug:/mnt/doc /mnt/slug/doc nfs auto,rw,users 0 0
slug:/mnt/work1 /mnt/slug/misc nfs auto,rw,users 0 0
slug:/mnt/work2 /mnt/slug/work nfs auto,rw,users 0 0
slug:/mnt/ref /mnt/slug/ref nfs auto,rw,users 0 0

...whilst the /etc/exports on the server obviously doesn't vary...

# more /etc/exports
# /etc/exports: NFS file systems being exported. See exports(5).
## 250Gb LaCie
## pics1
/mnt/torrents 192.168.1.0/255.255.255.0(rw,async,subtree_check)
## music1
/mnt/albums 192.168.1.0/255.255.255.0(rw,async,subtree_check)
## 500Gb LaCie
## music2
/mnt/music 192.168.1.0/255.255.255.0(rw,async,subtree_check)
## video
/mnt/video 192.168.1.0/255.255.255.0(rw,async,subtree_check)
## pics2
/mnt/pics 192.168.1.0/255.255.255.0(rw,async,subtree_check)
## doc
/mnt/doc 192.168.1.0/255.255.255.0(rw,async,subtree_check)
## misc
/mnt/work1 192.168.1.0/255.255.255.0(rw,async,subtree_check)
## work
/mnt/work2 192.168.1.0/255.255.255.0(rw,async,subtree_check)
## ref
/mnt/ref 192.168.1.0/255.255.255.0(rw,async,subtree_check)

Its strange that an improper power-cycle has wrecked such havoc!

Thank you very much for your suggestions so far, feels very close now.

Neil