From: Lars Marowsky-Bree <lmb@suse.de>
To: Circuitsoft Development <circuitsoft.devel@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: Fwd: Extended Volume Manager API
Date: Mon, 8 May 2006 23:51:36 +0200 [thread overview]
Message-ID: <20060508215136.GQ5856@marowsky-bree.de> (raw)
In-Reply-To: <64b292120605081417y1684cba4kfb85ce39c14df0f7@mail.gmail.com>
On 2006-05-08T16:17:07, Circuitsoft Development <circuitsoft.devel@gmail.com> wrote:
> I'm not. They also need to get permission from the network before they
> write to the disk, and they're not going to get permission without
> hearing back from everybody. Besides, since the same network is used
> to connect to the disks as is used to connect the computers to each
> other, how would it be able to access the disks without being able to
> access other computers which also connect to the disks?
You really should read up about split-brain scenarios, quorum, IO
fencing, cluster membership algorithms and the amazing variety of
different types of crashes.
Sincerely,
Lars Marowsky-Brée
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
next prev parent reply other threads:[~2006-05-08 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 5:26 Circuitsoft Development
2006-05-01 7:02 ` Valdis.Kletnieks
[not found] ` <64b292120605010759h4d9c74d7s717d125018ab95d3@mail.gmail.com>
2006-05-01 20:10 ` Fwd: " Circuitsoft Development
2006-05-02 12:42 ` Rik van Riel
[not found] ` <64b292120605062123gdb302d2g201fa59e93bc6a25@mail.gmail.com>
2006-05-08 21:17 ` Fwd: " Circuitsoft Development
2006-05-08 21:51 ` Lars Marowsky-Bree [this message]
2006-05-09 7:24 ` Circuitsoft Development
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=20060508215136.GQ5856@marowsky-bree.de \
--to=lmb@suse.de \
--cc=circuitsoft.devel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®