What do you do when you want to unmount a volume, but its BUSY by some nonexistant process?
I had a USB drive mounted and the drive went into suspend. It doesn't wake up properly with this kernel and unmounting hangs the command line. Syncing hangs too. Unmounting with the -f option tells me umount is also busy?!
root@dattaway dattaway # umount /v -f
umount2: Device or resource busy umount: /v: device is busy
root@dattaway dattaway # fuser /v /v:
The only thing I know how to do at this point is to guess and start killing processes all the way to init. There has to be a better way.
-=Duane http://dattaway.org
I have had this happen before too, with a USB pen drive. The only suggestion I have is that if you are in X-windows [gnome, kde, etc. etc.], shut it down (this will reduce the number processes and in my case kill the process that was making the USB pen drive "busy"). Once X has quit, try the umount command again. Not a scientific solution, but a "it worked for me one time" suggestion.
-Chris
On Sun, 9 Jan 2005 13:41:29 -0600 (CST), Duane Attaway [email protected] wrote:
What do you do when you want to unmount a volume, but its BUSY by some nonexistant process?
I had a USB drive mounted and the drive went into suspend. It doesn't wake up properly with this kernel and unmounting hangs the command line. Syncing hangs too. Unmounting with the -f option tells me umount is also busy?!
root@dattaway dattaway # umount /v -f
umount2: Device or resource busy umount: /v: device is busy
root@dattaway dattaway # fuser /v /v:
The only thing I know how to do at this point is to guess and start killing processes all the way to init. There has to be a better way.
-=Duane http://dattaway.org _______________________________________________ Kclug mailing list [email protected] http://kclug.org/mailman/listinfo/kclug
Duane Attaway wrote:
What do you do when you want to unmount a volume, but its BUSY by some nonexistant process?
I had a USB drive mounted and the drive went into suspend. It doesn't wake up properly with this kernel and unmounting hangs the command line. Syncing hangs too. Unmounting with the -f option tells me umount is also busy?!
root@dattaway dattaway # umount /v -f
umount2: Device or resource busy umount: /v: device is busy
root@dattaway dattaway # fuser /v /v:
The only thing I know how to do at this point is to guess and start killing processes all the way to init. There has to be a better way.
Does lsof work? It probably uses the same method as fuser, but it's worth a shot. You could also look in /proc/[0-9]*/fd/ for any links pointing to /v.
I was trying to test four modems on a USB Serial Adaptor Friday by using minicom, and had a number of problems that caused minicom to lock up. For some reason, one instance locked and could not be killed, maintaining a lock on the port and occupying the VC it was running on. I eventually rebooted to correct it.
(I eventually figured out that minicom would only address /dev/usb/tts/0, no matter which port I set it to in it's config file.)
-
Christopher Kanaan -
Duane Attaway -
Gerald Combs -
Jonathan Hutchins