archive mirror
 help / color / mirror / Atom feed
From: Marc Weber <>
Subject: [linux-lvm] RAID1 mirroring behavior when one disk is dead sometimes?
Date: Tue, 13 Apr 2021 17:52:53 +0200	[thread overview]
Message-ID: <> (raw)

I created a test with 2 disks then booted without disk2 then without disk1 (each time adding a file.

Then I booted with both. The result was in kernel logs I found 'mirroring or such' and I only got contents of disk 1.

Is there any option to say if both mirrors get changed don't mount but cause an error because that might be better than

getting newly written data reset randomly ?

Did I miss an option? Would mdadm be better ?

I tried looking at archives were CPU bottleneck for raids was mentioned often and 'work being done' on it.

What's status of that or are the advices given there still valid ?

Marc Weber

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

             reply	other threads:[~2021-04-13 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-13 15:52 Marc Weber [this message]
2021-04-13 19:44 ` Péter Sárközi
2021-04-15  4:19   ` [linux-lvm] RAID1 mirroring behavior when one disk is dead sometimes - why not just use random numbers ?? Marc Weber

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 \ \ \ \
    --subject='Re: [linux-lvm] RAID1 mirroring behavior when one disk is dead sometimes?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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