On Wednesday 23 September 2015 11:28:53 Timothy Pearson wrote:
Greetings;
I have a weird problem in that I seem to be able to access the remote machine, except for the most important directory on it, /home. An ls /net/machine/home ls: cannot access /net/shop/home: Stale NFS file handle
Expected this sudo ls /net/shop/root permission denied
But every other actually exists on the drive directory is ls'able. I've restarted all the nfs related stuff, everything but rebooted this machine.
Subject says it all. I need to find the experts.
Cheers, Gene Heskett
"There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page http://geneslinuxbox.net:6309/gene
Aside from the usual cricket havens (kernel mailing lists, where no one seems able to answer your questions ;-)) you might try the Arch Linux boards of all places. There are a lot of knowledgeable people there, and if you can distill the issue down enough you might get by even though you are using a different distro. :-)
That said, stale handle normally means the client has been disconnected from the server without knowing why; since you can access other directories on that server I'd be looking at: 1.) permissions on the server side
Define "server" please Timothy. I am under the impression that any machine with an /etc/exports file is the "server" at that instant. On GO704: drwxr-xr-x 3 root root 4096 Jun 21 15:24 home On lathe: drwxr-xr-x 3 root root 4096 May 8 09:16 home On shop: drwxr-xr-x 5 root root 4096 May 19 10:31 home
Which might be a clue, 2 3's on machines that work, and a 5, plus a shorter line format on the machine that doesn't. All installed from the same dvd image.
2.) Stale / broken portmapper / RPC services
Which I can force reinstall...
3.) Any firewalls between the two boxes, possibly blocking only certain ports
None.
If it isn't any of the easy things like that you're going to have to use Wireshark and get packet traces.
Tim
Twasn't installed, is now, gave me hell for running it as root (sudo) but won't trace eth0, no perms, if I don't. I let it capture about 500 packets including a couple directory listings on "shop", but even though I expanded every interchange between here and shop, that isn't a thing there to identify that fact that I am trying to do, or just did, a directory listing. So I can't connect what I'm seeing in the capture compared to what I typed and received a response to in a different workspace/terminal.
IOW, I am lost. BTDT, several times now. ;-)
I have to assume the man page will tell me what to do, so I'll see if I can suss it out.
A query on the debian list made last night has so far been ignored. And I am not subbed to the arch list, but it sounds like I should be.
Thank you Timothy.
Cheers, Gene Heskett