Hi
I have an external USB disk and a USB stick which behave differently under KDE when selecting "Safely Remove"
They both have 3 partitions /boot, /, SWAP (With Fedora installs on as it happens)
[root@naxos ~]# ls -l /dev/sdc* brw-r----- 1 root disk 8, 32 2007-06-29 11:34 /dev/sdc brw-r----- 1 root disk 8, 33 2007-06-29 11:34 /dev/sdc1 brw-r----- 1 root disk 8, 34 2007-06-29 11:34 /dev/sdc2 brw-r----- 1 root disk 8, 35 2007-06-29 11:34 /dev/sdc3
sdc1 and sdc2 are both mounted as per their "labels" (if inserted separately)
When Safely Remove is selected
1. The USB disk umount the 2 partitions but leaves the icons on the dektop and leaves /dev/sdc, /dev/sdc1 and /dev/sdc2
2. The USB memory stick umount the 2 partitions removes the icons from the desktop and only leaves /dev/sdc
naxos ~ 1005# ls -l /dev/sdc* brw-r----- 1 root disk 8, 32 2007-06-29 10:42 /dev/sdc
Thus the USB memory stick has to be removed and re-inserted to regain access.
For the USB disk you can just click on the icon
1. Why are the two "identical" devices treated differently?
2. Is there an easy method of changing all USB sticks to act the same as the USB Disk?
Its just annoying !
Surely you don't have to dig into hal/udev to fix this
Regards
john
John Austin wrote:
Thus the USB memory stick has to be removed and re-inserted to regain access.
For the USB disk you can just click on the icon
Why are the two "identical" devices treated differently?
Is there an easy method of changing all USB sticks to act the same as the USB Disk?
Actually I just had this same problem, granted I was on Gentoo when this happened, but I'd be willing to bet it's the same or similar problem. With KDE it is capable of mounting those devices on it's own, so in some cases hal/udev and KDE are competing against one another for mounting the disk. The symptom in my case was that the drive kept moving mount points from sda1 all the way down to sde1 over the course of an hour. In my case the way to fix this was to turn of ivman so that it wouldn't compete against KDE's kioslaves when mounting those USB drives I have.
HTH.
On Fri, 2007-06-29 at 09:10 -0400, Mark Haney wrote:
John Austin wrote:
Thus the USB memory stick has to be removed and re-inserted to regain access.
For the USB disk you can just click on the icon
Why are the two "identical" devices treated differently?
Is there an easy method of changing all USB sticks to act the same as the USB Disk?
Actually I just had this same problem, granted I was on Gentoo when this happened, but I'd be willing to bet it's the same or similar problem. With KDE it is capable of mounting those devices on it's own, so in some cases hal/udev and KDE are competing against one another for mounting the disk. The symptom in my case was that the drive kept moving mount points from sda1 all the way down to sde1 over the course of an hour. In my case the way to fix this was to turn of ivman so that it wouldn't compete against KDE's kioslaves when mounting those USB drives I have.
HTH.
Many thanks for the reply
I have had a look round and cannot find any reference on my machine (F7) to ivman
Google did bring up a reference that said "KDE 3.5 automount is worse than ivman on 3.4" so I have a feeling this isn't the cause
Regards John
John Austin wrote on Friday 29 June 2007:
- Why are the two "identical" devices treated differently?
I make a reasonable guess: that KDEs "fault". Those devices are not identical, they have different properties. You can look at them using hal-device-manager. KDE looks at these properties and invokes different hal methods over DBUS. In case of the memory stick it would be "Eject" and in case of the hard drive it would be "Unmount". It think so because I also have an USB memory stick and an USB hard driver and their hal method list is identical, but different methods are invoked on them.
- Is there an easy method of changing all USB sticks to act the same as the USB Disk?
I have some ideas but I had no time to investigate them further. I hope I will have in the near future.
1. Replace hal-storage-eject with hal-storage-unmount (in /usr/libexec) UGLY. And not update-safe.
2. Write a fdi file which either removes the Eject method from hal methods' list or let "Eject" point to "hal-storage-unmount" That would be my preferred method.
3. Somehow tell KDE to provide both options in the device's dialog: unmount and eject. That would be just perfect.
Its just annoying !
I most definitely agree with you. :-)
Surely you don't have to dig into hal/udev to fix this
About this I'm not so sure...
On Wed, 2007-07-04 at 23:38 +0200, Adalbert Prokop wrote:
John Austin wrote on Friday 29 June 2007:
- Why are the two "identical" devices treated differently?
I make a reasonable guess: that KDEs "fault". Those devices are not identical, they have different properties. You can look at them using hal-device-manager. KDE looks at these properties and invokes different hal methods over DBUS. In case of the memory stick it would be "Eject" and in case of the hard drive it would be "Unmount". It think so because I also have an USB memory stick and an USB hard driver and their hal method list is identical, but different methods are invoked on them.
I have managed to get hal-device-manager working and it does indeed show differences between the USB Stick and USB Disk, in particular
Stick info.addons dbus.Array([dbus.String(u'hald-addon-storage')]..... storage.media_check_enabled 1 storage.removable 1
Disk info.addons Does not exist storage.media_check_enabled 0 storage.removable 0
- Is there an easy method of changing all USB sticks to act the same as the USB Disk?
I have some ideas but I had no time to investigate them further. I hope I will have in the near future.
Replace hal-storage-eject with hal-storage-unmount (in /usr/libexec) UGLY. And not update-safe.
Write a fdi file which either removes the Eject method from hal methods' list or let "Eject" point to "hal-storage-unmount" That would be my preferred method.
Somehow tell KDE to provide both options in the device's dialog: unmount and eject. That would be just perfect.
Its just annoying !
I most definitely agree with you. :-)
Surely you don't have to dig into hal/udev to fix this
About this I'm not so sure...
-- bye, Adalbert
It is also noticeable that when using the USB Stick and Safely remove is invoked then /dev/sdx1 etc are removed leaving just /dev/sdx then this device does not work. ie fdisk /dev/sdx fails to find the device
My knowledge runs out at this stage !!
Many thanks for the reply
John
-
Adalbert Prokop -
Dr J Austin -
Mark Haney