linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zheng Lv <lv.zheng.2015@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm]  Power loss consistency for RAID
Date: Sun, 17 Mar 2019 23:05:23 +0800	[thread overview]
Message-ID: <69454a32-dee0-d57b-9be6-a4c02028f394@gmail.com> (raw)

Dear all,

I'm recently considering using software RAID instead of hardware 
controllers for my home server.

AFAIK, write operation on a RAID array is not atomic across disks. I'm 
concerned that what happens to RAID1/5/6/10 LVs after power loss.

Is manual recovery required, or is it automatically checked and repaired 
on LV activation?

Also I'm curious about how such recovery works internally.

Many thanks,
Zheng Lv

             reply	other threads:[~2019-03-17 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-17 15:05 Zheng Lv [this message]
2019-03-18  9:32 ` [linux-lvm] Power loss consistency for RAID Roberto Fastec
2019-03-18  9:35 ` Roberto Fastec
2019-03-18 12:38 ` Stuart D. Gathman

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=69454a32-dee0-d57b-9be6-a4c02028f394@gmail.com \
    --to=lv.zheng.2015@gmail.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).