From: Lars Marowsky-Bree <lmb@suse.de>
To: "Peter T. Breuer" <ptb@lab.it.uc3m.es>, linux-raid@vger.kernel.org
Subject: Re: [PATCH] secure write for RAID1
Date: Mon, 25 Apr 2005 14:33:28 +0200 [thread overview]
Message-ID: <20050425123328.GP32085@marowsky-bree.de> (raw)
In-Reply-To: <1toqj2-sjd.ln1@news.it.uc3m.es>
On 2005-04-23T22:48:01, "Peter T. Breuer" <ptb@lab.it.uc3m.es> wrote:
> This patch (completely untested of course - what, me?) makes RAID1 write
> to all components of a raid-1 array, else return error to the write
> attempt, when one component cannot be written.
Would it make sense to generalize and introduce a "write quorum" for
arrays with more than 2 mirrors - ie, must be committed to at least n
disks?
This would also apply to RAID6, actually. One could say that it needs to
be committed to N-1 disks; as RAID6 could cope with N-2 failures,
redundancy would still be preserved.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-04-25 12:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 20:48 [PATCH] secure write for RAID1 Peter T. Breuer
2005-04-25 12:33 ` Lars Marowsky-Bree [this message]
2005-04-25 15:52 ` Peter T. Breuer
2005-04-25 16:29 ` Peter T. Breuer
2005-04-25 17:03 ` Lars Marowsky-Bree
2005-04-27 3:24 ` Neil Brown
2005-04-27 6:05 ` Lars Marowsky-Bree
2005-04-27 11:26 ` Luca Berra
2005-04-28 12:34 ` Tom Coughlan
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=20050425123328.GP32085@marowsky-bree.de \
--to=lmb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=ptb@lab.it.uc3m.es \
/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).