From: Christian Hesse <list@eworm.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] autoactivation fails
Date: Thu, 21 May 2015 14:19:55 +0200 [thread overview]
Message-ID: <20150521141955.70ebe714@leda.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
Hello everybody,
with recent lvm2 I had problems booting an Arch Linux system with non-systemd
initramfs. lvmetad is launched, but volumes are not activated. A git bisect
reported this bad commit:
commit fe30658a4d5fe4e4e6bb346c9c9ee7142a98f49d
Author: Ondrej Kozina <okozina@redhat.com>
Date: Mon Apr 13 16:29:15 2015 +0200
toollib: close connection to lvmetad after fork
sharing connection between parent command and background
processes spawned from parent could lead to occasional failures
due to unexpected corruption in daemon responses sent to either child
or a parent.
lvmetad issued warning about duplicate config values in request.
LVM commands occasionaly failed w/ internal error after receving
corrupted response.
lvmetad connection is renewed when needed after explicit disconnect
in child
Reverting this single commit makes everything work with git master
(v2_02_120-36-gba68aed) again.
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Chris get my mail address: */=0;b=c[a++];)
putchar(b-1/(/* gcc -o sig sig.c && ./sig */b/42*2-3)*42);}
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2015-05-21 12:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 12:19 Christian Hesse [this message]
2015-05-21 15:09 ` [linux-lvm] autoactivation fails Ondrej Kozina
2015-05-21 18:57 ` Christian Hesse
2015-05-21 19:50 ` Christian Hesse
2015-05-22 6:44 ` Ondrej Kozina
2015-05-25 7:16 ` Ondrej Kozina
2015-05-25 16:36 ` Christian Hesse
2015-05-26 8:06 ` Christian Hesse
2015-05-26 8:49 ` Ondrej Kozina
2015-05-26 12:05 ` Christian Hesse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150521141955.70ebe714@leda.localdomain \
--to=list@eworm.de \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).