Comment from upstream: > This is most likely a bug with either cryptsetup itself or how cryptsetup is > integrated into Debian. The root problem is that cryptsetup creates an > intermediate dm device before creating the real one (check with udevmonitor). > Am pretty sure your udev rules don't handle that correctly. Try adding rules > to > ignore the temporary node (match on the dm name) and I think it'll > work.
I'm CC'ing the cryptsetup maintainers for their opinion. -- Sam Morris <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
