From: Marian Csontos <mcsontos@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Need information
Date: Tue, 22 Feb 2022 11:48:16 +0100 [thread overview]
Message-ID: <CAJNi=XoHny8m_k9F-eRaJn7cQBtzraOgQycjU9JDdqLe2BcNNg@mail.gmail.com> (raw)
In-Reply-To: <7034cec6-0b44-b34e-8e91-3f0ec3e50d9c@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1439 bytes --]
Check `dmsetup udevcookies` output. lvcreate may be waiting for udev
process which timed out - check the syslog. You can forcefully complete a
transaction by `dmsetup udevcomplete <cookie>`
On Tue, Feb 22, 2022 at 11:06 AM Zdenek Kabelac <zdenek.kabelac@gmail.com>
wrote:
> Dne 21. 02. 22 v 12:00 Gk Gk napsal(a):
> > Hi,
> >
> > I work on cloud platforms and linux. I need some guidance with an issue
> > observed with LVM.
> >
> > How to forcefully kill a running lvm command like lvcreate ? I tried
> using
> > kill -9 but it is not killing it. Only a reboot seems to does the trick.
> How
> > to forcefully kill the lvcreate process or for that matter any running
> lvm
> > commands ?
> >
> > Also how to check the progress of an lvm command like lvcreate or
> lvremove ?
>
> Hi
>
> 1. lvm2 should not freeze - it would be some horrible bug.
>
> 2. You can't kill any userspace app which is blocked in an uninterruptible
> kernel function - kill always wait till it gets to signal handler (i.e.
> you
> are opening&reading suspended device might be one such operation)
>
> 3. You need to tell us more about what you are doing - as without this
> there
> is no way to give meaningful help.
>
>
> Regards
>
> Zdenek
>
> _______________________________________________
> 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/
>
>
[-- Attachment #1.2: Type: text/html, Size: 2120 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
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/
prev parent reply other threads:[~2022-02-23 7:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 11:00 [linux-lvm] Need information Gk Gk
2022-02-22 10:05 ` Zdenek Kabelac
2022-02-22 10:48 ` Marian Csontos [this message]
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='CAJNi=XoHny8m_k9F-eRaJn7cQBtzraOgQycjU9JDdqLe2BcNNg@mail.gmail.com' \
--to=mcsontos@redhat.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).