[arch-general] systemd + crypttab

2012-11-01 Thread André Vitor de Lima Matos 
Hi.
I've a system where there's a harddisk encrypted with luks and a lvm pv
over it, used for backup. This disk is never removed or inserted while
system is online, but not in every boot up it's present.
Setting this volume in crypttab, when disk is absent, cryptsetup service
hangs for several seconds, before timing out and allowing systemd to
complete boot. There's any way of avoiding this, may be putting it to
background, or something like this?
Thanks,



signature.asc
Description: OpenPGP digital signature

Re: [arch-general] systemd + crypttab

2012-11-01 Thread Dave Reisner 
On Thu, Nov 01, 2012 at 03:42:42PM -0200, André Vitor de Lima Matos wrote:
 Hi.
 I've a system where there's a harddisk encrypted with luks and a lvm pv
 over it, used for backup. This disk is never removed or inserted while
 system is online, but not in every boot up it's present.
 Setting this volume in crypttab, when disk is absent, cryptsetup service
 hangs for several seconds, before timing out and allowing systemd to
 complete boot. There's any way of avoiding this, may be putting it to
 background, or something like this?
 Thanks,
 

crypttab(5) explains that nofail is the option you want to use:

  nofail
 The system will not wait for the device to show up and be
 unlocked at boot, and not fail the boot if it doesn't show up.

You'll need this in /etc/fstab as well.

d

Re: [arch-general] systemd + crypttab

2012-11-01 Thread André Vitor de Lima Matos 
Didn't work. Still hanging for more than a minute.
journalctl gives me this entries:

Nov 01 13:18:36 midichlorian kernel: EXT4-fs (sdc2): mounted
filesystem with ordered data mode. Opts: (null)
Nov 01 13:18:36 midichlorian systemd[1]: Mounted /boot.
Nov 01 13:19:49 midichlorian systemd[1]: Job

dev-disk-by\x2duuid-1de06510\x2d7b5a\x2d4cb6\x2d9380\x2db7fcc586498e.device/start
timed out.
Nov 01 13:19:49 midichlorian systemd[1]: Timed out waiting for
device
dev-disk-by\x2duuid-1de06510\x2d7b5a\x2d4cb6\x2d9380\x2db7fcc586498e.device.
Nov 01 13:19:49 midichlorian systemd[1]: Dependency failed for
Cryptography Setup for Backup.
Nov 01 13:19:49 midichlorian systemd[1]: Dependency failed for
dev-mapper-Backup.device.
Nov 01 13:19:49 midichlorian systemd[1]: Job
dev-mapper-Backup.device/start failed with result 'dependency'.
Nov 01 13:19:49 midichlorian systemd[1]: Job
systemd-cryptsetup@Backup.service/start failed with result 'dependency'.
Nov 01 13:19:49 midichlorian systemd[1]: Job

dev-disk-by\x2duuid-1de06510\x2d7b5a\x2d4cb6\x2d9380\x2db7fcc586498e.device/start
failed with result 'timeout'.
Nov 01 13:19:49 midichlorian systemd[1]: Starting Local File Systems.
Nov 01 13:19:49 midichlorian systemd[1]: Reached target Local File
Systems.

Any idea?

Em 01-11-2012 16:03, Dave Reisner escreveu:
 On Thu, Nov 01, 2012 at 03:42:42PM -0200, André Vitor de Lima Matos wrote:
 Hi.
 I've a system where there's a harddisk encrypted with luks and a lvm pv
 over it, used for backup. This disk is never removed or inserted while
 system is online, but not in every boot up it's present.
 Setting this volume in crypttab, when disk is absent, cryptsetup service
 hangs for several seconds, before timing out and allowing systemd to
 complete boot. There's any way of avoiding this, may be putting it to
 background, or something like this?
 Thanks,

 crypttab(5) explains that nofail is the option you want to use:

   nofail
  The system will not wait for the device to show up and be
  unlocked at boot, and not fail the boot if it doesn't show up.

 You'll need this in /etc/fstab as well.

 d

-- 
/-=| ? ? ? ? ? |=-\ «» ???
http://www.google.com/profiles/andre.vmatos


signature.asc
Description: OpenPGP digital signature

Re: [arch-general] systemd + crypttab

2012-11-01 Thread Sebastian Schwarz 
On 2012-11-01 at 14:03 -0400, Dave Reisner wrote:
 crypttab(5) explains that nofail is the option you want to use:

I also have an encrypted drive which might be present
at boot or not, but nofail isn't working for me, or at
least not as expected.  I already filed a bug upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=54210

André, you could comment there whether nofail is working for
you or not.