public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>, linux-kernel@vger.kernel.org
Subject: Re: Thoughts on using fs/jbd from drivers/md
Date: Fri, 17 May 2002 11:29:42 -0700	[thread overview]
Message-ID: <20020517182942.GF627@matchmail.com> (raw)
In-Reply-To: <15587.18828.934431.941516@notabene.cse.unsw.edu.au> <20020516161749.D2410@redhat.com>

On Thu, May 16, 2002 at 04:17:49PM +0100, Stephen C. Tweedie wrote:
> Hi,
> 
> On Thu, May 16, 2002 at 03:54:20PM +1000, Neil Brown wrote:
> > The basic idea is to provide journaling for md/RAID arrays.  There
> > are two reasons that one might want to do this:
> >  1/ crash recovery.  Both raid1 and raid5 need to reconstruct the
> >    redundancy after a crash.  For a degraded raid5 array, this is not
> >    possible and you can suffer undetected data corruption.
> >    If we have a journal of recent changes we can avoid the
> >    reconstruction and the risk of corruption.
> 
> Right.  The ability of soft raid5 to lose data in degraded mode over a
> reboot (including data that was not being modified at the time of the
> crash) is something that is not nearly as widely understood as it
> should be, and I'd love for us to do something about it.

Are there workarounds to avoid this problem?

What does it take to trigger the corruption?

I ask this because I have used a degraded raid5 because the source drive
would become a member, but I needed to copy the data first.  While doing so,
I had to reboot a couple times to reconfigure the boot loader.  All seems to
be working fine on the system today though.

Thanks,

Mike

  reply	other threads:[~2002-05-17 18:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-16  5:54 Thoughts on using fs/jbd from drivers/md Neil Brown
2002-05-16 15:17 ` Stephen C. Tweedie
2002-05-17 18:29   ` Mike Fedyk [this message]
2002-05-17 18:34     ` Stephen C. Tweedie
2002-05-18  1:35       ` Mike Fedyk
2002-05-18 12:47         ` Stephen C. Tweedie
2002-05-21  9:03         ` Helge Hafting
2002-05-26  8:41   ` Daniel Phillips
2002-05-27 11:34     ` Stephen C. Tweedie
  -- strict thread matches above, loose matches on Subject: below --
2002-05-27 11:50 Neil Brown

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=20020517182942.GF627@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=sct@redhat.com \
    /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