archive mirror
 help / color / mirror / Atom feed
From: Roberto Fastec <>
To: LVM general discussion and development <>
Subject: Re: [linux-lvm] Power loss consistency for RAID
Date: Mon, 18 Mar 2019 10:32:45 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

it is automatic 

though you should avoid power losses as better as you can

with online PSU against line interactive ones ( which are good for consumer PCs and displays)

	  Messaggio originale  

Inviato: 18 marzo 2019 10:05
Rispondi a:
Oggetto: [linux-lvm] Power loss consistency for RAID

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

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

  reply	other threads:[~2019-03-18  9:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-17 15:05 [linux-lvm] Power loss consistency for RAID Zheng Lv
2019-03-18  9:32 ` Roberto Fastec [this message]
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:

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