Red Hat Bugzilla – Bug 73397
.Trash on removable disks makes them unmountable
Last modified: 2015-01-07 19:00:09 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020724 Description of problem: nautilus creates a .Trash on removable disks (zip) when an item is deleted causing fam to watch the .Trash on that disk making it unmountable Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. mount zip disk 2. use nautilus to delete item from it 3. unmount 4. remount (nautilus sees the .Trash and sets a watch on it) 5. Try to unmount (commandline or through nautilus) Actual Results: device is busy and won't free up until fam is killed Expected Results: fs should have been unmounted Additional info:
This should be fixed in nautilus 2.0.6-6 (reopen if not)
reopening. I was able to reproduce this with a floppy disk w/ nautilus-2.0.6-6
You need to unmount it using nautilus.
Ah, I missed that part of the bug report. Unmounting from the command line isn't intended to work. If unmount via nautilus doesn't work (with latest nautilus/gnome-vfs2 from rawhide), then please reopen the bug.
I guess 3.5" floppies are treated differently.... Should I open a separate bug to track that issue? If I mount a floppy at the command line and delete a file with nautilus, then I can't unmount it either. There doesn't seem to be an obvious way to unmount this device from within nautilus. Additionally, the "eject" option in the contextual menu doesn't apply.
If you mount a floppy you should get a desktop icon for it; if not, that is a separate bug yes. If you have a desktop icon, then it should offer an unmount option on right-click. Also if you right click empty space on the desktop, there is a Disks submenu that should offer the option. And true Eject should be disabled for floppies, probably, though for IDE devices we can't really know reliably if the device offers Eject I don't think.
It always says Eject for removable media, because we can't know which devices are ejectable. Some floppies are.
hp - the icon appears on the desktop as expected. alexl - thanks for the clarification re: the eject option. But, a similar condition exists for floppy disks if the following steps are followed: 1- mount floppy 2- browse to floppy w/ nautilus and delete a file 3- try to unmount floppy -- fam prevents you.
Where can I get a newer version of nautilus to check this with? And as far as the ejetc versus unmount goes - why not offer both? Though right now even eject isn't actually ejecting my disk (when I'm not having trouble with fam and can still unmount it).
benl: I don't understand what you mean by step 3? Do you select "Eject" in the floppy menu, or are you trying to unmount from the command line? The first should work, and the last can never work.
Not to be too irritating, but shouldn't there remain some ability to unmount from the commandline? Why is there a watch placed on the .Trash of removable disks anyway?
alexl: there is no unmount option from withing nautilus for a 3.5" floppy unless the drive supports eject. And the fam process that is started prevents a clean command line unmount operation.
Why do you say that? Did you test it? The operation called "Eject" in the menu for a floppy does: 1) remove the fam watch for the trash on the floppy 2) unmount the floppy 3) execute "eject" (which ejects the floppy if the hardware supports it). Is it not doing this?
"Why do you say that? Did you test it?" -- yes. 1- insert floppy. 2- mount w/ "Disks" contextual menu. 3- try to unmount it w/ eject. 4- icon still appears on desktop, and "mount" shows /dev/fd0 as mounted. "eject" *did* remove the fam watch (sorry about the earlier confusion), but it did not unmount the floppy.
Ok. That sounds like a bug. Can you file a separate bug about that?