Using the Disk Management GUI.
I mounted the floppy
copied a file to it by dragging from one Nautilus window to another
Then I tried to unmount the floppy and got an error that the device (/media/floppy) was busy.
This is not the first time this has happened to me.
And it does not happen all the time. In fact, yesterday I did the exact same steps with no problem.
most of the gui file managers will leave devices open by some process.
use the fuser command to determine what process id you can kill to be able to unmount your device :)
Robert Moskowitz wrote:
Using the Disk Management GUI.
I mounted the floppy
copied a file to it by dragging from one Nautilus window to another
Then I tried to unmount the floppy and got an error that the device (/media/floppy) was busy.
This is not the first time this has happened to me.
And it does not happen all the time. In fact, yesterday I did the exact same steps with no problem.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
At 08:26 AM 5/25/2005, fluid wrote:
most of the gui file managers will leave devices open by some process.
use the fuser command to determine what process id you can kill to be able to unmount your device :)
I am not really familar with these commands (maybe why I use the GUI!). I just spent one year on Unix, Solaris 3 ii '93....
I did a man fuser then tried:
fuser /media/floppy
and got an empty list back.
Robert Moskowitz wrote:
At 08:26 AM 5/25/2005, fluid wrote:
most of the gui file managers will leave devices open by some process.
use the fuser command to determine what process id you can kill to be able to unmount your device :)
I am not really familar with these commands (maybe why I use the GUI!). I just spent one year on Unix, Solaris 3 ii '93....
I did a man fuser then tried:
fuser /media/floppy
and got an empty list back.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
if that is where your device is mounted, then its not currently mounted. ;)
beyond that, you need to open a terminal, stick in a floppy, and do:
mount /media/floppy
when you are done, make sure every program that was opened and in that path are now closed, and issue:
umount /media/floppy
if its busy when you try and umount, then use fuser to figure out whats got it, and use 'kill' to shut down those processes. those filemanagers will leave paths open for no real reason (except stat'ing it, or watching for new file objects)
At 08:41 AM 5/25/2005, fluid wrote:
if that is where your device is mounted, then its not currently mounted. ;)
beyond that, you need to open a terminal, stick in a floppy, and do:
mount /media/floppy
when you are done, make sure every program that was opened and in that path are now closed, and issue:
umount /media/floppy
if its busy when you try and umount, then use fuser to figure out whats got it, and use 'kill' to shut down those processes. those filemanagers will leave paths open for no real reason (except stat'ing it, or watching for new file objects)
Wow was this ever disasterous!
mount /media/floppy said it was already mounted
unmount /media/floppy said it was busy.
then I tried fuser -m /media/foppy
and it returned 2565
so I: kill 2565
and the system goes haywire! terminal takes off like the enter key is stuck down.
I close terminal then the desktop goes blewy and starts opening all sorts of windows. I manage to get to shutdown, but nothing happens. Finally I just powered down.....
There has GOT to be a better way!
Illegitimi non Carborundum
Having the problem again, but I am getting smarter.
after I do the fuser -m /media/floopy
I do a ps xjaf
I find out that the process that seems to be holding onto the floppy is:
/usr/libexec/gam_server
This time, killing that process lets me umount the floppy.
This has happened twice to me today.
At 08:41 AM 5/25/2005, fluid wrote:
Robert Moskowitz wrote:
At 08:26 AM 5/25/2005, fluid wrote:
most of the gui file managers will leave devices open by some process.
use the fuser command to determine what process id you can kill to be able to unmount your device :)
I am not really familar with these commands (maybe why I use the GUI!). I just spent one year on Unix, Solaris 3 ii '93....
I did a man fuser then tried:
fuser /media/floppy
and got an empty list back.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
if that is where your device is mounted, then its not currently mounted. ;)
beyond that, you need to open a terminal, stick in a floppy, and do:
mount /media/floppy
when you are done, make sure every program that was opened and in that path are now closed, and issue:
umount /media/floppy
if its busy when you try and umount, then use fuser to figure out whats got it, and use 'kill' to shut down those processes. those filemanagers will leave paths open for no real reason (except stat'ing it, or watching for new file objects) _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
copied a file to it by dragging from one Nautilus window to another
Then I tried to unmount the floppy and got an error that the device (/media/floppy) was busy.
Did you still have the two nautilus windows open when you attempted to unmount the floppy? If you still have a window open and in the floppy directory or if you have a terminal session in a mounted directory, you will not be able to unmount the device. This to me would explain why your steps work some of the time, and not others.
- -- Jim Perrin
At 09:19 AM 5/25/2005, Jim Perrin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
copied a file to it by dragging from one Nautilus window to another
Then I tried to unmount the floppy and got an error that the device (/media/floppy) was busy.
Did you still have the two nautilus windows open when you attempted to unmount the floppy? If you still have a window open and in the floppy directory or if you have a terminal session in a mounted directory, you will not be able to unmount the device. This to me would explain why your steps work some of the time, and not others.
thinking back...
I closed the window that was open to the floppy, but not the other. Of course that one was open to the directory of the file that I dragged onto the floppy.
BINGO!
Next time I will close it too....
-
fluid -
Jim Perrin -
Robert Moskowitz