Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: drbd-dev@linbit.com, linux-ha-dev@lists.linux-ha.org
Subject: Re: [Drbd-dev] Re: [Linux-ha-dev] [RFC] (CRM and) DRBD (0.8) states and transistions, recovery strategies
Date: Sat, 25 Sep 2004 11:59:24 +0200	[thread overview]
Message-ID: <20040925095924.GE4267@marowsky-bree.de> (raw)
In-Reply-To: <Hk8L7YsCaLPZMUXM+NGHIHM=lge@web.de>

On 2004-09-25T11:50:04,
   Lars Ellenberg <Lars.Ellenberg@linbit.com> said:

> well. they are different events, and I must handle both of them.
> there indeed is no benefit to it. but this is not about theoretically
> descibing it, in the end I want to code a state machine from it,
> and know that it is complete.

Ah. Ok. Then we agree.

> appart from the fact that the local storage should never fail,
> and should possibly be some sort of raid itself...

Right! It'd all be best if nothing ever failed! ;-)


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX AG - A Novell company


  reply	other threads:[~2004-09-25  9:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24 14:29 [Drbd-dev] [RFC] (CRM and) DRBD (0.8) states and transistions, recovery strategies Lars Ellenberg
2004-09-24 21:11 ` [Drbd-dev] Re: [Linux-ha-dev] " Lars Marowsky-Bree
2004-09-24 23:04   ` Lars Ellenberg
2004-09-25  8:54     ` Lars Marowsky-Bree
2004-09-25  9:50       ` Lars Ellenberg
2004-09-25  9:59         ` Lars Marowsky-Bree [this message]
2004-09-26 18:40   ` Andrew Beekhof
2004-09-27 12:19     ` Lars Ellenberg
2004-09-27 12:38       ` Andrew Beekhof
2004-09-27 14:52 ` [Drbd-dev] " Philipp Reisner
2004-09-29 12:58   ` Philipp Reisner
2004-09-29 17:07     ` Lars Ellenberg
2004-10-06 11:55       ` Philipp Reisner

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=20040925095924.GE4267@marowsky-bree.de \
    --to=lmb@suse.de \
    --cc=drbd-dev@linbit.com \
    --cc=linux-ha-dev@lists.linux-ha.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