From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Teigland Date: Fri, 29 Sep 2023 16:01:40 -0500 Subject: dmeventd is not respecting /etc/lvm/devices/system.devices In-Reply-To: References: Message-ID: <20230929210140.GA28125@redhat.com> List-Id: To: lvm-devel@redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Fri, Sep 29, 2023 at 12:18:07PM -0700, Eric Wheeler wrote: > Hello all, > > I am not sure how to resolve the dmeventd warning below, maybe you can > help. It appears that dmeventd is finding PVs attached to VMs, but those > volumes are not listed in /etc/lvm/devices/system.devices so, presumably, > they should be ignored by dmeventd. Thanks for bringing his up, it's a neglected and hidden corner of the devices file feature that's not well developed. The existing solution to this problem isn't great, but should work: create /etc/lvm/devices/dmeventd.devices, where dmeventd.devices contains devs for any VG where dmeventd is needed. That might be the same as system.devices (you could just copy system.devices to dmeventd.devices.) If you don't actually need dmeventd, then dmeventd.devices could be empty, or better just disable that service. Without a dmeventd.devices file, dmeventd does not use any devices file and looks at all PVs on the system, as you've seen. This was a quick way get around the fact that multiple devices files can be used, but dmeventd needs to service all of them. It turns out multiple devices files aren't really used by anyone, as far as I can tell (at least not yet.) The default should be for dmeventd to use system.devices, I expect we can make that change for the next release. > We used to use `global_filter` and that worked fine, but that seems to be > deprecated starting in el9 in favor of system.devices. If we try to enable > the filters in lvm.conf, then pvs/lvs/vgs commands complain about the > filter options being used together with `use_devicesfile=1`. Note that we > have PVs on LVs for ssd allocation to different VGs, so `scan_lvs=1` is > enabled. (Maybe turning off scan_lvs would "fix" dmeventd, but I can't > test that because we need PVs on LVs for this deployment.) I don't think scan_lvs will have any impact on this. > Aug 28 15:25:29 hv1.ewheeler.net dmeventd[886522]: WARNING: VG name data is used by VGs pcqIki-TjE0-iFMN-D8MH-19Er-ypSm-djfl5D and 9UEiuo-DYzj-UTLi-XYCi-KiBO-wQi2-w5QUtX. It's always been difficult to know what dmeventd is doing, and I wonder what it's running so frequently. Dave