linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: "Peter T. Breuer" <ptb@lab.it.uc3m.es>, linux-raid@vger.kernel.org
Subject: Re: RAID1 and data safety?
Date: Tue, 29 Mar 2005 14:13:57 +0200	[thread overview]
Message-ID: <20050329121357.GK9998@marowsky-bree.de> (raw)
In-Reply-To: <8kqnh2-o1n.ln1@news.it.uc3m.es>

On 2005-03-29T13:26:32, "Peter T. Breuer" <ptb@lab.it.uc3m.es> wrote:

> > Not good advice.  DO put the journal on a raid device.  It is much
> > safer there.
> Two journals means two possible sources of unequal information - plus the
> two datasets.  We have been through this before. You get the journal
> you deserve.

The RAID never exposes this potential inconsistency to the higher levels
though.

Indeed, you get what you deserve.


-- 
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business


  reply	other threads:[~2005-03-29 12:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-29  8:54 AW: AW: RAID1 and data safety? Schuett Thomas EXT
2005-03-29  9:27 ` Peter T. Breuer
2005-03-29 10:09   ` Neil Brown
2005-03-29 11:26     ` Peter T. Breuer
2005-03-29 12:13       ` Lars Marowsky-Bree [this message]
2005-04-04 22:57       ` Doug Ledford
2005-03-29  9:30 ` AW: " Molle Bestefich
2005-03-29 10:08 ` AW: " Neil Brown
2005-03-29 11:29   ` Peter T. Breuer
2005-03-29 16:46     ` Luca Berra
2005-03-29 18:43       ` Peter T. Breuer
2005-03-29 20:07     ` Mario Holbe
2005-04-04 20:06     ` Doug Ledford
2005-04-08 12:16       ` Peter T. Breuer
  -- strict thread matches above, loose matches on Subject: below --
2005-04-07 15:35 AW: " Schuett Thomas EXT
2005-04-07 16:05 ` Doug Ledford
2005-04-10 17:54   ` Peter T. Breuer
2005-03-16  9:13 Molle Bestefich
2005-03-21 22:26 ` Neil Brown
2005-03-22  8:48   ` Molle Bestefich

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=20050329121357.GK9998@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).