Red Hat Bugzilla – Bug 122335
drive mount applet can't unmount a usb disk
Last modified: 2007-11-30 17:10:41 EST
Description of problem: I've set up a usb disk in /etc/fstab which is user controllable and I can mount and unmount from the command line. I added the drive mount applet to my desktop and changed it to use /mnt/usbdisk where I mount my usb disk. When I click on the drivemount icon, the usb disk is mounted and a disk icon appears on my desktop. However, whenever I click it again it can't unmount it and claims that the device is busy. However, I can unmount it using the desktop icon by right clicking and selecting the "unmount volume" option. On a related note: the applet has options for icons distinguishing between when the disk is mounted or not, but these are not active when I set it up for a usb disk. Shouldn't they be? Also isn't a desktop disk icon redundant now that I have to use the disk mount applet to mount the disk? Version-Release number of selected component (if applicable): gnome-applets-2.6.0-4 How reproducible: always Steps to Reproduce: 1. setup usb disk and drive mount icon 2. click on disk applet to mount 3. try and unmount by clicking on disk applet again Actual results: Mount failed because device busy Expected results: umount disk Additional info:
Does umount /mnt/usbdisk work from the command line?
No /mnt/usbdisk doesn't work either. The only way to unmount is to right-click on the usbdisk icon gnome puts up and select "Unmount volumne"
Ah, I see. This must be just a conflict between the drivemount applet and Nautilus. Nautilus probably adds a FAM monitor on the directory which is why its being reported as busy. The drivemount applet should probably ask Nautilus to unmount the volume or something.
Right. Would that also correct the problem where one cannot unmount from the command line?
The applet has been completely re-worked upstream in GNOME 2.10 to use gnome-vfs just like nautilus, so I'll close this bug as resolved UPSTREAM. If you see the issue in later versions of GNOME (I don't expect you will), then please do re-open the bug.