can't unmount devices
I'm having this problem with on two machines, both SuSE 8.2. I'll put in a zip disk or a cd or a floppy, and when I'm ready to unmount it, sometimes it won't let me. It gives me this error; Could not unmount device. The reported error was: umount: /media/cdrom: device is busy I look in the process table and can't find anything related to the device in question, I try browsing to different folders to make sure it doesn't still think I'm looking at the mounted drive. I've also tried just waiting a while to see if the system figures it out on it's own. When this happens, the only way to get the disc out is to restart. -- Allen Seelye Aseelye@blackfoot.net Happiness is not the absence of conflict but the ability to cope with it.
On Tue, 2003-12-02 at 10:32, Allen Seelye wrote:
I'm having this problem with on two machines, both SuSE 8.2. I'll put in a zip disk or a cd or a floppy, and when I'm ready to unmount it, sometimes it won't let me. It gives me this error;
Could not unmount device. The reported error was: umount: /media/cdrom: device is busy
Try using lsof /media/cdrom to see what process still is using the device. -- Marshall "Nothing is impossible, we just do not have all the answers to make the impossible, possible."
* Allen Seelye <aseelye@blackfoot.net> [12-02-03 10:38]:
I'm having this problem with on two machines, both SuSE 8.2. I'll put in a zip disk or a cd or a floppy, and when I'm ready to unmount it, sometimes it won't let me. It gives me this error;
Could not unmount device. The reported error was: umount: /media/cdrom: device is busy
I look in the process table and can't find anything related to the device in question, I try browsing to different folders to make sure it doesn't still think I'm looking at the mounted drive. I've also tried just waiting a while to see if the system figures it out on it's own. When this happens, the only way to get the disc out is to restart.
If you were accessing the drive with konq, you need to look for a kinit process that was initiated when you accessed the drive and kill it. This is common. A solution would be to use krusader or fr or mc or command-line to access the cd/floppy/zip. When you leave the device, the device is released. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org
Allen, You've gotten a couple of high-tech answers...let me try a lower-tech approach. And pardon me if you've already considered the following... I've experienced the same problem on several distros -- Mandrake, Red Hat, and SuSE 9.0. In my case, it happens because: a. I'm transferring large files or large numbers of files and the directory from which I'm transferring shows empty, while they appear in on the outboard drive. So I try to unmount, forgetting that the files may not have fully crossed to the outboard drive yet. or b. I have a minimized terminal window, file manager, or app that is set to the drive I'm trying to unmount, and I've either momentarily forgotten to shut the program down or >cd .. back up to a higher level directory. Thus, when I get those kinds of unmount messages, those are the first two things I check. Best, Pete -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Peter N. Spotts Science and technology correspondent | The Christian Science Monitor One Norway Street, Boston MA 02115 Office: 617-450-2449 | Office in Home: 508-520-3139 pspotts@alum.mit.edu | www.csmonitor.com | www.peterspotts.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On Tuesday 02 December 2003 17:09, Peter N. Spotts wrote:
Allen,
You've gotten a couple of high-tech answers...let me try a lower-tech approach. And pardon me if you've already considered the following...
Or another low tech approach. KDE has a setting to help speed up Konq. It loads at least one instance of Konq in the background, and holds it there so that when you do make a call to Konq it appears quicker... or so the theory goes. You'll find this setting buried in the KDE Control Centre. I've found that if you set this to zero, the problem you've described goes away. My theory is that somehow the mount to floppy or CDROM gets attached to this phantom preloaded background instance of Konq. When you try to unmount the device, you can't because when umount checks the device it sees that Konq is still connected to the device. When it sees this it bounces back the "Cannot unmount device. Device busy" message. C.
I've experienced the same problem on several distros -- Mandrake, Red Hat, and SuSE 9.0. In my case, it happens because:
a. I'm transferring large files or large numbers of files and the directory from which I'm transferring shows empty, while they appear in on the outboard drive. So I try to unmount, forgetting that the files may not have fully crossed to the outboard drive yet.
or
b. I have a minimized terminal window, file manager, or app that is set to the drive I'm trying to unmount, and I've either momentarily forgotten to shut the program down or >cd .. back up to a higher level directory.
Thus, when I get those kinds of unmount messages, those are the first two things I check.
Best,
This did the trick. It's under performance in konq settings. I set the nomuber of preloads to '0' and it seems to have gone away. Thanks! On Tuesday 02 December 2003 12:59 pm, Clayton wrote:
On Tuesday 02 December 2003 17:09, Peter N. Spotts wrote:
Allen,
You've gotten a couple of high-tech answers...let me try a lower-tech approach. And pardon me if you've already considered the following...
Or another low tech approach. KDE has a setting to help speed up Konq. It loads at least one instance of Konq in the background, and holds it there so that when you do make a call to Konq it appears quicker... or so the theory goes. You'll find this setting buried in the KDE Control Centre.
I've found that if you set this to zero, the problem you've described goes away. My theory is that somehow the mount to floppy or CDROM gets attached to this phantom preloaded background instance of Konq. When you try to unmount the device, you can't because when umount checks the device it sees that Konq is still connected to the device. When it sees this it bounces back the "Cannot unmount device. Device busy" message.
C.
I've experienced the same problem on several distros -- Mandrake, Red Hat, and SuSE 9.0. In my case, it happens because:
a. I'm transferring large files or large numbers of files and the directory from which I'm transferring shows empty, while they appear in on the outboard drive. So I try to unmount, forgetting that the files may not have fully crossed to the outboard drive yet.
or
b. I have a minimized terminal window, file manager, or app that is set to the drive I'm trying to unmount, and I've either momentarily forgotten to shut the program down or >cd .. back up to a higher level directory.
Thus, when I get those kinds of unmount messages, those are the first two things I check.
Best,
-- Allen Seelye Aseelye@blackfoot.net Happiness is not the absence of conflict but the ability to cope with it.
participants (5)
-
Allen Seelye -
Clayton -
Marshall Heartley -
Patrick Shanahan -
Peter N. Spotts