Bug#409875: [Pkg-cryptsetup-devel] Bug#409875: bug #409875

David Härdeman david at hardeman.nu
Thu Feb 8 00:14:35 CET 2007


On Wed, Feb 07, 2007 at 11:26:16PM +0100, Johannes Schlumberger wrote:
>Hi,
>> This would suggest that the problem is not with cryptsetup at least. 
>> Something seems wonky with device-mapper in general.
>
>Whom should I be talking to about this?

That would be the dmsetup package maintainer, but lets keep at it for a 
while before we call him in

>> If it tries to setup 253:2, that suggests that there are two other 
>> device-mapper devices already setup...what is the output of "ls -al 
>> /dev/mapper", "dmsetup table" and "cat /proc/mounts"? Also, are you 
>> using udev?
>
>That is right, my two encrypted swappartitions.
>...
>[23:24:04][root at asso:/home/spjsschl]# dmsetup table
>swap2: 0 995967 crypt aes-cbc-plain
>8fd07cf5cecac858cdd2c0ce673449b4c1734cecbe8a24e5be629d542c975cf1 0 22:5 0
>swap1: 0 6458067 crypt aes-cbc-plain
>dde5fec1ee7146100bc83af997171ce196c2d1c453134d21e574f85ccc296588 0 22:65 0

Which devices are 22:5 and 22:65? I'm guessing /dev/hdc5 and /dev/hdd2?

Could you provide me with the output from "ls -al /dev/hd*" and "fdisk -l 
/dev/hd?"

(BTW, the above keys are random keys, right?)

-- 
David Härdeman




More information about the Pkg-cryptsetup-devel mailing list