* John Andersen <jsamyth@gmail.com> [09-13-11 18:09]:
David's Flash cards thru a reader vs Tejas's USB sticks are two different problems.
maybe
USB in all recent versions of OpenSuse mount in quick removal mode (aka synchronous mode) where the application receives indication that the write is complete only when it IS IN FACT complete, there is no caching, and files are closed and fat is written after each file. It makes for terrible performance, but its safer.
I have not experienced this, but will not argue
With a reader, depending on how it is connected, it may not appear as USB (even if it is in fact USB), in which case all bets are off, and you have to use safely remove option.
There is still a problem with Safely remove in Linux for USB. It is not the same as EJECT.
Now I will argue. I have 11.4 with the "Device Notifier" applet and the "eject" indicator/icon appears to eject the device. It definitely umounts the device, and demsg confirm that. dmesg: ------------------ 1 --------------------------------- [262931.917663] sd 20:0:0:0: [sdg] 31326208 512-byte logical blocks: (16.0 GB/14.9 GiB) [262931.921142] sd 20:0:0:0: [sdg] No Caching mode page present [262931.921144] sd 20:0:0:0: [sdg] Assuming drive cache: write through [262931.925023] sd 20:0:0:0: [sdg] No Caching mode page present [262931.925027] sd 20:0:0:0: [sdg] Assuming drive cache: write through [262931.926361] sdg: sdg1 [262990.786704] sdg: detected capacity change from 16039018496 to 0 ------------------ 2 --------------------------------- [263016.705854] sd 20:0:0:0: [sdg] Spinning up disk....ready [263018.063288] sd 20:0:0:0: [sdg] 31326208 512-byte logical blocks: (16.0 GB/14.9 GiB) [263018.065759] sd 20:0:0:0: [sdg] No Caching mode page present [263018.065762] sd 20:0:0:0: [sdg] Assuming drive cache: write through [263018.069132] sd 20:0:0:0: [sdg] No Caching mode page present [263018.069137] sd 20:0:0:0: [sdg] Assuming drive cache: write through [263018.070516] sdg: sdg1 [263032.655941] sdg: detected capacity change from 16039018496 to 0 The first instance above the card was inserted in the card reader and then removed/ejected via the indicator/icon. The second instance the card was inserted in the card reader and then ejected via the cl "eject /dev/sdg1"
There seems no way to do an eject in KDE yet.
the above was performed in KDE 4.6.5
The two are quite different, EJECT is not normally done even if you click the USB applet and select what appears to be the eject icon.
not according to my experience.
This is not a problem for USB sticks that are accessed in synchronous mode. But it can be a big problem for things that pretend to be USB devices, such as many android phones, Nook Ereaders, etc.
For these to recognize that you are truly finished, you have to EJECT. And with KDE, You have to do this from the command line, or wait a long time for your device to quiesce.
I found this out after trashing my Nook storage some time back.
I have followed this procedure for several years w/o problem. I am speaking *only* about CF cards in my Stratitec multi-reader: Bus 001 Device 010: ID 05e3:0710 Genesys Logic, Inc. USB 2.0 33-in-1 Card Reader I can/will preform further tests if you wish. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org