Bug 268223 - USB disks seem to be just unmounted, not "safely removed"
Summary: USB disks seem to be just unmounted, not "safely removed"
Status: RESOLVED DUPLICATE of bug 267398
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: libsolid-udisks (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: Lukáš Tinkl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-11 14:40 UTC by Kevin Brubeck Unhammer
Modified: 2011-03-11 16:07 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Brubeck Unhammer 2011-03-11 14:40:36 UTC
Version:           unspecified (using KDE 4.6.1) 
OS:                Linux

I've got a Cowon iAudio E2, a USB ogg/flac/mp3-player, and whenever I remove it with the regular panel/taskbar device notifier, it says that the device "can now be safely removed". However, if I then unplug it, several files often get corrupted, e.g. a certain song will skip a bit at certain places, and if I plug it in again and do a diff, I get "binary files … differ". This is easily reproducible. So I figure the device notifier doesn't really safely remove the device, only umounts it. I found this script

http://elliotli.blogspot.com/2009/01/safely-remove-usb-hard-drive-in-linux.html

which does something with sdparm to safely stop the device, and when I use that after umounting with the notifier, the files seem to survive.

Feature request: do whatever that script does after umounting.

Reproducible: Always

Steps to Reproduce:
Plug in a Cowon iAudio E2
Copy over about 50 mp3's.
Do a diff -r to make sure files were correctly copied over. 
Click the notifier to "safely remove", 
Remove, 
Plug back in,
Do a diff -r.

Actual Results:  
Certain files will be corrupted and differ.

Expected Results:  
Files should not differ.

Unfortunately I haven't got any other such devices to test with.
Comment 1 Lukáš Tinkl 2011-03-11 16:05:59 UTC

*** This bug has been marked as a duplicate of bug 267398 ***
Comment 2 Lukáš Tinkl 2011-03-11 16:07:02 UTC
Please reopen if necessary after testing with KDE 4.6.2, thx