"Device Is Busy" when unmounting devices ARRRGH

[sakiZ]

OK, I finally got my old zip drive working and recognized.

And I even got my Fuji FinePix 2300 camera to be recognized as a simple USB storage device. I can download my pics and everything. (That was a revelation!!!)

BUT! How do I unmount and or "refresh" these devices when I want to

1. eject, and put in a new zip disk

OR

2. change memory cards in the camera so that it sees a fresh one? I mean, I will typically use more than one memory card on a trip or photo shoot

When I do: umount /mnt/zip OR umount /dev/sdb4

I get "device is busy". And I can't even manually eject the disk by pressing the eject button.

THE CAMERA:

If I do: umount /mnt/camera

I again get "device is busy".

This prevents me from changing out memory cards.

What's the trick here? How do unmount these things?

sakiZ

[firebyrd10]

I find that sometimes opening a file in konqueror helps.

If nothing else works try a lazy -l unmount. The shows it as not being mounted, but programs useing it can still access it and it could cause corruption. Just wait a little bit, then try to remove.

[gnarvaja]

I find that sometimes opening a file in konqueror helps.
Konqueror leaves some open handles (do a top after using konqueror on a mounted directory) that prevents umounting devices. I usually use:

umount -f /<rebel directory> to force the unmount. You have to make sure that there is no other software is using the device. Such distraction can corrupt the filesystem on the device you are trying to unmount. For example, saving configuration files when you shutdown Knoppix.

--GN

[sakiZ]

Umount -f !!!

I'm going to have to buy that Hack Knoppix book. I assume this kind of info is in it.

sakiZ

[firebyrd10]

umount -f /<rebel directory> to force the unmount. --GN


I've found that even that doesn't work sometimes, it just won't unmounmt.


What is doing a top?

[OErjan]

top is a prosess/mem... monitoring tool. it displays what program uses how much memory and cpu, what pid it has (process id, the one you use too kill things)...

[markpreston]

Once you have finished downloading or copying your photo files you need to change back out of the /mnt/camera and /mnt/zip
directories, and close any programs such as konqueror that may be allowing you to view the files. Once this has been done I would expect the umount commands to work, without the -f. Then you can change the memory card and mount the new one.
Regards,
Mark

[gnarvaja]

Once you have finished downloading or copying your photo files you need to change back out of the /mnt/camera and /mnt/zip
directories, and close any programs such as konqueror that may be allowing you to view the files. Once this has been done I would expect the umount commands to work, without the -f. Then you can change the memory card and mount the new one.
When using Konqueror check the following setting:


1. Select Settings -> Configure Konqueror
2. Select the 'Performance' icon at the bottom
3. Make sure that in the preloading sections, the number of preloaded instances is 0

This way you make sure that Konqueror *really* closes and frees any resouorces it might hold, particularly mounted devices.

top is a pretty ps -ef

--GN

[rrfish72]

I don't know much about #1 but I have a zip and I have to wait for it to stop spinning and then it works great. If I mount it right away then everything works properly even if it is still spinning/working. Never had any problem with a busy zip. Need more info to help.

[gnarvaja]

I don't know much about #1 but I have a zip and I have to wait for it to stop spinning and then it works great. If I mount it right away then everything works properly even if it is still spinning/working. Never had any problem with a busy zip. Need more info to help.
I had the problem with USB / PCMCIA flash drives too. By removing the memory cards/sticks too soon or with unsuccesful umounts I ended with corrupted files. Konqueror is not the only offender, but since I changed the setting I don't have the problem as often.

--GN