archive mirror
 help / color / mirror / Atom feed
From: Olaf Seibert <>
Subject: Re: [linux-lvm] raid10 with missing redundancy, but health status claims it is ok.
Date: Tue, 31 May 2022 13:27:21 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <YpTPwJbsmG9Dr4X2@itl-email>

On 30.05.22 16:07, Demi Marie Obenour wrote:
> Can you try to live-migrate the VMs off of this node?  If not, can you
> announce a maintenance window and power off the VMs so you can take a
> block-level backup?

Alas, this (type of) compute node is designed specifically to use local
storage instead of (shared) network storage. This prevents live migration.
If live migration were possible (and it would include migrating the
disk storage), then this would more or less automatically solve
the problem: on the new node the LV would be a fresh one
and thus nicely mirrored.

Maybe somebody could add support for something like that to OpenStack,
but right now it can't do it.


SysEleven GmbH
Boxhagener Straße 80
10245 Berlin

T +49 30 233 2012 0
F +49 30 616 7555 0

Aktueller System-Status immer unter:

Firmensitz: Berlin
Registergericht: AG Berlin Charlottenburg, HRB 108571 B
Geschäftsführer: Marc Korthaus, Jens Ihlenfeld, Andreas Hermann

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

      reply	other threads:[~2022-05-31 11:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 13:56 [linux-lvm] raid10 with missing redundancy, but health status claims it is ok Olaf Seibert
2022-05-28 16:15 ` John Stoffel
2022-05-30  8:16   ` Olaf Seibert
2022-05-30  8:49     ` Olaf Seibert
2022-06-01 21:58       ` John Stoffel
2022-05-30 14:07     ` Demi Marie Obenour
2022-05-31 11:27       ` Olaf Seibert [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:

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

  git send-email \ \ \ \

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