archive mirror
 help / color / mirror / Atom feed
From: "Thomas Deutschmann" <>
To: "LVM general discussion and development" <>
Subject: Re: [linux-lvm] lvcreate hangs forever during snapshot creation when suspending volume
Date: Mon, 1 Aug 2022 22:34:56 +0200	[thread overview]
Message-ID: <000601d8a5e6$29a770d0$7cf65270$> (raw)
In-Reply-To: <>


I think there is a misunderstanding.

I am not calling LVM from any container.

I am calling LVM from the host system.

Also, please don't get confused that I mentioned systemd-nspawn. I am able to reproduce this problem without any container running on the host system.

Any other idea?



linux-lvm mailing list
read the LVM HOW-TO at

  reply	other threads:[~2022-08-01 20:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-30 16:33 [linux-lvm] lvcreate hangs forever during snapshot creation when suspending volume Thomas Deutschmann
2022-08-01 17:29 ` Zdenek Kabelac
2022-08-01 17:34   ` Zdenek Kabelac
2022-08-01 20:34     ` Thomas Deutschmann [this message]
2022-08-02  3:01       ` Thomas Deutschmann
2022-08-02 14:52         ` Zdenek Kabelac
2022-08-03  1:37           ` Thomas Deutschmann
2022-08-28 22:38             ` Thomas Deutschmann
2022-08-29 10:32               ` Zdenek Kabelac

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000601d8a5e6$29a770d0$7cf65270$' \ \ \

* 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).