Hey again, On 09/07/2010 Milan Broz wrote: > On 07/09/2010 09:41 AM, Γιώργος Πάλλας wrote: > > > # WARNING: other process locked internal device > > temporary-cryptsetup-18450, retrying remove. > > # WARNING: Process PID 18473 (hald-probe-volu) [PPID 1711 (hald-runner)] > > spying on internal device /dev/dm-4. > > Ha! So finally the debug code found something locking the device! :-) > > HAL _must_ _not_ open temporary-cryptsetup device. > It can scan final device but not the temporary one. > (udev/udisks have this solved, I thought hal uses the same...) > > Maybe it is not the real problem but please fix hal too here.
I discussed that with the hal maintainer. Hal already has a workaround to ignore temporary-cryptsetup-* devices (in hald/linux/osspec.c). The problem here seems to be that hal probes /dev/dm-4, and not the temporary-cryptsetup device. and the workaround doesn't ignore that one. so, Giorgos, please temporarily disable hal (/etc/init.d/hal stop), and see whether the issue disappears. In that case, hal is the problem for sure. But then still the problem is, how should hal distinguish temporary cryptsetup devices reliably, when '/dev/dm-X' is used? Milan, is there any better/cheaper solution than a lookup for symlinks in /dev/mapper/*? greetings, jonas
signature.asc
Description: Digital signature
