Any update on this???
Initially I wasn't very sure where exactly the problem lied. Especially because there were many parties involved. But todays investigation can confirm that it must be a problem with hal. Hal is not adding non-partitioned encrypted devices into its database. ===== From KDE Bug: 113629 In fact, the problem seems to be with HAL. My initial suspicion was that udev might not be generating the device entry/label correctly, but that doesn't seem to be the reason. Here, In Problematic case: Nov 11 23:10:38 learner udevd-event[5814]: udev_node_update_symlinks: update symlink 'disk/by-uuid/bc1026e2-1393-49e7-a6f6-72c01e93b47e' of '/block/dm-2' Nov 11 23:10:38 learner udevd-event[5814]: udev_db_get_devices_by_name: found index directory '/dev/.udev/names/disk\x2fby-uuid\x2fbc1026e2-1393-49e7-a6f6-72c01e93b47e' Nov 11 23:10:38 learner udevd-event[5814]: update_link: found 1 devices with name 'disk/by-uuid/bc1026e2-1393-49e7-a6f6-72c01e93b47e' Nov 11 23:10:38 learner udevd-event[5814]: update_link: found '/block/dm-2' for 'disk/by-uuid/bc1026e2-1393-49e7-a6f6-72c01e93b47e' Nov 11 23:10:38 learner udevd-event[5814]: update_link: compare (our own) priority of '/block/dm-2' -100 >= 0 Nov 11 23:10:38 learner udevd-event[5814]: update_link: 'disk/by-uuid/bc1026e2-1393-49e7-a6f6-72c01e93b47e' with target 'dm-2' has the highest priority -100, create it Nov 11 23:10:38 learner udevd-event[5814]: node_symlink: found existing symlink '/dev/disk/by-uuid/bc1026e2-1393-49e7-a6f6-72c01e93b47e' Nov 11 23:10:38 learner udevd-event[5814]: node_symlink: preserve already existing symlink '/dev/disk/by-uuid/bc1026e2-1393-49e7-a6f6-72c01e93b47e' to '../../dm-2' Nov 11 23:10:38 learner udevd-event[5814]: udev_node_update_symlinks: update symlink 'disk/by-label/USB_SEAGATE' of '/block/dm-2' Nov 11 23:10:38 learner udevd-event[5814]: udev_db_get_devices_by_name: found index directory '/dev/.udev/names/disk\x2fby-label\x2fUSB_SEAGATE' Nov 11 23:10:38 learner udevd-event[5814]: update_link: found 1 devices with name 'disk/by-label/USB_SEAGATE' Nov 11 23:10:38 learner udevd-event[5814]: update_link: found '/block/dm-2' for 'disk/by-label/USB_SEAGATE' Nov 11 23:10:38 learner udevd-event[5814]: update_link: compare (our own) priority of '/block/dm-2' -100 >= 0 Nov 11 23:10:38 learner udevd-event[5814]: update_link: 'disk/by-label/USB_SEAGATE' with target 'dm-2' has the highest priority -100, create it Nov 11 23:10:38 learner udevd-event[5814]: node_symlink: found existing symlink '/dev/disk/by-label/USB_SEAGATE' Nov 11 23:10:38 learner udevd-event[5814]: node_symlink: preserve already existing symlink '/dev/disk/by-label/USB_SEAGATE' to '../../dm-2' Nov 11 23:10:38 learner udevd-event[5814]: pass_env_to_socket: passed 751 bytes to socket '/org/freedesktop/hal/udev_event', Nov 11 23:10:38 learner udevd-event[5814]: pass_env_to_socket: passed -1 bytes to socket '@/org/kernel/udev/monitor', Nov 11 23:10:38 learner udevd-event[5814]: udev_event_run: seq 1435 finished with 0 Nov 11 23:10:38 learner udevd[1240]: udev_done: seq 1435, pid [5814] exit with 0, 0 seconds old udev did its job. it exited cleanly. Now the non-problematic case: Nov 11 23:15:54 learner udevd-event[6064]: udev_node_update_symlinks: update symlink 'disk/by-uuid/b1d29a26-9d95-4aa4-8d9d-9498a874312e' of '/block/dm-3' Nov 11 23:15:54 learner udevd-event[6064]: udev_db_get_devices_by_name: found index directory '/dev/.udev/names/disk\x2fby-uuid\x2fb1d29a26-9d95-4aa4-8d9d-9498a874312e' Nov 11 23:15:54 learner udevd-event[6064]: update_link: found 1 devices with name 'disk/by-uuid/b1d29a26-9d95-4aa4-8d9d-9498a874312e' Nov 11 23:15:54 learner udevd-event[6064]: update_link: found '/block/dm-3' for 'disk/by-uuid/b1d29a26-9d95-4aa4-8d9d-9498a874312e' Nov 11 23:15:54 learner udevd-event[6064]: update_link: compare (our own) priority of '/block/dm-3' -100 >= 0 Nov 11 23:15:54 learner udevd-event[6064]: update_link: 'disk/by-uuid/b1d29a26-9d95-4aa4-8d9d-9498a874312e' with target 'dm-3' has the highest priority -100, create it Nov 11 23:15:54 learner udevd-event[6064]: node_symlink: found existing symlink '/dev/disk/by-uuid/b1d29a26-9d95-4aa4-8d9d-9498a874312e' Nov 11 23:15:54 learner udevd-event[6064]: node_symlink: preserve already existing symlink '/dev/disk/by-uuid/b1d29a26-9d95-4aa4-8d9d-9498a874312e' to '../../dm-3' Nov 11 23:15:54 learner udevd-event[6064]: udev_node_update_symlinks: update symlink 'disk/by-label/USBDISK' of '/block/dm-3' Nov 11 23:15:54 learner udevd-event[6064]: udev_db_get_devices_by_name: found index directory '/dev/.udev/names/disk\x2fby-label\x2fUSBDISK' Nov 11 23:15:54 learner udevd-event[6064]: update_link: found 1 devices with name 'disk/by-label/USBDISK' Nov 11 23:15:54 learner udevd-event[6064]: update_link: found '/block/dm-3' for 'disk/by-label/USBDISK' Nov 11 23:15:54 learner udevd-event[6064]: update_link: compare (our own) priority of '/block/dm-3' -100 >= 0 Nov 11 23:15:54 learner udevd-event[6064]: update_link: 'disk/by- label/USBDISK' with target 'dm-3' has the highest priority -100, create it Nov 11 23:15:54 learner udevd-event[6064]: node_symlink: found existing symlink '/dev/disk/by-label/USBDISK' Nov 11 23:15:54 learner udevd-event[6064]: node_symlink: preserve already existing symlink '/dev/disk/by-label/USBDISK' to '../../dm-3' Nov 11 23:15:54 learner udevd-event[6064]: pass_env_to_socket: passed 735 bytes to socket '/org/freedesktop/hal/udev_event', Nov 11 23:15:54 learner udevd-event[6064]: pass_env_to_socket: passed -1 bytes to socket '@/org/kernel/udev/monitor', Nov 11 23:15:54 learner udevd-event[6064]: udev_event_run: seq 1459 finished with 0 Nov 11 23:15:54 learner udevd[1240]: udev_done: seq 1459, pid [6064] exit with 0, 0 seconds old Nov 11 23:15:54 learner NetworkManager: <debug> [1226425554.923853] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/volume_uuid_b1d29a26_9d95_4aa4_8d9d_9498a874312e'). Here too udev did its job. But here also the device got added to hal. ====== Another look: [EMAIL PROTECTED]:/sys/block$ tree dm-2/ dm-2/ |-- bdi -> ../../class/bdi/254:2 |-- capability |-- dev |-- holders |-- power | `-- wakeup |-- range |-- removable |-- size |-- slaves | `-- sdb -> ../../sdb |-- stat |-- subsystem -> ../../block `-- uevent 6 directories, 8 files [EMAIL PROTECTED]:/sys/block$ tree dm-3/ dm-3/ |-- bdi -> ../../class/bdi/254:3 |-- capability |-- dev |-- holders |-- power | `-- wakeup |-- range |-- removable |-- size |-- slaves | `-- sdc2 -> ../../sdc/sdc2 |-- stat |-- subsystem -> ../../block `-- uevent You see here that dm-3 is a partitioned encrypted device and dm-2 is a non-partitioned encrypted device. If I query the hal database, it only know about dm-3. There is no record about dm-2 [EMAIL PROTECTED]:/sys/block$ sudo lshal | grep -i dm-2 [EMAIL PROTECTED]:/sys/block$ sudo lshal | grep -i dm-3 block.device = '/dev/dm-3' (string) linux.sysfs_path = '/sys/block/dm-3' (string) This makes me conclude that it is a problem with hal Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."
signature.asc
Description: This is a digitally signed message part.
