kmc77 Posted June 20, 2004 Report Share Posted June 20, 2004 (edited) I know I saw a post on this a week or two ago, but I can't find it. Occasionaly when I try to unmount my USB HD, I get a "device busy" message. Please excuse me asking the question again, but I can't get the dang thing unmounted tonight. Normally I just wait an hour, and it's not busy anymore, but It's been on for 5 hours now, and still busy. How do I find out what it's busy doing, and how do I kill it when I find out? Edited June 20, 2004 by kmc77 Quote Link to comment Share on other sites More sharing options...
kmc77 Posted June 20, 2004 Author Report Share Posted June 20, 2004 Does anyone at least know the thread I'm talking about? Thing has been on for like 10 hours now. Quote Link to comment Share on other sites More sharing options...
VeeDubb Posted June 20, 2004 Report Share Posted June 20, 2004 I'm affraid I haven't a clue what post, but I had the same problem once with /dev/cdrom. Turned out i had /mnt/cdrom open in a konqeror window on desktop 2 and it wouldn't let me unmount untill I closed it. Quote Link to comment Share on other sites More sharing options...
streeter Posted June 20, 2004 Report Share Posted June 20, 2004 "lsof | grep mountpoint_of_your_HD" will tell you which files are open and the PID. Then kill <PID> if you need to Could try umount -f /dev/whatever Quote Link to comment Share on other sites More sharing options...
kmc77 Posted June 20, 2004 Author Report Share Posted June 20, 2004 [root@kevins kevin]# umount -f /mnt/usbhd umount2: Device or resource busy umount: /dev/scsi/host1/bus0/target0/lun0/part1: not mounted umount: /mnt/usbhd: Illegal seek umount2: Device or resource busy umount: /mnt/usbhd: device is busy No luck with umount -f [root@kevins kevin]# lsof | grep /dev/scsi/host1/bus0/target0/lun0/part1 bash: lsof: command not found or with lsof | grep The dang thing's still running Quote Link to comment Share on other sites More sharing options...
kmc77 Posted June 20, 2004 Author Report Share Posted June 20, 2004 Success! I found what I was looking for in one of aru's old FAQ's. This one to be exact. Thanks aru. [root@kevins kevin]# fuser -vm /mnt/usbhd This shows the offending process [root@kevins kevin]# fuser -km /mnt/usbhd This kills the offending process In case any one was wondering, I got a little trigger happy and used the kill process command before I checked it, so I don't know what was tying things up. Thanks for the help all. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.