Problems with cryptsetup and udev on feisty

[Josef Wolf]

On Fri, Aug 24, 2007 at 01:38:47PM -0400, Paul S wrote:
> Josef Wolf said the following on 08/23/2007 03:32 PM:
> > Until last week, when I made "apt-get update; apt-get upgrade".  Now I
> > can't "cryptsetup luksOpen" any more: after I enter the passphrase,
> > cryptsetup simply hangs for several minutes.  Finally I get an error
> > report:
> > 
> >   # cryptsetup luksOpen /dev/sda11 crypted
> >   key slot 0 unlocked.
> >   Rendezvous with udev timed out for 'crypted'; stat failed: No such file or directory
> >   Command successful.
> >   # 
> > 
> > Although it claims that the command was succesful, the filesystem don't
> > appear in /dev/mapper.
> 
> I'm running feisty up to date and have no such problems.  Are you sure 
> you didn't foobar your encrypted file?

I am perfectly sure, because I can access the filesystem with grml (terminal
based live-cd, check out www.grml.org) without any problems.

> Did you try "sudo cryptsetup luksDump /dev/sda11" to check?  If
> everything is ok, try booting up the feisty CD, then add cryptsetup
> to the live session, then try opening your encrypted file from the
> live session .. just to prove that the file still works.

It definitely works.  The problem seems to be that some changes were made
to avoid race conditions when device-mapper creates a new device and udev
needs to notice it (sory, I don't understand the details)