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

Hi Mike,

Thanks for the reply.

--- In nslu2-linux@yahoogroups.com, "Mike Westerhof (mwester)" <mwester@...> wrote:
>
> >
> > I see in dmesg....
> >
> > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> > RPC: Registered udp transport module.
> > RPC: Registered tcp transport module.
> > Installing knfsd (copyright (C) 1996 okir@...).
> > NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
> > NFSD: unable to find recovery directory /var/lib/nfs/v4recovery
> > NFSD: starting 90-second grace period
> >
> Red herring. SlugOS 5.3 doesn't do NFS v4 (it supports V3 and V2), so
> this message is just noise (we probably should have disabled V4 support
> altogether, but the effort to do so didn't seem worth the time, since
> it's just a cosmetic message).

Ok, duly ignored.

> There's no lock involved; there is no state maintained for NFS mounts
> themselves (and there's actually no locking maintained unless you are
> running the lockd, but even so it won't prevent a mount from happening).
>
> Look for a permissions issue. I would wonder if, at the time your
> exports are being processed, those mount points in /mnt are actually
> mounted yet?

I've tried restarting the nfsserver on the slug and still get the same error, and the file systems are mounted...

root@slug:/var/log# df -h
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 6400 5472 928 86% /initrd
/dev/sdb3 9843308 2935996 6407292 31% /
/dev/sdb3 9843308 2935996 6407292 31% /dev/.static/dev
udev 2048 60 1988 3% /dev
/dev/sdb1 241116 173813 54855 76% /mnt/backup
/dev/sdb5 9841097 6499703 2841373 70% /mnt/portage
/dev/sdb6 109969760 81428728 22954832 78% /mnt/torrents
/dev/sdb7 109969760 30633912 73749648 29% /mnt/albums
/dev/sda1 196870980 155003496 31867024 83% /mnt/music
/dev/sda2 98435476 87451408 5983840 94% /mnt/video
/dev/sda3 98435476 93433356 1892 100% /mnt/pics
/dev/sda5 19694836 14750992 3943400 79% /mnt/doc
/dev/sda6 19694836 3840028 14854364 21% /mnt/work1
/dev/sda7 29538432 6120760 21917204 22% /mnt/work2
/dev/sda8 18050192 3529108 13604176 21% /mnt/ref
tmpfs 15120 0 15120 0% /var/volatile
tmpfs 15120 0 15120 0% /dev/shm

I thought I'd check from my laptop and I get...

mount.nfs: mount to NFS server 'slug:/mnt/ref' failed: RPC Error: Program not registered

So I set about checking that RPC was running properly on the slug and could be seen from the client(s).

On the slug I get...

root@slug:/var/log# 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

On the clients I get the same information...

# 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.

So I'm still stumped by this unfortunately.

Cheers

Neil