[Request] Mask cryptsetup 1.0.7.

[Piotr Karbowski]

Hi.

I recommand hardmask >=sys-fs/cryptsetup-1.0.7.

http://code.google.com/p/cryptsetup/issues/detail?id=34

1.0.7 is in ~arch.

[Piotr Karbowski]

Just for record, in 10 times when I use cryptsetup-1.0.7, 3 times I
need restart system to get dmcrypt working. 1.0.6 work as it should.

[Erick Michau]

On Sat, Dec 26, 2009 at 9:34 PM, Piotr Karbowski <jabbe...@gmail.com> wrote:

Just for record, in 10 times when I use cryptsetup-1.0.7, 3 times I
need restart system to get dmcrypt working. 1.0.6 work as it should.

I use it system wide since the release in ~ (which is more recent than the provided link), reboot half a dozen times a day and never had any glitches, not a single one. I don't use lvm volumes maybe that's the culprit.

Could that be related to your lvm volumes? (I assume you have a luks/lvm setup given the provided link) because so far without lvm, cryptsetup-1.0.7 does exactly what it's supposed to do (in my case).

 

--

You received this message because you are subscribed to the Google Groups "Funtoo" group.
To post to this group, send email to funto...@googlegroups.com.
To unsubscribe from this group, send email to funtoo-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/funtoo-dev?hl=en.

[Piotr Karbowski]

No, I dont using lvm. Just dmcrypt. Funny is that I always was able to
mount rootfs but when system booted and tired to mount /home I got
from time to time issue "Command failed: device-mapper: create ioctl
failed: Device or resource busy".

Anyway, this is know bug. Work for you without problem, but not for
me. In order to get better system and prevent this bug I think this
version *should* be hardmasked.

[Erick Michau]

As I understood, you use cryptsetup to mount /home, not /, right? If so, then maybe udev (have you recently upgraded?) is doing something wrong. According to gmazyland on the provided issue link, seems that the reason cryptsetup-1.0.6 works in this case is because it uses internally udevsettle as it's not the case for 1.0.7.

If you are in an investigative mood, you could try bumping the cryptsetup-1.0.7-r1.ebuild to the new cryptsetup-1.1.0-rc3.

http://cryptsetup.googlecode.com/files/cryptsetup-1.1.0-rc3.tar.bz2

See if the problem remains, if so then it's udev messing around and not cryptsetup.

Keep us posted on how you fix your issue, I'm very interested in your feedback as I actively use cryptsetup.

Good luck

erick

[Piotr Karbowski]

I have both, rootfs (mounted by handwritten initramfs) and home
encrypted by dmcrypt

Thanks, I will try cryptsetup-1.1.0-rc3 and raport feedback.

To be honest it may be problem with udev or kernel but only new
cryptsetup have problem with it.