All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Gergely Tamas <dice@mfa.kfki.hu>
Cc: Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: write barrier patches for 2.4.21
Date: Tue, 26 Aug 2003 13:13:53 +0400	[thread overview]
Message-ID: <20030826091353.GA788@namesys.com> (raw)
In-Reply-To: <20030826090348.GA29526@mfa.kfki.hu>

Hello!

On Tue, Aug 26, 2003 at 11:03:48AM +0200, Gergely Tamas wrote:
>  > > Where can I get Jens Axboe's + Chris Mason's (reiserfs) ide write
>  > > barrier patches for kernel 2.4.21 ?
>  > > I'd like to test a 3ware based raid setup (8xide) with write cache
>  > > enabled.
>  > I think that the patch does not have 3ware support. Only conventional IDE
>  > controllers are supported by the patch.
> Thanks.
> So the only way for production servers is still with write cache
> disabled.

Actually if you have some sort of uninterruptible power supply that never fails (and
you have correct shutdown scripts to shut the box down when its about to run out), you
are safe to use write cache.

Bye,
    Oleg

  reply	other threads:[~2003-08-26  9:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-25 17:08 write barrier patches for 2.4.21 Gergely Tamas
2003-08-26  8:17 ` Oleg Drokin
2003-08-26  9:03   ` Gergely Tamas
2003-08-26  9:13     ` Oleg Drokin [this message]
2003-08-26  9:32       ` Gergely Tamas
2003-08-26 21:46 ` Tom Vier
2003-08-27  6:41   ` Oleg Drokin
2003-08-27 22:03     ` Tom Vier
2003-08-28  0:37       ` Chris Mason
2003-08-28 17:07         ` Mike Fedyk
2003-08-29  0:07           ` Tom Vier
2003-08-29  1:18             ` Mike Fedyk
2003-08-29  1:44               ` Chris Mason
2003-08-29  1:56         ` Matthias Andree
2003-09-02 22:10     ` Hans Reiser
2003-09-04 14:56       ` Oleg Drokin
  -- strict thread matches above, loose matches on Subject: below --
2003-09-04 20:49 Tom Vier

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=20030826091353.GA788@namesys.com \
    --to=green@namesys.com \
    --cc=dice@mfa.kfki.hu \
    --cc=reiserfs-list@namesys.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.