[pkg-cryptsetup-devel] Bug#544487: Bug#544487: please try to reproduce with old cryptsetup

Carl Worth cworth at cworth.org
Sun Sep 20 21:04:53 UTC 2009


Excerpts from Jonas Meurer's message of Sun Sep 06 02:26:59 -0700 2009:
> On 05/09/2009 Jonas Meurer wrote:
> > thanks for your bugreport.

No problem.

> > could you try to reproduce the bug with the cryptsetup from
> > debian/testing[1]?
> > 
> > you can do so by installing (downgrading to) the cryptsetup 2:1.0.7-1
> > package and regenerating the initramfs with
> > # update-initramfs -u -k $(uname -r)
> > 
> > you might want to backup the working initramfs before.
> > 
> > i guess that the bug is not related to version 2:1.0.7-2 of the
> > cryptsetup package, as nothing regarding device symlinks etc. changed
> > between -1 and -2.
> 
> please try the attached (yet untested) patch, and see whether that fixes
> the bug for you. you'll need to update the initramfs after applying the
> patch.

Hi Jonas,

I really appreciate you following up and suggesting various things to
try. And I'm sorry I didn't get back to you sooner with any feedback.

Today I'm upgrading my kernel and needing to generate a new initramfs,
so I thought this would be the perfect time to test your proposed fix.

However, I found that an unmodified initramfs-tools is now generating
a functional initramfs for me.

Apparently something (certainly the upgrade of some package) changed
my setup so that my root filesystem is no longer a symlink. See the
contents of /etc/fstab and /etc/mtab below and contrast with the
contents I originally reported.

So things are working for me now, and apparently whatever was buggy
has been fixed. I do wish I could verify the patch you sent, but I
don't know that it would be wise for me to try getting my system into
a state such that I could test it.

-Carl

-- /etc/fstab 
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/mapper/yoom-root /               ext3    errors=remount-ro 0       1
/dev/sda1       /boot           ext2    defaults        0       2
/dev/mapper/yoom-swap_1 none            swap    sw              0       0

-- /etc/mtab 
/dev/mapper/yoom-root / ext3 rw,errors=remount-ro 0 0
tmpfs /lib/init/rw tmpfs rw,nosuid,mode=0755 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0
udev /dev tmpfs rw,mode=0755 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0
/dev/sda1 /boot ext2 rw 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,noexec,nosuid,nodev 0 0

-- $(ls -l /dev/mapper/)
total 0
crw-rw---- 1 root root  10, 60 2009-09-19 12:14 control
brw-rw---- 1 root root 254,  0 2009-09-19 12:14 sda2_crypt
brw-rw---- 1 root root 254,  1 2009-09-19 12:14 yoom-root
brw-rw---- 1 root root 254,  2 2009-09-19 12:14 yoom-swap_1
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20090920/53337a3a/attachment.pgp>


More information about the pkg-cryptsetup-devel mailing list