Steve Fosdick wrote:
So what has happenned here is that Linux thinks the remote windows filesystem is still mounted and therefore it doesn't flush the names on that filesystem from internal caches, hence why some names on that filesystem look to be still there - when you try to open one of the files or get more information on it though Linux tries to re-connect to the windows machine and finds it doesn't respond.
So, to stop the errors you either need to tell Linux you don't need access to that filesystem any more by umounting it, or startup the windows box again so Linux can see it.
Thanks, Steve....that makes sense. However I can't unmount as it thinks the share is busy, and I did restart the windows - is there any way i can manually flush the names on the internal cache? Thanks, Jenny.
On Sat, 16 Feb 2002 12:43:24 Jenny_Hopkins@toby-churchill.com wrote:
Thanks, Steve....that makes sense. However I can't unmount as it thinks the share is busy, and I did restart the windows - is there any way i can manually flush the names on the internal cache? Thanks, Jenny.
In Linux, when you try to umount a filesystem and Linux says it's busy that means that a Linux program has a file open on the filesystem concerned. Often this is a program which was started with it's current directory on that filesystem.
Have a look at the fuser command which can tell you which processes have files open on a filesystem so you can close them down or kill them off. Once you have no Linux processes with files open on the filesystem then you should be able to umount it.
Steve.