From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 139CEC433F5 for ; Thu, 10 Mar 2022 07:46:16 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-486-J9w7cHKkMTmXQxeYEd4s2g-1; Thu, 10 Mar 2022 02:46:10 -0500 X-MC-Unique: J9w7cHKkMTmXQxeYEd4s2g-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5AC6F811E81; Thu, 10 Mar 2022 07:46:03 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id 458A5140EBFE; Thu, 10 Mar 2022 07:46:03 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id CA22B195FD43; Thu, 10 Mar 2022 07:45:59 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id F23301953541 for ; Wed, 9 Mar 2022 19:49:02 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id D0C867D037C; Wed, 9 Mar 2022 19:49:02 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast10.extmail.prod.ext.rdu2.redhat.com [10.11.55.26]) by smtp.corp.redhat.com (Postfix) with ESMTPS id CD4007D037B for ; Wed, 9 Mar 2022 19:49:02 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id AD2911C05B0D for ; Wed, 9 Mar 2022 19:49:02 +0000 (UTC) Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-573-fL9uCEoeMwu35SNL1srEcg-1; Wed, 09 Mar 2022 14:49:00 -0500 X-MC-Unique: fL9uCEoeMwu35SNL1srEcg-1 Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 37FE71F381; Wed, 9 Mar 2022 19:48:59 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id F2CED13D7C; Wed, 9 Mar 2022 19:48:58 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id fGtBOKoEKWIJTAAAMHmgww (envelope-from ); Wed, 09 Mar 2022 19:48:58 +0000 Message-ID: <166d9e5658f38f384a9938973a81c00c7abd75c9.camel@suse.com> From: Martin Wilck To: LVM general discussion and development Date: Wed, 09 Mar 2022 20:48:58 +0100 In-Reply-To: <20220309172606.GB5819@redhat.com> References: <38c190ac39c244d9442670589b7bfeb4f800383e.camel@suse.com> <20220309162711.GA5819@redhat.com> <06ec8ee06986abfe772485a44d6bb57781cb5718.camel@suse.com> <20220309172606.GB5819@redhat.com> User-Agent: Evolution 3.42.4 MIME-Version: 1.0 X-Mimecast-Impersonation-Protect: Policy=CLT - Impersonation Protection Definition; Similar Internal Domain=false; Similar Monitored External Domain=false; Custom External Domain=false; Mimecast External Domain=false; Newly Observed Domain=false; Internal User Name=false; Custom Display Name List=false; Reply-to Address Mismatch=false; Targeted Threat Dictionary=false; Mimecast Threat Dictionary=false; Custom Threat Dictionary=false X-Scanned-By: MIMEDefang 2.85 on 10.11.54.9 X-Mailman-Approved-At: Thu, 10 Mar 2022 07:45:56 +0000 Subject: Re: [linux-lvm] LVM autoactivation and udev X-BeenThere: linux-lvm@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: LVM general discussion and development Cc: Peter Rajnoha , Heming Zhao Errors-To: linux-lvm-bounces@redhat.com Sender: "linux-lvm" X-Scanned-By: MIMEDefang 2.85 on 10.11.54.7 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=linux-lvm-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Wed, 2022-03-09 at 11:26 -0600, David Teigland wrote: > > > > If we started pvscan later, in RUN, and a VG became complete, > > instead > > of printing the VG name to stdout, it could run the "systemd-run" > > command for lvm-activate-${VG}, which is currently called in 69-dm- > > lvm.rules, directly instead, by fork()ing and exec()ing > > "systemd-run". > > That was what I meant. Just a thought, not sure if it really works. > > Having pvscan fork systemd-run vgchange -aay doesn't sound nice at > all. > The point of this new design is clean up and simplify things, > separating > the scanning from the activation: pvscan just scans the device, and > vgchange activates the VG. It was just a thought, trying to figure out a way to move this logic in to RUN completely, so that pvscan would be able to access udev properties. I'll wait for the fix for the external_device_info_source=udev case, which you mentioned in your previous post. Thanks, Martin _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://listman.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/