If I get an error saying that a device is busy (like /dev/dvd), how can I tell what 'has' the device and how can I release it in order to unmount it? -- Cheers, Trey --- "There is a theory which states that if ever anyone discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable. There is another which states that this has already happened." --Douglas Adams
On Friday 13 February 2004 02:40 am, Trey Sizemore wrote:
If I get an error saying that a device is busy (like /dev/dvd), how can I tell what 'has' the device and how can I release it in order to unmount it?
the lsof command lists what processes have which files open. look at the man page for more info. Dylan
-- Cheers, Trey ---
"There is a theory which states that if ever anyone discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable.
There is another which states that this has already happened." --Douglas Adams
-- "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -Benjamin Franklin
On Thu, 2004-02-12 at 21:53, Dylan wrote:
the lsof command lists what processes have which files open. look at the man page for more info.
Dylan
Thanks, I'll check it out. Strangely, I was able to unmount shortly thereafter. -- Cheers, Trey --- If there is a sin against life, it consists perhaps not so much in despairing of life as in hoping for another life and in eluding the implacable grandeur of this life. --Albert Camus
fuser fuser -v /data USER PID ACCESS COMMAND /data anders 6986 f.... konqueror anders 9352 ..c.. bash anders 24093 f.... k3b root mount point for kernel /data fuser -k <file> tries to kill the processes accessing <file> fredagen den 13 februari 2004 03.40 skrev Trey Sizemore:
If I get an error saying that a device is busy (like /dev/dvd), how can I tell what 'has' the device and how can I release it in order to unmount it?
Alle 04:13, venerdì 13 febbraio 2004, Trey Sizemore ha scritto:
On Thu, 2004-02-12 at 21:53, Dylan wrote:
the lsof command lists what processes have which files open. look at the man page for more info.
Dylan
Thanks, I'll check it out. Strangely, I was able to unmount shortly thereafter.
Maybe you have hit a konqueror bug. If you mount the dvd/cd and close the konqueror window, it remains active using the dvd as a working directory. I use fuser -km /mountpoint_of_dvd to umount the dvd when it happens. Praise
On Friday 13 February 2004 16:42, praisetazio wrote:
Alle 04:13, venerdì 13 febbraio 2004, Trey Sizemore ha scritto:
On Thu, 2004-02-12 at 21:53, Dylan wrote:
the lsof command lists what processes have which files open. look at the man page for more info.
Dylan
Thanks, I'll check it out. Strangely, I was able to unmount shortly thereafter.
Maybe you have hit a konqueror bug. If you mount the dvd/cd and close the konqueror window, it remains active using the dvd as a working directory. I use fuser -km /mountpoint_of_dvd to umount the dvd when it happens.
Praise
I'll bet money it isn't a Konq bug... it's a "feature" a "setting" that someone thought would really help speed up Konq and just gets in the way of the average user. I've posted this solution before.... Trey, try this: Open Konq, go to Settings > Configure Konqueror. Scroll down until you see the rocket ship icon labeled Performance. Click on it. Set the Max number of instances to zero, and click Apply, OK, then restart Konq. I'll bet your device busy problem magically disappears. I tell everyone to disable this setting as soon as they install SUSE and are using KDE3.1x C.
Konqueror preloading is a feature. Konqueror using a cd-rom as current directory when it does not need to use it is a bug. Why shoud not it use the user's home directory when it is in a preloaded state? Your solution work, my solution works too when it happens.
Mmmm valid point. I didn't look at it that way. Now that you've pointed it out, I agree with you... a bug. And an annoying one when all you want to do is eject your CDROM. C.
Alle 19:38, venerdì 13 febbraio 2004, Clayton ha scritto:
On Friday 13 February 2004 16:42, praisetazio wrote:
Alle 04:13, venerdì 13 febbraio 2004, Trey Sizemore ha scritto:
On Thu, 2004-02-12 at 21:53, Dylan wrote:
the lsof command lists what processes have which files open. look at the man page for more info.
Dylan
Thanks, I'll check it out. Strangely, I was able to unmount shortly thereafter.
Maybe you have hit a konqueror bug. If you mount the dvd/cd and close the konqueror window, it remains active using the dvd as a working directory. I use fuser -km /mountpoint_of_dvd to umount the dvd when it happens.
Praise
I'll bet money it isn't a Konq bug... it's a "feature" a "setting" that someone thought would really help speed up Konq and just gets in the way of the average user. I've posted this solution before....
Trey, try this: Open Konq, go to Settings > Configure Konqueror. Scroll down until you see the rocket ship icon labeled Performance. Click on it. Set the Max number of instances to zero, and click Apply, OK, then restart Konq. I'll bet your device busy problem magically disappears. I tell everyone to disable this setting as soon as they install SUSE and are using KDE3.1x
C.
Konqueror preloading is a feature. Konqueror using a cd-rom as current directory when it does not need to use it is a bug. Why shoud not it use the user's home directory when it is in a preloaded state? Your solution work, my solution works too when it happens. Praise
participants (5)
-
Anders Dahlqvist -
Clayton -
Dylan -
praisetazio -
Trey Sizemore