On 21/11/2007 Dick Middleton wrote:
>> This leads to problems if you invoke cryptsetup as part of a udev role.
>
> rule (not role).
>
>> udevsettle waits until queued kernel/udev events are processed and the
>> 'run programs' have finished. Due to cryptsetup itself being a 'run
>> programm' in thi
Jonas,
great. I enhanced the documentation in README.Debian, but as i'm not a
native english speaker, I hereby ask you to proofread the text ;-)
Cryptsetup and udev
---
As a workaround for some yet-to-be-fixed race condition in kernel,
device-mapper or udev, cryptsetup curren
On 21/11/2007 Dick Middleton wrote:
>> Do you have any evidence?
>
> I looked at the source - udevsettle has a default timeout of 180s.
Ok, good to know. I just opened a bugreport against udev asking for
documentation of this default in the manpage.
> I checked that udevsettle as the only functi
Jonas Meurer wrote:
On 19/11/2007 Dick Middleton wrote:
I suspect that udevsettle is the one you added to cryptsetup. Maybe a
timeout would fix this?
udevsettle indeed supports a --timeout= option, and this would
workaround your delay.
maybe the reason for your 3 minutes delay is that udevsett
Jonas,
maybe the reason for your 3 minutes delay is that udevsettle has a builtin
timeout of 3 minutes.
That was my assumption.
Do you have any evidence?
er ... no ! Just the guesswork of the ignorant ;-)
It's just it hangs up every time for *exactly* 3 mins every time doing
something w
On 19/11/2007 Dick Middleton wrote:
>>> I suspect that udevsettle is the one you added to cryptsetup. Maybe a
>>> timeout would fix this?
>>
>> udevsettle indeed supports a --timeout= option, and this would
>> workaround your delay.
>
>> maybe the reason for your 3 minutes delay is that udevsettl
Jonas,
I suspect that udevsettle is the one you added to cryptsetup. Maybe a
timeout would fix this?
udevsettle indeed supports a --timeout= option, and this would
workaround your delay.
maybe the reason for your 3 minutes delay is that udevsettle has a builtin
timeout of 3 minutes.
Tha
On 18/11/2007 Dick Middleton wrote:
>> I prepared cryptsetup packages with the proposed patch applied. could
>> you give them a try?
>
> I just submitted this as a bug to udev (451702) completely forgetting the
> workaround recently made to cryptsetup. So FYI:
>
> --
> [...]
>
> What seems to be
Jonas Meurer wrote:
I prepared cryptsetup packages with the proposed patch applied. could
you give them a try?
I just submitted this as a bug to udev (451702) completely forgetting
the workaround recently made to cryptsetup. So FYI:
--
I have a run rule script which checks a block device f
On 17/10/2007 To David Härdeman wrote:
> > That's good to hear.
> >
> > Jonas, the race condition still remains in libdevmapper, this fix works
> > around it for cryptsetup so it still needs to be fixed in libdevmapper. I
> > say we reassign this bug, keep an eye on it and remove the Novell patch
On 17/10/2007 David Härdeman wrote:
> On Tue, October 16, 2007 20:16, Dick Middleton wrote:
> > Jonas Meurer wrote:
> >> I prepared cryptsetup packages with the proposed patch applied. could
> >> you give them a try?
> >
> > I'll try it a bit more determinedly later but the initial signs are good.
On Tue, October 16, 2007 20:16, Dick Middleton wrote:
> Jonas Meurer wrote:
>> I prepared cryptsetup packages with the proposed patch applied. could
>> you give them a try?
>>
>> you can find them at http://people.debian.org/~mejo/cryptsetup/
>
> I tried that; It works for me! Well ... er, I trie
Jonas Meurer wrote:
I prepared cryptsetup packages with the proposed patch applied. could
you give them a try?
you can find them at http://people.debian.org/~mejo/cryptsetup/
I tried that; It works for me! Well ... er, I tried 4 times and rebuilt initrd
which also worked properly. I notic
On 15/10/2007 Dick Middleton wrote:
> > The problem seems to be documented here (and the ubuntu patch to
> > libdevmapper seems to contain some relevant code):
> > https://wiki.ubuntu.com/UdevDeviceMapper
> >
> > So, I'm CC:ing the maintainers for libdevmapper and udev to ask their
> > advice befo
David Härdeman wrote:
The problem seems to be documented here (and the ubuntu patch to
libdevmapper seems to contain some relevant code):
https://wiki.ubuntu.com/UdevDeviceMapper
So, I'm CC:ing the maintainers for libdevmapper and udev to ask their
advice before I reassign this BR.
Have you s
On Oct 05, David Härdeman <[EMAIL PROTECTED]> wrote:
> The problem seems to be documented here (and the ubuntu patch to
> libdevmapper seems to contain some relevant code):
> https://wiki.ubuntu.com/UdevDeviceMapper
All of this needs to be fixed in the lvm packages, udev does not ship
any rules wh
On Mon, October 1, 2007 21:16, Dick Middleton wrote:
> Package: cryptsetup
> Version: 2:1.0.5-2
> Severity: important
>
>
> I have a curious effect; sometimes I get an error with luksOpen such as
> this:
>
> Failed to setup dm-crypt key mapping.
> Check kernel for support for the aes-cbc-plain ciph
On Wed, October 3, 2007 15:58, Dick Middleton wrote:
> David Härdeman wrote:
>
>> Thanks, could you now do one more thing for me? A strace from a
>> successful
>> invocation would be nice for comparison (I assume you've setup a test
>> partition for this considering the "testpwd" password that you
David Härdeman wrote:
Thanks, could you now do one more thing for me? A strace from a successful
invocation would be nice for comparison (I assume you've setup a test
partition for this considering the "testpwd" password that you use).
No, it's real; I just added a new password. Don't worry, I
On Wed, October 3, 2007 10:39, Dick Middleton wrote:
> David Härdeman wrote:
>>> strace echo -n x| cryptsetup luksOpen /dev/mapper/vg02-devil
>>> devil
>>
>> Sorry, but you need to have the strace call on the right hand side of
>> the
>> pipe ("echo -n xxx | strace ..."). Could you please try
David Härdeman wrote:
strace echo -n x| cryptsetup luksOpen /dev/mapper/vg02-devil devil
Sorry, but you need to have the strace call on the right hand side of the
pipe ("echo -n xxx | strace ..."). Could you please try again?
And it didn't seem to reproduce the same error (probably be
On Wed, October 3, 2007 00:04, Dick Middleton wrote:
> David Härdeman wrote:
>> On Tue, Oct 02, 2007 at 10:10:40PM +0100, Dick Middleton wrote:
>>> David Härdeman wrote:
On Mon, October 1, 2007 21:16, Dick Middleton wrote:
> I have a curious effect; sometimes I get an error with luksOpen s
On Tue, Oct 02, 2007 at 11:04:13PM +0100, Dick Middleton wrote:
> Is this helpful?
Could have been, but you got the wrong trace. :)
> strace echo -n x| cryptsetup luksOpen /dev/mapper/vg02-devil devil
Please try the following:
echo -n x | strace cryptsetup luksOpen /dev/mapper/vg02-de
David Härdeman wrote:
On Tue, Oct 02, 2007 at 10:10:40PM +0100, Dick Middleton wrote:
David Härdeman wrote:
On Mon, October 1, 2007 21:16, Dick Middleton wrote:
I have a curious effect; sometimes I get an error with luksOpen such as
this:
Failed to setup dm-crypt key mapping.
The first mes
On Tue, Oct 02, 2007 at 10:10:40PM +0100, Dick Middleton wrote:
David Härdeman wrote:
On Mon, October 1, 2007 21:16, Dick Middleton wrote:
I have a curious effect; sometimes I get an error with luksOpen such as
this:
Failed to setup dm-crypt key mapping.
The first message is usually reporte
On Mon, October 1, 2007 21:16, Dick Middleton wrote:
> I have a curious effect; sometimes I get an error with luksOpen such as
> this:
>
> Failed to setup dm-crypt key mapping.
> Check kernel for support for the aes-cbc-plain cipher spec and verify that
> /dev/mapper/vg02-devil contains at least 26
Package: cryptsetup
Version: 2:1.0.5-2
Severity: important
I have a curious effect; sometimes I get an error with luksOpen such as this:
Failed to setup dm-crypt key mapping.
Check kernel for support for the aes-cbc-plain cipher spec and verify that
/dev/mapper/vg02-devil contains at least 261
27 matches
Mail list logo
