archive mirror
 help / color / mirror / Atom feed
From: Demi Marie Obenour <>
To: LVM general discussion and development <>
Subject: Re: [linux-lvm] raid10 with missing redundancy, but health status claims it is ok.
Date: Mon, 30 May 2022 10:07:56 -0400	[thread overview]
Message-ID: <YpTPwJbsmG9Dr4X2@itl-email> (raw)
In-Reply-To: <>

[-- Attachment #1.1: Type: text/plain, Size: 1128 bytes --]

On Mon, May 30, 2022 at 10:16:27AM +0200, Olaf Seibert wrote:
> First, John, thanks for your reply.
> On 28.05.22 18:15, John Stoffel wrote:
> >>>>>> "Olaf" == Olaf Seibert <> writes:
> > 
> > I'm leaving for the rest of the weekend, but hopefully this will help you...
> > 
> > Olaf> Hi all, I'm new to this list. I hope somebody here can help me.
> > 
> > We will try!  But I would strongly urge that you take backups of all
> > your data NOW, before you do anything else.  Copy to another disk
> > which is seperate from this system just in case.
> Unfortunately there are some complicating factors that I left out so far.
> The machine in question is a host for virtual machines run by customers.
> So we can't just even look at the data, never mind rsyncing it.
> (the name "nova" might have given that away; that is the name of the 
> OpenStack compute service)

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?
Demi Marie Obenour (she/her/hers)
Invisible Things Lab

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 202 bytes --]

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

  parent reply	other threads:[~2022-05-30 14:08 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 [this message]
2022-05-31 11:27       ` Olaf Seibert

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=YpTPwJbsmG9Dr4X2@itl-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).