SuSE 8.0 -- ncpfs: "Stale NFS file handle" (unable to access "." or ".." -- VFS issue?)
Hi, Has anyone had problems with SuSE 8.0 and mounting NetWare volumes? I didn't have this problem with SuSE 7.2 or SuSE 7.3. (Unfortunately, I only have one SuSE 8.0 machine to test this problem on.) I can successfully mount a volume using ncpmount and I can access everything if I start from the right place. Here is a few commands to demonstrate what I am talking about: (I am connecting to the NetWare server called 'hal' with by username, 'alle_lowe'. BTW: I get the same results if I mount a specific volume (-V) or If I specify no volume.) # ncpmount -S hal -U alle_lowe /NetWare/hal **<password>** I'm now connected to the server. # cd /NetWare/hal # ls ls: .: Stale NFS file handle Accessing "." (the current directory) fails. But, If I access the directory using it's absolute path, then everything works fine: # ls /NetWare/hal chip dev sys Everything here worked as expected; the proper directories are listed. Now lets jump into a subdirectory and look up the VFS tree: # cd /NetWare/hal/chip # ls .. ls: ..: Stale NFS file handle No good! I thought I saw a pattern at this point, so I started to assume that maybe it was choking on relative paths. But then I tried this: # ls ../../hal chip dev sys Which worked. Now, unless I'm missing something here, this would be a relative path that essentially reduces to "..", which failed just a few seconds ago. I think that the term "NFS" in the error message is referring to just a "Network" file system and not the just the "nfs" protocol. I really don't know at what level this message is being produced, but I assume that it is coming from the application. I tried a bunch of other command line tools (echo * (using bash), find, tar,..) and they all had similar results:: Accessing the mounted point using either "." or ".." doesn't work. I believe I can rule out any kind of 'permissions' issues since I can actually access the mount using the absolute path. I also tried the same thing using smbfs and nfs and both worked fine (as expected). I tried different mount point locations, different NetWare users, but I always had the same results. If you can confirm or deny any of these issue on your machine, please drop me a line. Any comments or suggestions are welcomed. Thanks, Lowell Alleman lowella@mfps.com
We had same problem with SUSE 8.0. Updated ncpfs to a later version and still problem. Other SUSE versions (eg 7.2,7.3) OK. Haven't looked at in detail as our test machine is now being used somewhere else. David
-----Original Message----- From: Alleman, Lowell [mailto:lowella@MFPS.COM] Sent: Thursday, 23 May 2002 12:42 To: suse-linux-e@suse.com Subject: [SLE] SuSE 8.0 -- ncpfs: "Stale NFS file handle" (unable to access "." or ".." -- VFS issue?)
Hi,
Has anyone had problems with SuSE 8.0 and mounting NetWare volumes? I didn't have this problem with SuSE 7.2 or SuSE 7.3. (Unfortunately, I only have one SuSE 8.0 machine to test this problem on.)
I can successfully mount a volume using ncpmount and I can access everything if I start from the right place. Here is a few commands to demonstrate what I am talking about: (I am connecting to the NetWare server called 'hal' with by username, 'alle_lowe'. BTW: I get the same results if I mount a specific volume (-V) or If I specify no volume.)
# ncpmount -S hal -U alle_lowe /NetWare/hal **<password>**
I'm now connected to the server.
# cd /NetWare/hal # ls ls: .: Stale NFS file handle
Accessing "." (the current directory) fails. But, If I access the directory using it's absolute path, then everything works fine:
# ls /NetWare/hal chip dev sys
Everything here worked as expected; the proper directories are listed.
Now lets jump into a subdirectory and look up the VFS tree:
# cd /NetWare/hal/chip # ls .. ls: ..: Stale NFS file handle
No good! I thought I saw a pattern at this point, so I started to assume that maybe it was choking on relative paths. But then I tried this:
# ls ../../hal chip dev sys
Which worked. Now, unless I'm missing something here, this would be a relative path that essentially reduces to "..", which failed just a few seconds ago.
I think that the term "NFS" in the error message is referring to just a "Network" file system and not the just the "nfs" protocol. I really don't know at what level this message is being produced, but I assume that it is coming from the application.
I tried a bunch of other command line tools (echo * (using bash), find, tar,..) and they all had similar results:: Accessing the mounted point using either "." or ".." doesn't work.
I believe I can rule out any kind of 'permissions' issues since I can actually access the mount using the absolute path. I also tried the same thing using smbfs and nfs and both worked fine (as expected). I tried different mount point locations, different NetWare users, but I always had the same results.
If you can confirm or deny any of these issue on your machine, please drop me a line. Any comments or suggestions are welcomed.
Thanks,
Lowell Alleman lowella@mfps.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Dear all - I'm trying to set the serial port on a usb hub that has 3 USB ports, a parallel port and a serial port. (Dlink DSB-H3SP/DU-H3SP). When I run lsmod, I see usbserial is loaded. And when I do hwinfo --usb, I see the hub among the usb hardware. I'm trying to use the serial port to connect to my Palm Vx, which has a serial port cradle. I can't figure out how to determine whether the serial port is actually being seen and if it is, what the device name is. I've tried ttyUSB0 - 4, but none of those seem to work. I'm using SuSE 7.3 on a Toshiba laptop that has no serial (or parallel) ports, so I would like to figure out how to get this working. I would appreciate any help on getting this working. Thanks, Harry
participants (3)
-
Alleman, Lowell -
David Milligan -
Harry Reinert