All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Vier <tmv@comcast.net>
To: Christian Mayrhuber <christian.mayrhuber@gmx.net>
Cc: reiserfs-list@namesys.com
Subject: Re: Need Warm Fuzzies, ReiserFS (3)
Date: Mon, 20 Dec 2004 14:23:25 -0500	[thread overview]
Message-ID: <20041220192325.GB12169@zero> (raw)
In-Reply-To: <200412201725.03216.christian.mayrhuber@gmx.net>

On Mon, Dec 20, 2004 at 05:25:03PM +0100, Christian Mayrhuber wrote:
> Disk barriers are only in since 2.6.9, so maybe these get turned on per 
> default after some more testing. That did happen to the data=ordered journal 
> mode.

I was under the impression that they were on by default. I wish this was
documented somewhere; it's very important and i bet a LOT of sysadmins don't
even consider the problems of having write-back caching enabled. At least
most scsi drives come with it disabled by default. There's only wb support
for ata and sata, fwih, too.

A quick grep didn't help me find if there's any other barrier mode other
than flush. It looked like reiserfs had support specifically for flush mode.
I would have thought it'd be done just as a call to something like blkwb().



What about software raid? Are the barriers pushed through the raid layer?



There's been some interesting discussion about this subject on the netbsd
tech-kern list, btw.

-- 
Tom Vier <tmv@comcast.net>
DSA Key ID 0x15741ECE

  parent reply	other threads:[~2004-12-20 19:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-20  5:41 Need Warm Fuzzies, ReiserFS (3) Jim Miller
2004-12-20 12:31 ` Christian Mayrhuber
2004-12-20 15:38   ` Tom Vier
2004-12-20 16:25     ` Christian Mayrhuber
2004-12-20 16:32       ` Spam
2004-12-20 20:24         ` Christian Mayrhuber
2004-12-20 20:31           ` Spam
2004-12-20 20:55             ` Christian Mayrhuber
2004-12-20 21:26             ` Tom Vier
2004-12-20 21:34               ` Spam
2004-12-21 15:49                 ` Tom Vier
2004-12-20 19:23       ` Tom Vier [this message]
2004-12-20 20:04         ` Christian Mayrhuber
2004-12-20 17:27 ` Hans Reiser

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=20041220192325.GB12169@zero \
    --to=tmv@comcast.net \
    --cc=christian.mayrhuber@gmx.net \
    --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.