GNOME Bugzilla – Bug 689088
Don't default to write-benchmark if device is in use
Last modified: 2013-02-17 20:12:54 UTC
... otherwise the user just ends up with a "Device is busy" error dialog, see e.g. https://bugzilla.redhat.com/show_bug.cgi?id=879840 and elsewhere. Also, if a write-benchmark is requested, try to ensure the device is not used (by e.g. unmounting filesystems, locking encrypted devices).
Fixed on master, see: http://git.gnome.org/browse/gnome-disk-utility/commit/?id=f8decc497b1ab8b46313a14e9532a83343e3d132 http://git.gnome.org/browse/gnome-disk-utility/commit/?id=20598b11709b3f6c5190b09f6f62214fee10e7df http://git.gnome.org/browse/gnome-disk-utility/commit/?id=dbf23244358db32e3fef15a05d3308b79c856042 This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Solution tested in Rawhide (F19) and I still get the error when executing write test on mounted disk. Better would be info message that the test is not possible on mounted drive instead of error message.
(In reply to comment #2) > Solution tested in Rawhide (F19) and I still get the error when executing write > test on mounted disk. Better would be info message that the test is not > possible on mounted drive instead of error message. Rawhide (F19) doesn't have this yet.
*** Bug 693943 has been marked as a duplicate of this bug. ***