by Hello, I'm having some NFS problems which result in the error in the
subject line.
I'm running Linux on a P-90 with a 3Com 3c509 ethernet card.
I have been trying to mount a disk "-t nfs" over ethernet at work.
My mount command shows the following:
/dev/hda2 on / type ext2 (rw)
/dev/hda1 on /dosc type msdos (rw)
none on /proc type proc (rw)
The disk I want to mount is called "/export/home" on a machine called
"vader." Sometimes I am only able to mount it for A SINGLE ACCESS.
Afterwards, the mount remains, but I am no longer able to access it.
dave fred george
stuff in home
That was how /home was supposed to look.
Then, some time later...
/home has disappeared!
/dev/hda2 on / type ext2 (rw)
/dev/hda1 on /dosc type msdos (rw)
none on /proc type proc (rw)
vader:/export/home on /home type nfs (rw,addr=192.83.225.35)
Hmmm... NFS thinks it's still there!
can't create lock file /etc/mtab~: File exists
oops.
mount clntudp_create: RPC: Port mapper failure - RPC: Unable to send
No matter what I do, until I boot linux again I get this same RPC
error. I have tried killing rpc.nfsd and re-statring it, and this
SOMETIMES works. I have tried dmesg, and this is what I see
NFS: notice message: result=-11
nfs_statfs: statfs error = 11
NFS: notice message: result=-11
nfs_statfs: statfs error = 11
NFS: notice message: result=-11
nfs_statfs: statfs error = 11
NFS: notice message: result=-11
nfs_statfs: statfs error = 11
etc. etc. etc.
How can I get NFS to mount robustly? Why should I be able to access
the mount once or twice before I start getting errors?
Thanks for any advice you can give me,
Dave