Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#6204 - Cryptsetup 1.0.4-2 broken

Attached to Project: Arch Linux
Opened by Alexander Rink (freigeist) - Friday, 12 January 2007, 19:08 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 13 January 2007, 21:09 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Cryptsetup 1.0.4-2 seems to be broken. I can not mount my encrypted partition with the latest version (1.0.4-2), while 1.0.4-1 still works without problems. I can create the /dev/mapper entry but I can not mount it. /var/log/messages says:

Jan 12 17:35:51 t-rex device-mapper: ioctl: error adding target to table
Jan 12 17:35:51 t-rex device-mapper: ioctl: device doesn't appear to be in the dev hash table.
This task depends upon

Closed by  Thomas Bächler (brain0)
Saturday, 13 January 2007, 22:27 GMT
Reason for closing:  Not a bug
Comment by Alexander Rink (freigeist) - Friday, 12 January 2007, 19:25 GMT
Forget about the /var/log/messages entries, they seem to be not related (I forgot adding the partition number). But the error is still as stated above. I can't mount the /dev/mapper/crypt entry because "mount: you must specify the filesystem type". I have just again verified the bug, downgrading to 1.0.4-1 instantly fixed the problem.
Comment by Thomas Bächler (brain0) - Saturday, 13 January 2007, 21:24 GMT
A little bit more details please. Which exact command do you use to open the crypt device? Can you compare the resulting "dmsetup table" output between -2 and -1 (don't post it here, as it contains your key). What is the cryptsetup output?

The problem is a little weird, because the only difference between the two versions is that -2 suppresses the "Command successful" message when cryptsetup has successfully executed a "luksOpen" command (for nicer initscripts output), the rest is identical. I use cryptsetup without trouble on my machines.
Comment by Alexander Rink (freigeist) - Saturday, 13 January 2007, 21:57 GMT
I just looked in it again a few minutes ago and I can't reproduce the bug anymore, rebooting the system after the upgrade seemed to solve the problem. During the first upgrade (when the problem occurred) I was running kernel-ck for the first time, I upgraded crypt-setup and it wasn't working anymore, I downgraded and it worked again, today I upgraded, switched back to my beyond kernel and rebooted, now it's working fine. Sorry for the trouble.

Loading...