[pkg-cryptsetup-devel] Bug#576646: Start cryptsetup-early after nbd-client

[Libor Klepáč]

Package: cryptsetup
Version: 2:1.1.0~rc2-1
Severity: wishlist

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,
I didn't want to fill a bug, I just asked in mailing list but it's not read maybe.
Here is my message.

- ----------
Hi,
I don't want to fill bug, I just want to ask.

We are setting up backup server, which will boot from nfs (this works, nfsroot 
created easily using debootstrap). Four local disks will be in raid5 (we are 
testing it in vmware now, so only one disk).

I have created luks on /dev/sda , then created lvm on top of it.

This host has to boot automatically and we dont want to have keyfile on 
filesystem of it. So i started nbd-server on other host and put key into it 
(1024B).
So on backup server crypttab looks like this
backup  /dev/sda       /dev/nbd0    luks,size=8192,noearly

Problem is that /etc/init.d/cryptdisks starts after lvm, so i put 
"/etc/init.d/lvm2 start" to rc.local.

nbd-client has to start before cryptdisks, so I added nbd-client to Required-Start field of cryptdisk. (And i have had to remove "X-Start-Before:    checkfs" so it doesn't complain about loop)

When i try to add nbd-client to cryptdisks-early (so luks is opened before lvm 
starts), insserv complains about loop. I don't know how to solve this, do you 
have any ideas please?

insserv -v -d
insserv: There is a loop between service cryptdisks-early and nbd-client if 
started
insserv:  loop involving service nbd-client at depth 7
insserv:  loop involving service networking at depth 6
insserv: There is a loop between service cryptdisks-early and nbd-client if 
started
insserv:  loop involving service lvm2 at depth 3
insserv:  loop involving service cryptdisks-early at depth 2
insserv:  loop involving service udev at depth 1
insserv:  loop involving service mountnfs at depth 10
insserv: There is a loop between service lvm2 and cryptdisks-early if started
insserv:  loop involving service checkfs at depth 16
insserv: exiting now without changing boot order!

Any ideas please? Or is this setup just to complicated/wrong?
- ---------

We are starting crypted as nonearly now , and we are starting lvm in rc.local now - no problem for us.

This wishlist is just to let you know about the loop.
It would be nice if there is some solution for this, maybe our setup is to insane to support ;)

With regards
Libor

- -- System Information:
Debian Release: squeeze/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-bfs311-bfs311 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJLuudFAAoJEPDvjG7Cn0eOSF8P/jDFQ16zrUsLyGI2xtqM6dcb
jvtpkZuOjWaXiTAT/lZ6JHDXWXtptAkTH6JJEneY+JGFhLy5OM8mEyfdJ6ljat9D
RnDujx2xjfMBRGGKCY+iQ/yQUgFoUaZTh/WBlGkwdsAnHKAMZW5H4gYDzhpRT212
VB5pywuDLkMXsLJhc/XVnwZsoJj0yMX5NVfLAuA/xqBU/E180fBeQDqoELEPSNC6
8nvO4si3aIvtN+maR8QxOQXnkjnEofG8qpvZ5Tuk++VWpoQe+8fSUFzw6/eCNH+t
iZ1tj4Lsn9iZYGxIN8x+rWLA2RNIqUVzfuzaxWX3tEyCpCvNU0KrRy9Hf4fv+LW2
PODjAtCiCM2JdAFq7hFgrnkl2MxPgj6d1SYtVhsI4hDt5IukPn+fRj/pC7R8tfaR
Kt/viLPhfsPvkZouk8RwbW2IwiM4moss2SboehkuZsw3gUC9NjH9hgBxED+MFOe5
GWYBTgQTSgjcs46U0XdNAWSTsqvyRRR3KUc1KyyyJcWktbsKQ3jNVaIXAxSgMd5O
0syE9NbB0iwsQOnd99MCcgEkGXyaSN76SCWtm22/nCSuHNFpz2s7Ry6NAfs1TANe
tztXqEKOpWMKaZKLRlg82xeUN5UHtZWq9hKsZ2ZYIDyY8ALErPDBHqXbKbb7Qp1f
qjUoNqTC/+jGFEXWhsT3
=PidW
-----END PGP SIGNATURE-----