Bug 919194 - Missed safely remove option, eject does not remove power (USB-flash, USB-HDD)
Summary: Missed safely remove option, eject does not remove power (USB-flash, USB-HDD)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: udisks2
Version: 20
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Michael Catanzaro
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-07 19:57 UTC by Nrbrtx
Modified: 2015-06-29 11:47 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 11:47:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 676321 0 None None None Never
GNOME Bugzilla 695281 0 None None None Never
Launchpad 1067876 0 None None None Never
Launchpad 1127135 0 None None None Never
Novell 808447 0 None None None Never

Description Nrbrtx 2013-03-07 19:57:33 UTC
Removing powered device from USB port is unsafe operation. It is not sufficient to unmount/eject drive, it must be completely powered off before removal.

Please bring back "Safely remove" to Nautilus.

I tried 4 Transcend flashes, 1 ADATA, 2 no-name (SMI and ChipsBnk). They remain powered after eject - it's DANGEROUS for my (and anybody's) data.
I tried external USB-SATA Tsunami HDD - Disks does not spin down (stop) it - It's DANGEROUS for my (and anybody's) data.

This bug come from Nautilus. Ubuntu is affected by this bug too (see https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1067876, https://bugs.launchpad.net/nautilus/+bug/1127135).

Comment 1 Nrbrtx 2013-03-07 20:05:58 UTC
I can detach USB-flash or HDD from console with "udisks --detach /dev/sdX", but it is not simple way for linux-newbies.

Comment 2 Nrbrtx 2013-03-10 18:24:53 UTC
On other laptop (Asus T101MT) Transcend flash is remounted automatically by Nautilus (?) after "udisks --detach /dev/sdX".

Comment 3 Nrbrtx 2013-03-12 17:23:12 UTC
I tested 4 flashes and 1 USB HDD - you can read my test report (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dHJBalI2b09TQ2ZNOHJOQnhFbEVXaXc).
The conclusion is very bad:  I tested Ubuntu 12.04 LTS, Ubuntu 13.04, Fedora 18, OpenSuse 12.3. All they can't remove power from USB drives like it was in GNOME 2 and previous versions of GNOME 3.

Comment 4 Martin Pitt 2013-03-13 08:30:54 UTC
I reported that to https://bugzilla.gnome.org/show_bug.cgi?id=695281 some days ago. It seems to me that either many USB sticks are lying and claim that they have removable media, or it's a bug in the kernel driver that sets "removable=1" for them.

Nrbtx, note that it's not quite dangerous -- devices are still "eject"ed, which means unmounting everything and releasing the media. The actual USB device remains powered up, but that's not a concern for data safety.

Comment 5 Nrbrtx 2013-03-13 08:42:16 UTC
I don't think so. 
Removing a powered device is not a good idea anyway (especially rotating USB-HDD).

Comment 6 Nrbrtx 2013-03-21 19:43:49 UTC
Safely remove is partially working under Fedora 19 alpha (from http://fedorapeople.org/groups/qa/20130320-gnome/20130320-gnome-i686.iso).
Nautilus showed Safely remove option for 1 of my 5 flashes and USB-HDD.
It powered off 1 of my 5 flashes, but USB-HDD did not spin down.

Comment 7 Cosimo Cecchi 2013-03-21 20:56:38 UTC
-> gvfs

As Martin says in comment #4, Nautilus' behavior didn't change here anytime recently, but gvfs/udisks apply different heuristics now, which are reflected in the options available to the GIO clients like Nautilus.

Comment 8 Nrbrtx 2013-04-27 14:14:52 UTC
Bug still exists in Fedora 18 with latest updates. 
Please inform GNOME developers and fix this bug using joint efforts.

Comment 9 Nrbrtx 2013-04-28 17:16:52 UTC
Bug exists in Gnome 3.8 (Fedora 19).

Comment 10 Fedora Admin XMLRPC Client 2013-05-23 14:41:50 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 11 Fedora Admin XMLRPC Client 2013-05-23 14:44:09 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 12 Fedora Admin XMLRPC Client 2013-05-23 14:47:00 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 13 Fedora Admin XMLRPC Client 2013-05-23 14:49:38 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 14 Nrbrtx 2013-06-23 13:10:09 UTC
Bug still exists in Fedora 18 and 19.

Comment 15 Nrbrtx 2013-07-02 19:44:30 UTC
Bug exists in Fedora 19 final. What's next?

Comment 16 Andre Robatino 2013-07-22 15:52:16 UTC
I saw this with F18. I clean installed F19 when it came out. Now I generally have to unmount several times because it tends to automatically remount. But when it finally does unmount for good, it automatically powers off. I have gnome-disk-utility-3.8.2-1.fc19.x86_64 and gvfs-1.16.3-2.fc19.x86_64.

Comment 17 Nrbrtx 2013-11-24 12:49:22 UTC
Bug exists in Fedora 20.

Comment 18 Nrbrtx 2013-12-24 09:09:17 UTC
Bug exists in Fedora 20 final version.

Comment 19 Nrbrtx 2014-01-18 19:51:49 UTC
Bug still exists in Fedora 20. Please fix it.

Comment 20 Nrbrtx 2014-04-28 09:25:35 UTC
The bug exists in Red Hat ____Enterprise___ Linux Workstation 7.0 (Maipo).

Bug can be fixed by upgrading udisks to version 2.1.3 (see commits http://cgit.freedesktop.org/udisks/commit/?id=fcdd8f48b6ac9b1b6da82fdf5f59230fc2ea6feb and http://cgit.freedesktop.org/udisks/commit/?id=a54c2fa14c522487a78828d4a9dfd89f916a3576).

Comment 21 Fedora Admin XMLRPC Client 2015-02-26 17:26:20 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 22 Fedora Admin XMLRPC Client 2015-02-26 22:39:14 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 23 Fedora End Of Life 2015-05-29 08:54:49 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 24 Fedora End Of Life 2015-06-29 11:47:21 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.