From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 941691381FA for ; Wed, 7 May 2014 06:11:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0653FE09F1; Wed, 7 May 2014 06:11:54 +0000 (UTC) Received: from smtpq2.tb.mail.iss.as9143.net (smtpq2.tb.mail.iss.as9143.net [212.54.42.165]) by pigeon.gentoo.org (Postfix) with ESMTP id CCE4CE09CB for ; Wed, 7 May 2014 06:11:52 +0000 (UTC) Received: from [212.54.42.137] (helo=smtp6.tb.mail.iss.as9143.net) by smtpq2.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1Whv56-0001Nx-1J for gentoo-user@lists.gentoo.org; Wed, 07 May 2014 08:11:52 +0200 Received: from 53579160.cm-6-8c.dynamic.ziggo.nl ([83.87.145.96] helo=data.antarean.org) by smtp6.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1Whv55-0005nU-GQ for gentoo-user@lists.gentoo.org; Wed, 07 May 2014 08:11:52 +0200 Received: from andromeda.localnet (unknown [10.20.13.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by data.antarean.org (Postfix) with ESMTPSA id 305D64C for ; Wed, 7 May 2014 08:11:50 +0200 (CEST) From: "J. Roeleveld" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Problems with loop-aes Date: Wed, 07 May 2014 08:11:02 +0200 Message-ID: <2812089.ihluqybgHf@andromeda> User-Agent: KMail/4.11.5 (Linux/3.10.25-gentoo; KDE/4.11.5; x86_64; ; ) In-Reply-To: <20140506213452.GA30163@waltdnes.org> References: <20140506183108.GA29693@waltdnes.org> <15054377.ZrtTjlGeGV@andromeda> <20140506213452.GA30163@waltdnes.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Ziggo-spambar: ---- X-Ziggo-spamscore: -4.8 X-Ziggo-spamreport: ALL_TRUSTED=-1,BAYES_00=-1.9,PROLO_TRUST_RDNS=-3,RDNS_DYNAMIC=0.982,TW_LV=0.077 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-Archives-Salt: fd2ca5c8-0d5f-4f01-9fc5-e8808203b2d6 X-Archives-Hash: ba3530e82190d564bdb445842c63044f On Tuesday, May 06, 2014 05:34:52 PM Walter Dnes wrote: > On Tue, May 06, 2014 at 08:45:01PM +0200, J. Roeleveld wrote > > > On Tuesday, May 06, 2014 02:31:08 PM Walter Dnes wrote: > > > I'm trying to set up USB-key-encryption for use with a laptop. I'm > > > > > > running mdev instead of udev on the laptop, so lvm doesn't work. > > > > I find this strange, as LVM can manage the /dev-entries directly. > > On my systems, this is necessary as udev regularly fails to properly > > handle > > these entries. > > > > Eg. the following setting: " verify_udev_operations = 1 " > > There are other options for udev documented in /etc/lvm/lvm.conf. > > Unfortunately, mdev != udev. People running RAID have problems too. I know it isn't. I just find it strange that LVM can't work without udev when I see options which configure the LVM-tools to either double-check udevs actions or even completely bypass udev: *** # Set to 0 to disable udev synchronisation (if compiled into the binaries). # Processes will not wait for notification from udev. # They will continue irrespective of any possible udev processing # in the background. You should only use this if udev is not running # or has rules that ignore the devices LVM2 creates. # The command line argument --nodevsync takes precedence over this setting. # If set to 1 when udev is not running, and there are LVM2 processes # waiting for udev, run 'dmsetup udevcomplete_all' manually to wake them up. udev_sync = 1 # Set to 0 to disable the udev rules installed by LVM2 (if built with # --enable-udev_rules). LVM2 will then manage the /dev nodes and symlinks # for active logical volumes directly itself. # N.B. Manual intervention may be required if this setting is changed # while any logical volumes are active. udev_rules = 1 # Set to 1 for LVM2 to verify operations performed by udev. This turns on # additional checks (and if necessary, repairs) on entries in the device # directory after udev has completed processing its events. # Useful for diagnosing problems with LVM2/udev interactions. verify_udev_operations = 1 *** > > I believe " cryptsetup " does not use the LVM tools. But has a new device > > created by the kernel directly, which should be picked up by a device > > manager directly. > > But cryptsetup pulls in lvm2 as a dependancy... > > [d531][waltdnes][~] emerge -pv cryptsetup > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild N ] sys-fs/lvm2-2.02.103 USE="readline (-clvm) (-cman) -lvm1 > -lvm2create_initrd (-selinux) -static -static-libs -thin -udev" 1,313 kB > [ebuild N ] sys-fs/cryptsetup-1.6.2 USE="openssl -gcrypt -kernel > -nettle -nls -python -reencrypt -static -static-libs -udev -urandom" > PYTHON_SINGLE_TARGET="python2_7 -python2_6" PYTHON_TARGETS="python2_7 > -python2_6" 1,162 kB You need it for the device-mapper stuff. That might also listen to the above setting in /etc/lvm/lvm.conf. Can you try setting the above one to " 0" and re-test? I don't have any machine with mdev to test myself. Also, the following page seems to indicate cryptsetup, LVM and mdev do work together: http://jootamam.net/howto-basic-cryptsetup.htm This works inside an initramfs and I don't see a reason why it can't work outside of the initramfs. -- Joost