View Full Version : umounting in FC2 Test 1
18th February 2004, 11:06 PM
Has anyone had trouble unmounting floppies and CDROM's AFTER looking at files with Konqueror in Fedora 2? Also, the KDE floppy formatter seems broken. I can format with fdformat and mkfs on the command line fine. I can also look at files from any OTHER means than Konqueror and the umount fine.
However, AFTER the Konqueror browsing for files on either one of those devices, the system will NOT let me umount as it says it is still "busy" even though I am not in it's directory. If I go to ROOT with an su command, it still won't let me. ONLY if I LOG IN as root, will it let me umount the drives. I am curious if anyone else is having this trouble with Test 1.
19th February 2004, 01:02 AM
i got same problem with my cdrom, only root allow me to mount
19th February 2004, 01:41 AM
Good, now I know that I'm not crazy...well, at least in THAT way. So to clarify MY problem. I can MOUNT just fine...as a matter of fact, as a regular user, the CDROM automounts so I haven't really had to mount it. But I can also mount a floppy. I can UNmount it also, as long as I DON'T look at the files with Konqueror (as far as I can tell). If I don't do that, then I can unmount (umount) the file system. fstab file is normal.
Funny thing is, at least for me, I can't even umount when I su to root. The ONLY way is to LOG IN as root and then umount. So good, now I know that the problem is found and it will be fixed.
The other problem is that the GUI floppy formatter with KDE doesn't work. It SEEMS to format the disk, but it will not create a file system. I use the command line to two-step the process (for me the most reliable way) using fdformat command and then the mkfs command, and it works great...so I'm sure that ALL of these issues are KDE issues.
Thanks for the reply....I'll keep my ears open, but I'm sure with Test TWO these problems will be corrected.
19th February 2004, 09:32 AM
This has been a problem plaguing FC1 and even earlier. It seems to be fixed and then rears its ugly head again...
Basically fam, the file monitoring daemon is locking the cdrom process with supposed open files and thus won't let umount free it.
You can see this by issuing a `/usr/sbin/lsof /mnt/cdrom`
You should see an entry for fam.
Anyway, the bugzilla entry for this is located here:
Right at the bottom, Alexander Larrson on RedHat has explained the problem and stated that fam version 126.96.36.199 fixes the problem.
Alternatively, a couple quick fixes that should let you unmount the drive are:
service xinetd restart
ps aux | grep fam
kill -15 <pid>
<pid> is the process id for fam
Hope that helps.
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.