From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Duncan Townsend <duncancmt@gmail.com>
Subject: Re: [linux-lvm] thin: pool target too small
Date: Wed, 23 Sep 2020 00:02:03 +0200 [thread overview]
Message-ID: <c675a85e-9739-cda9-5588-654337783182@redhat.com> (raw)
In-Reply-To: <CAODnkUCkbfvyq8mUpK1OEx5C1jgfmjyYauHzjcA12aGnY6kLGA@mail.gmail.com>
Dne 21. 09. 20 v 15:47 Duncan Townsend napsal(a):
> On Mon, Sep 21, 2020 at 5:23 AM Zdenek Kabelac <zkabelac@redhat.com> wrote:
>>
>> Dne 21. 09. 20 v 1:48 Duncan Townsend napsal(a):
>>> Hello!
>
> Ahh, thank you for the reminder. My apologies for not including this
> in my original message. I use Void Linux on aarch64-musl:
>
>>> I had a problem with a runit script that caused my dmeventd to be
>>> killed and restarted every 5 seconds. The script has been fixed, but
>>
>> Kill dmeventd is always BAD plan.
>> Either you do not want monitoring (set to 0 in lvm.conf) - or
>> leave it to it jobs - kill dmeventd in the middle of its work
>> isn't going to end well...)
>
> Thank you for reinforcing this. My runit script was fighting with
> dracut in my initramfs. My runit script saw that there was a dmeventd
> not under its control, and so tried to kill the one started by dracut.
> I've gone and disabled the runit script and replaced it with a stub
> that simply tried to kill the dracut-started dmeventd when it receives
> a signal.
Ok - so from looking at the resulting 'mixture' of metadata you
have in your archive and what physically present on PV header are
and now noticing this is some 'not-so-standard' distro - I'm starting to
suspect the reason of all these troubles.
Withing 'dracut' you shouldn't be firering dmeventd at all - monitoring
should be enabled (by vgchange --monitor y) once you switch to your rootfs
so dmenventd is execute from your rootfs!
By letting 'dmeventd' running in your 'dracut world' - it lives in its
own environment and likely its very own locking dir.
That makes it very easy your dmeventd runs in parallel with your other lvm2
commands - and since this way it's completely unprotected
(as file-locking is what it is) - as the resize is operation for several
seconds it has happened your 'admins' command replaced whatever dmeventd was
doing.
So I think to prevent repeated occurrence of this problem - you'll need
to ensure your system-booting will follow the pattern from distros
like Fedora.
Regards
Zdenek
next prev parent reply other threads:[~2020-09-22 22:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 23:48 [linux-lvm] thin: pool target too small Duncan Townsend
2020-09-21 9:23 ` Zdenek Kabelac
2020-09-21 13:47 ` Duncan Townsend
2020-09-22 22:02 ` Zdenek Kabelac [this message]
2020-09-23 18:13 ` Duncan Townsend
2020-09-23 18:49 ` Zdenek Kabelac
2020-09-23 19:54 ` Duncan Townsend
2020-09-24 17:54 ` Zdenek Kabelac
2020-09-26 13:30 ` Duncan Townsend
2020-09-29 14:33 ` Duncan Townsend
2020-09-29 15:53 ` Zdenek Kabelac
2020-09-30 18:00 ` Duncan Townsend
2020-10-02 13:05 ` Duncan Townsend
2020-10-09 21:15 ` Duncan Townsend
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=c675a85e-9739-cda9-5588-654337783182@redhat.com \
--to=zkabelac@redhat.com \
--cc=duncancmt@gmail.com \
--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).