fuzzylizard Posted February 26, 2003 Report Share Posted February 26, 2003 When I try to access one of my directories on a fat32 mounted partition I keep getting this error: ls: .: Stale NFS file handle As far as I know, that directory is not NFS. At least I have never set it up as such. If I use konquerer, I have no trouble accessing the directory, but I can't get at it through bash. Any ideas? Quote Link to comment Share on other sites More sharing options...
aru Posted February 26, 2003 Report Share Posted February 26, 2003 how is that partiton mounted? post your fstab file. does that happens always? what other applications are accesing at the same time that directory? (run "lsof | grep directory_name" as root when the error happens again to get that info). And the same partition? are you using nfs or portmap? Quote Link to comment Share on other sites More sharing options...
fuzzylizard Posted February 26, 2003 Author Report Share Posted February 26, 2003 Thanks for the help how is that partiton mounted? post your fstab file. Here is what my fstab says. /dev/hda5 /mnt/data vfat iocharset=iso8859-1,codepage=850,umask=0 0 0 does that happens always? No, this is the first time what other applications are accesing at the same time that directory? (run "lsof | grep directory_name" as root when the error happens again to get that info). And the same partition? The applications that I was running at the time were: emacs - reading files directly from the directory anjuta - same as emacs mozilla (no access to that partition though) xmms - reading mp3 files off the /mnt/data partition amsn, gkrellm are you using nfs or portmap? No, not that I know of. I just checked the directory again and I once again have complete access to it. Very strange. :? :? :? Quote Link to comment Share on other sites More sharing options...
Cannonfodder Posted February 26, 2003 Report Share Posted February 26, 2003 I had that happen too (few days ago) , but I opened a new console and closed the old one and that took care of it.. Quote Link to comment Share on other sites More sharing options...
fuzzylizard Posted February 26, 2003 Author Report Share Posted February 26, 2003 At the time of the error, I tried that and it did not go away. :( It's gone now, hopefully it will stay that way. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.