[pkg-cryptsetup-devel] Bug#554506: Bug#554506: unable to find root volume

Harald Braumann harry at unheit.net
Thu Aug 19 23:21:24 UTC 2010


reopen 554506
tags 554506 patch
stop

Hi,

On Thu, Jul 08, 2010 at 12:58:02AM +0200, Jonas Meurer wrote:
> hey Harald,
> 
> On 28/06/2010 Harald Braumann wrote:
> > This bug also hits, if a source device name of the form /dev/<vg>/<lv> is used
> > in /etc/crypttab. The hook script fails to properly map this to 
> > /dev/mapper/<vg>-<lv>
> > 
> > The reason is, that dmsetup changed the way links are set up in /dev. Formerly,
> > files in /dev/<vg>/ (or /dev/disk/by-uuid) where links to device files in 
> > /dev/mapper/. Now they are links to /dev/dm-*. 
> > 
> > The solution is simple, and actually already there in the function 
> > `canonical_device'. I've just copied that part to `get_device_opts'. Patch 
> > appended.
> 
> cryptsetup svn trunk should have fixed this bug in a different way.
> canonical_device is now invoked both in get_root_device() and
> get_resume_devices(). could you verify that the new package fixes this
> bug for you?

sorry for not getting back to you sooner, I somehow lost track of this.

This bug is still not fixed for me in version 2:1.1.3-3. In my case,
the problem is, that the source device doesn't start with /dev/mapper.

I have attached another patch, which is equivalent to my previous
patch, but this time using canonical_device().

Cheers,
harry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: links2.patch
Type: text/x-diff
Size: 391 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20100820/012abf52/attachment.patch>


More information about the pkg-cryptsetup-devel mailing list