All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
	Jean-Eric Cuendet <Jean-Eric.Cuendet@linkvest.com>,
	linux-lvm@msede.com
Subject: Re: [linux-lvm] ReiserFS/XFS/JFS, LVM, Raid5
Date: Mon, 3 Jul 2000 18:16:14 +0100	[thread overview]
Message-ID: <20000703181614.N3284@redhat.com> (raw)
In-Reply-To: <20000703181627.A19757@gruyere.muc.suse.de>; from ak@suse.de on Mon, Jul 03, 2000 at 06:16:27PM +0200

Hi,

On Mon, Jul 03, 2000 at 06:16:27PM +0200, Andi Kleen wrote:
> On Mon, Jul 03, 2000 at 03:05:24PM +0100, Stephen C. Tweedie wrote:
> > The only known problem with journaling and software raid is to do with
> > the raid array rebuild code in raid1/5.  The rebuild could cause I/O
> > to be done in the wrong order for the filesystem, causing clean blocks
> > in the buffer cache to be flushed to disk as part of the rebuild.
> > That is fixed in the 2.4 soft raid.  raid0 and LVM were never affected
> > by this as they have no rebuild operation.
> 
> Note this applies only to the RAID1 in Raid 0.90 or in 2.4.
> Unpatched 2.2 does Raid1 reconstruction in user space only and should be 
> safe for journaling.

I think the user-space rebuild still has the same problem --- it
accesses the underlying raid device through the buffer cache, causing
clean buffers to be written to disk.  That's enough to kill
journaling.

Cheers,
 Stephen

  reply	other threads:[~2000-07-03 17:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-28  9:21 [linux-lvm] ReiserFS/XFS/JFS, LVM, Raid5 Jean-Eric Cuendet
2000-07-03 14:05 ` Stephen C. Tweedie
2000-07-03 16:16   ` Andi Kleen
2000-07-03 17:16     ` Stephen C. Tweedie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-28  9:23 Jean-Eric Cuendet
2000-06-28 12:26 ` Patrick Boutilier
2000-06-26 11:14 Jean-Eric Cuendet
2000-06-26 15:01 ` Brian Kress
2000-06-27 21:07 ` Patrick Boutilier

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=20000703181614.N3284@redhat.com \
    --to=sct@redhat.com \
    --cc=Jean-Eric.Cuendet@linkvest.com \
    --cc=ak@suse.de \
    --cc=linux-lvm@msede.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.