http://bugzilla.novell.com/show_bug.cgi?id=589016 http://bugzilla.novell.com/show_bug.cgi?id=589016#c Nikanth K changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |596448 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=589016 http://bugzilla.novell.com/show_bug.cgi?id=589016#c1 Nikanth K changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Basesystem AssignedTo|knikanth@novell.com |lnussel@novell.com Severity|Normal |Minor --- Comment #1 from Nikanth K 2010-04-20 06:49:22 UTC --- When cryptsetup is trying to remove the temporary dm device it created, the blkid called by an udev rule is holding the device open for a while. cryptsetup sleeps for a while and tries again. So everything is fine. But how to fix this ugly message? May be cryptsetup should do something like "udevadm settle" before trying to remove the device it just created? But retrying after sleeping for a while works as well, except for the ugly message from the kernel. Reassigning to cryptsetup maintainer. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=589016 http://bugzilla.novell.com/show_bug.cgi?id=589016#c3 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #3 from Ludwig Nussel 2010-04-20 09:21:03 CEST --- I think those upstream commits fix it: http://code.google.com/p/cryptsetup/source/detail?r=199 http://code.google.com/p/cryptsetup/source/detail?r=198 Someone just needs to backport the patches to 11.3 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.