how can I (really) force a umount?

  • Follow


I'm connecting to a couple of shares on an XP Pro workstation - not a 
good idea, I know, but it's convenient in this case except:

sometimes the XP workstation gets rebooted while the shares are 
connected. After that, I can't disconnect them and I can't reconnect 
them. This creates a real problem because some programs (esp. under 
wine) seem to read the full /mnt folder so they take forever.

I've tried umount //server/share --force as root but it doesn't work. I 
get 4 or 5 error messages telling me things like the device is busy, etc..

Any solutions?
0
Reply Gary 11/15/2004 3:24:57 PM

On Mon, 15 Nov 2004 10:24:57 -0500, Gary Dale wrote:

> I'm connecting to a couple of shares on an XP Pro workstation - not a 
> good idea, I know, but it's convenient in this case except:
> 
> sometimes the XP workstation gets rebooted while the shares are 
> connected. After that, I can't disconnect them and I can't reconnect 
> them. This creates a real problem because some programs (esp. under 
> wine) seem to read the full /mnt folder so they take forever.
> 
> I've tried umount //server/share --force as root but it doesn't work. I 
> get 4 or 5 error messages telling me things like the device is busy, etc..
> 
> Any solutions?

see man lsof

lsof
kill processes holding drive/mount point
umount



0
Reply Baho 11/15/2004 11:54:50 PM


Baho Utot wrote:
> On Mon, 15 Nov 2004 10:24:57 -0500, Gary Dale wrote:
> 
> 
>>I'm connecting to a couple of shares on an XP Pro workstation - not a 
>>good idea, I know, but it's convenient in this case except:
>>
>>sometimes the XP workstation gets rebooted while the shares are 
>>connected. After that, I can't disconnect them and I can't reconnect 
>>them. This creates a real problem because some programs (esp. under 
>>wine) seem to read the full /mnt folder so they take forever.
>>
>>I've tried umount //server/share --force as root but it doesn't work. I 
>>get 4 or 5 error messages telling me things like the device is busy, etc..
>>
>>Any solutions?
> 
> 
> see man lsof
> 
> lsof
> kill processes holding drive/mount point
> umount

   fuser -k path
is even better
0
Reply Mihai 11/16/2004 8:14:14 PM

Mihai Osian wrote:
> Baho Utot wrote:
> 
>> On Mon, 15 Nov 2004 10:24:57 -0500, Gary Dale wrote:
>>
>>
>>> I'm connecting to a couple of shares on an XP Pro workstation - not a 
>>> good idea, I know, but it's convenient in this case except:
>>>
>>> sometimes the XP workstation gets rebooted while the shares are 
>>> connected. After that, I can't disconnect them and I can't reconnect 
>>> them. This creates a real problem because some programs (esp. under 
>>> wine) seem to read the full /mnt folder so they take forever.
>>>
>>> I've tried umount //server/share --force as root but it doesn't work. 
>>> I get 4 or 5 error messages telling me things like the device is 
>>> busy, etc..
>>>
>>> Any solutions?
>>
>>
>>
>> see man lsof
>>
>> lsof
>> kill processes holding drive/mount point
>> umount
> 
> 
>   fuser -k path
> is even better


Gives me an Input/Output error.
0
Reply Gary 11/19/2004 4:51:54 AM


Baho Utot wrote:
> On Mon, 15 Nov 2004 10:24:57 -0500, Gary Dale wrote:
> 
> 
>>I'm connecting to a couple of shares on an XP Pro workstation - not a 
>>good idea, I know, but it's convenient in this case except:
>>
>>sometimes the XP workstation gets rebooted while the shares are 
>>connected. After that, I can't disconnect them and I can't reconnect 
>>them. This creates a real problem because some programs (esp. under 
>>wine) seem to read the full /mnt folder so they take forever.
>>
>>I've tried umount //server/share --force as root but it doesn't work. I 
>>get 4 or 5 error messages telling me things like the device is busy, etc..
>>
>>Any solutions?
> 
> 
> see man lsof
> 
> lsof
> kill processes holding drive/mount point
> umount
> 
> 
> 

gives me a "Warning: can't stat() smbfs file system" /mnt/mntpoint.
0
Reply Gary 11/19/2004 4:53:32 AM

4 Replies
702 Views

(page loaded in 0.076 seconds)

Similiar Articles:













7/23/2012 6:01:52 AM


Reply: