here is the story. i have two boxes on my net. one is my trusty linux debian woody (dist-upgrade to testing) i will call geekazoid. the other is a winxp box (i call frumpy) that i use as a gaming/file storage. frumpy is connect the the lan via WUSB11. i have included an auto connect on boot via fstab from the linux to the winxp share drive. this is mounted in /xp. now my win box was down for 5-6 hours while i was at work (according to my wife) and geekazoid lost the connection. i got frumpy back up and running again and went to geekazoid to check the connection and upon "ls" i got
i tried to umount and received
i know that all i have to do is reboot and the problem is fixed but then that will fsck up my uptime. i am only on 3 days and i would like to see how far i can go. i know that there is a was to kill this connection, there has to be, with all the splender that is linux. if there is more information that anyone needs that i can give i will. can someone help please?

it's messy but just remount the share again. if you then run "mount" you will see the share mounted twice, but other than being nasty looking it will be fine.

thanks acid. i will try that when i get home from work and let you know how it works out.

is there anyway to clean it up??

NFS is a REALLY crappy protocol, it crashes all the time, use random port number during connection and has damn trouble to handle NAT (remember that NFS use ip authentification). Plus it stall any apps trying to use it while crashed (even if you specify SOFT or INTR flag, NFS handle this well half the time anyways).

When it is crashed up (like in your case) often the easier thing to do is reboot (or to swear during thirty min to unlock the damn thing using silly tricks).

I can't give you miracle tricks, try to mount again/umount, try to kill all NFS/RPC deamon, try to restart the NFS server. NFS is just a bad old thing.