On Sat, 24 May 2014 15:55:47 -0700 Michael Ewan <[email protected]> dijo:
>On 5/24/2014 12:50 PM, John Jason Jordan wrote: >> Now that I have the problem resolved, I'd like to figure out how to >> stop it from happening again. From my dim understanding of what I >> read about this error message on the net, apparently it happens when >> the server changes a file on the share. The server (the laptop) is >> constantly accessing files on the share because some are distros >> that I continue to seed with the laptop. But this is the first time >> the "Stale NFS Handle" error happened, even though I have been >> seeding for ages. In other words, just accessing the files must not >> be enough to trigger the error. >With NFS the server and multiple clients can change files, however the >server many not dismount/remount the physical file system with >affecting the clients. Dismounting the physical file system will >change the NFS handle which any active clients detect. The client >will refuse to do anything because it has a stale map of where files >are on the file system. Usually just unmount/remount on the client >will fix this, so there was something seriously amiss on your server. >Check your logs to see if the server had unmounted the file system due >to errors. The drive in question is a 3 TB USB drive connected to the laptop (the server). It does get unmounted and remounted once or twice a month when I go somewhere and take the laptop with me, as the drive stays at home disconnected. When I return I plug it in and remount it. Then I launch my bittorrent client (Ktorrent) and it continues seeding as it was when the drive was disconnected from the laptop. I have done this numerous times, the most recent being last Sunday when I took the laptop with me to the Clinic. Friday was the first time I tried to access the share from the desktop since Sunday, so it is possible that the current problem was caused by unmounting and remounting the drive then, but I swear I have done so many times in the past and it did not affect the share. Also note that the laptop was shut down and rebooted, once when going to the Clinic and yet again on returning home. I assume this would restart the NFS service. But note also that the share that the desktop connects to is the entire /media folder on the laptop, not just the drive itself. After much head-scratching and advice from here I learned that you cannot share a removable drive; it must be a permanent folder. It is not a problem for me, and I doubt that this is the cause of the current error message, but I mention it just in case it is part of the problem. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
