From: Oleksandr Natalenko <firstname.lastname@example.org> To: Martin Wilck <email@example.com> Cc: LVM general discussion and development <firstname.lastname@example.org>, Christian Hesse <email@example.com>, Heming Zhao <firstname.lastname@example.org>, Oleksandr Natalenko <email@example.com>, LVM general discussion and development <firstname.lastname@example.org> Subject: Re: [linux-lvm] [PATCH 1/1] pvscan: wait for udevd Date: Thu, 18 Feb 2021 16:30:09 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Hi. (will comment only on what I can comment, dropping the rest) On Thu, Feb 18, 2021 at 04:19:01PM +0100, Martin Wilck wrote: > > I'm not sure this issue is reproducible with any kind of LVM layout. > > What I have is thin-LVM-on-LUKS-on-LVM: > > I saw MD in your other logs...? FWIW, one of the machines have soft RAID, another does not, the issue is reproducible regardless of whether there's soft RAID or not. > > Feb 10 17:24:26 archlinux lvm: pvscan VG sys run > > autoactivation. > > Feb 10 17:24:26 archlinux lvm: /usr/bin/dmeventd: stat failed: > > No such file or directory > > What's going on here? pvscan trying to start dmeventd ? Why ? There's a > dedicated service for starting dmeventd (lvm2-monitor.service). I can > see that running dmeventd makes sense as you have thin pools, but I'm > at a loss why it has to be started at that early stage during boot > already. > > This is a curious message, it looks as if pvscan was running from an > environment (initramfs??) where dmeventd wasn't available. The message > is repeated, and after that, pvscan appears to hang... Not sure either. FWIW, real root is on a thin volume (everything is, in fact, except /boot and swap). > > Feb 10 17:24:26 archlinux lvm: pvscan PV /dev/md0 online. > > Feb 10 17:24:26 archlinux lvm: /usr/bin/dmeventd: stat failed: > > No such file or directory > > Feb 10 17:24:26 archlinux lvm: WARNING: Failed to monitor > > sys/pool. > > Feb 10 17:24:56 spock systemd: lvm2-pvscan@253:2.service: State > > 'stop-sigterm' timed out. Killing. > > Feb 10 17:24:56 spock systemd: lvm2-pvscan@253:2.service: Killing > > process 643 (lvm) with signal SIGKILL. > > Feb 10 17:24:56 spock systemd: lvm2-pvscan@253:2.service: Main > > process exited, code=killed, status=9/KILL > > Feb 10 17:24:56 spock systemd: lvm2-pvscan@253:2.service: Failed > > with result 'timeout'. > > Feb 10 17:24:56 spock systemd: Stopped LVM event activation on > > device 253:2. > > So what's timing out here is the attempt to _stop_ pvscan. That's > curious. It looks like a problem in pvscan to me, not having reacted to > a TERM signal for 30s. > > It's also worth noting that the parallel pvscan process for device 9:0 > terminated correctly (didn't hang). Yes, pvscan seems to not react to SIGTERM. I have DefaultTimeoutStopSec=30s, if I set this to 90s, pvscan hangs for 90s respectively. -- Best regards, Oleksandr Natalenko (post-factum) Principal Software Maintenance Engineer _______________________________________________ linux-lvm mailing list email@example.com https://listman.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2021-02-19 8:18 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-11 11:16 Christian Hesse [not found] ` <firstname.lastname@example.org> 2021-02-17 8:22 ` Martin Wilck [not found] ` <20210217130329.7de41147@leda> 2021-02-17 13:38 ` Oleksandr Natalenko 2021-02-18 15:19 ` Martin Wilck 2021-02-18 15:30 ` Oleksandr Natalenko [this message] 2021-02-19 9:22 ` Martin Wilck 2021-02-19 16:37 ` David Teigland 2021-02-19 22:47 ` Zdenek Kabelac 2021-02-21 20:23 ` Martin Wilck 2021-02-22 9:57 ` Zdenek Kabelac 2021-02-22 13:04 ` Christian Hesse 2021-02-25 16:51 ` Oleksandr Natalenko 2021-02-21 20:26 ` Martin Wilck 2021-02-17 13:49 ` Martin Wilck 2021-02-17 19:11 ` Oleksandr Natalenko
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [linux-lvm] [PATCH 1/1] pvscan: wait for udevd' \ /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
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).