I'm running FC3 with a KDE desktop. Recently, I've been having problems unmounting floppy disks. Regardless of whether I use the right mouse button on the "Floppy" icon to unmount the disk or use the command "umount /media/floppy" in a terminal window I get the message: "/media/floppy device is busy" twice. (Why twice anyway?) I've tried using the command "fuser /dev/fd0" to locate processes accessing the disk and this gives me a pid -- but when I try killing the process a new pid replaces it. The only way out seems to be rebooting... which just doesn't seem right!
Is this a bug or something "hanging on" in my system? Does anyone have a suggestion for troubleshooting this further?
Am Di, den 01.03.2005 schrieb Gerhard Magnus um 23:02:
I'm running FC3 with a KDE desktop. Recently, I've been having problems unmounting floppy disks. Regardless of whether I use the right mouse button on the "Floppy" icon to unmount the disk or use the command "umount /media/floppy" in a terminal window I get the message: "/media/floppy device is busy" twice. (Why twice anyway?) I've tried using the command "fuser /dev/fd0" to locate processes accessing the disk and this gives me a pid -- but when I try killing the process a new pid replaces it. The only way out seems to be rebooting... which just doesn't seem right!
Is this a bug or something "hanging on" in my system? Does anyone have a suggestion for troubleshooting this further?
Would you mind to tell us which PID you are killing? I mean which respawning service it is which's PID you kill.
Alexander
On Tue, 2005-03-01 at 23:29 +0100, Alexander Dalloz wrote:
Am Di, den 01.03.2005 schrieb Gerhard Magnus um 23:02:
I'm running FC3 with a KDE desktop. Recently, I've been having problems unmounting floppy disks. Regardless of whether I use the right mouse button on the "Floppy" icon to unmount the disk or use the command "umount /media/floppy" in a terminal window I get the message: "/media/floppy device is busy" twice. (Why twice anyway?) I've tried using the command "fuser /dev/fd0" to locate processes accessing the disk and this gives me a pid -- but when I try killing the process a new pid replaces it. The only way out seems to be rebooting... which just doesn't seem right!
Is this a bug or something "hanging on" in my system? Does anyone have a suggestion for troubleshooting this further?
Would you mind to tell us which PID you are killing? I mean which respawning service it is which's PID you kill.
OK, I tried this again. Here's the relevant output line from "ps aux": magnusg 5415 0.0 0.3 4912 1908 ? S 16:20 0:00 /usr/libexec/gam_
On Tue, 2005-03-01 at 16:30 -0800, Gerhard Magnus wrote:
On Tue, 2005-03-01 at 23:29 +0100, Alexander Dalloz wrote:
Am Di, den 01.03.2005 schrieb Gerhard Magnus um 23:02:
I'm running FC3 with a KDE desktop. Recently, I've been having problems unmounting floppy disks. Regardless of whether I use the right mouse button on the "Floppy" icon to unmount the disk or use the command "umount /media/floppy" in a terminal window I get the message: "/media/floppy device is busy" twice. (Why twice anyway?) I've tried using the command "fuser /dev/fd0" to locate processes accessing the disk and this gives me a pid -- but when I try killing the process a new pid replaces it. The only way out seems to be rebooting... which just doesn't seem right!
Is this a bug or something "hanging on" in my system? Does anyone have a suggestion for troubleshooting this further?
Would you mind to tell us which PID you are killing? I mean which respawning service it is which's PID you kill.
OK, I tried this again. Here's the relevant output line from "ps aux": magnusg 5415 0.0 0.3 4912 1908 ? S 16:20 0:00 /usr/libexec/gam_
This problem seems to have been solved by the latest gamin update.
On Tue, 2005-03-01 at 23:29 +0100, Alexander Dalloz wrote:
Am Di, den 01.03.2005 schrieb Gerhard Magnus um 23:02:
I'm running FC3 with a KDE desktop. Recently, I've been having problems unmounting floppy disks. Regardless of whether I use the right mouse button on the "Floppy" icon to unmount the disk or use the command "umount /media/floppy" in a terminal window I get the message: "/media/floppy device is busy" twice. (Why twice anyway?) I've tried using the command "fuser /dev/fd0" to locate processes accessing the disk and this gives me a pid -- but when I try killing the process a new pid replaces it. The only way out seems to be rebooting... which just doesn't seem right!
Is this a bug or something "hanging on" in my system? Does anyone have a suggestion for troubleshooting this further?
Would you mind to tell us which PID you are killing? I mean which respawning service it is which's PID you kill.
Alexander
Alexander, I have been having a similar problem with CDs as well Recently I used lsof and found 4 processes of gamin running on /media/cdrom that I killed and was then able to unmount/eject the CD.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
Am Mi, den 02.03.2005 schrieb Jeff Vian um 2:35:
Alexander, I have been having a similar problem with CDs as well Recently I used lsof and found 4 processes of gamin running on /media/cdrom that I killed and was then able to unmount/eject the CD.
Hi Jeff!
So we have back the old "ghost"? I mean gamin obsoleted fam, and fam was well known to cause that device blocking issue. Though I do not see an open bug report with bugzilla related to this, nor a note in the 2 FC3 gamin updates' changelogs.
Alexander
On Wed, 2005-03-02 at 03:46 +0100, Alexander Dalloz wrote:
Am Mi, den 02.03.2005 schrieb Jeff Vian um 2:35:
Alexander, I have been having a similar problem with CDs as well Recently I used lsof and found 4 processes of gamin running on /media/cdrom that I killed and was then able to unmount/eject the CD.
Hi Jeff!
So we have back the old "ghost"? I mean gamin obsoleted fam, and fam was well known to cause that device blocking issue. Though I do not see an open bug report with bugzilla related to this, nor a note in the 2 FC3 gamin updates' changelogs.
Alexander
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
It looks like this is related:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149199
I did not see the update in rawhide.
Bob...
On Wed, 2005-03-02 at 03:46 +0100, Alexander Dalloz wrote:
Am Mi, den 02.03.2005 schrieb Jeff Vian um 2:35:
Alexander, I have been having a similar problem with CDs as well Recently I used lsof and found 4 processes of gamin running on /media/cdrom that I killed and was then able to unmount/eject the CD.
Hi Jeff!
So we have back the old "ghost"? I mean gamin obsoleted fam, and fam was well known to cause that device blocking issue. Though I do not see an open bug report with bugzilla related to this, nor a note in the 2 FC3 gamin updates' changelogs.
Alexander
Apparently
I had not checked bugzilla nor tried repeating since I have only noticed it twice, and verified the cause once. I also have not yet tried to reproduce it to confirm the details.
As I noted though, it clearly was gamin that caused the "device busy" error on the CD. I will retry that soon.
I have also had errors unmounting my pen drive but the device has always powered down so I did not research that yet either.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
Am Mi, den 02.03.2005 schrieb Alexander Dalloz um 3:46:
So we have back the old "ghost"? I mean gamin obsoleted fam, and fam was well known to cause that device blocking issue. Though I do not see an open bug report with bugzilla related to this, nor a note in the 2 FC3 gamin updates' changelogs.
Alexander
Just came in as the official announcement:
Fedora Core 3 Update: gamin-0.0.25-1.FC3
This release fixes some problems with gamin-0.0.24 especially for temporary storage like USB keys. --------------------------------------------------------------------- * Tue Mar 1 2005 Daniel Veillard veillard@redhat.com 0.0.25-1.FC3
- Fix a configure problem reported by Martin Schlemmer - Fix the /media/* and /mnt/* mount blocking problems from 0.0.24 e.g. #142637
Alexander