So, I’ve got a mount point that is used by a backup script, it seems that this script has been mounting the remote device via samba and not unmounting (umount) it at the end of it’s task. Now the server has it’s knickers well and truely in a knot. I know a good old fashioned reboot will sort it out, but I don’t want to do that.
umount as a normal user returns
[code]umount: it seems /mnt/o is mounted multiple times[/code]
When run as root it returns (6 times)
[code]umount: /mnt/o: device is busy[/code]
Which would suggest that I’m either CD’ed into it, or the backup program is still running, many times.
So, after killing off all terminals in use (in case anyone is in a folder on the mount) it still won’t damn umount. Trying to work out how to restart the ssh daemons and ftp ones in case that’s the issue.
The command smbumount raised my hopes briefly, but gives the same errors. I think I’ve got to deal with the device actually being busy first! Typing fuser seems to suggest no users are using the device, odd.
[code]fuser -u /mnt/o[/code]
So fiddling around I run it wuthout the user flag at get back
[code]/mnt/o: 25257[/code]
Aha, a PID of someone using it! It’s me! In the current terminal that I’m in at the moment! Oh crap! So, log out, log back in. Run it again. The fuser command now tells me nothing again, but I still can’t unmount. Also, lsof doesn’t reveal any files using anything under /mnt/o or just /mnt.
Hmm, in another act of random desparation I type
[code]fuser -mk /mnt/[/code]
Which kills of half my open windows and process, but does indeed free up the drive. I’m not really sure about it, so really wouldn’t recommend it!
Not a job well done…
Home > About This Post
This entry was posted by Chris Andrews on Wednesday, January 17th, 2007, at 4:07 pm, and was filed in Technical.
Subscribe to the
RSS 2.0 feed for all comments to this post.
Post a Comment