mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicholas Knight <tegeran@home.com>
To: Matthias Andree <matthias.andree@stud.uni-dortmund.de>,
	linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: [PATCH] 2.4.10 improved reiserfs a lot, but could still be better
Date: Mon, 24 Sep 2001 13:05:38 -0700	[thread overview]
Message-ID: <20010924200537.SRVB23487.femail38.sdc1.sfba.home.com@there> (raw)
In-Reply-To: <B0005839269@gollum.logi.net.au> <20010924161518.KYHD11251.femail27.sdc1.sfba.home.com@there> <20010924185303.B10117@emma1.emma.line.org>
In-Reply-To: <20010924185303.B10117@emma1.emma.line.org>

On Monday 24 September 2001 09:53 am, Matthias Andree wrote:
> On Mon, 24 Sep 2001, Nicholas Knight wrote:
> > > Turn it off (I have no idea of internals, but I presume it'll
> > > still be a write-through cache, so reading back will still be
> > > served from the buffer). Do hdparm -W0 /dev/hd[a-h].
> >
> > I'm sorry, but that's not acceptable.
> > Please note the dd timings at the bottom of this message.
>
> Well, of course, turning off the cache will cause performance
> penalties, but it at least gives you a chance to get away with a
> recoverable file system should the power fail or the box crash.

Would you like to read the rest of my message please? Cheap UPS's can 
provide protection against power failures. If your data is that 
valuble, you can afford a cheap UPS to give you 5 minutes to shut down.

>
> > Yes, a typical desktop user isn't going to notice much, even a
> > normal webserver or fileserver not dealing with constant updates
> > may not, but certain workloads will. These workloads are real
> > enough that telling people to disable write caching out of hand is
> > a bad idea.
>
> I switched a box to ext3 with write caches off in expectance of
> multiple power outages during works, and NOTHING happened. I expect
> that box is now writing 4 times slower than before, I have no real
> figures, and it's still "smooth enough" in spite of 2.4.9.

Would you like to read it AGAIN? I specificaly said that MOST people 
would not notice a real difference.

>
> > Keep in mind also, that you may be putting your data and
> > filesystems in more risk by not using a write cache as with using
> > it.
>
> Utterly non-sense.
>
> Linear writing as dd mostly does is BTW something which should never
> be affected by write caches.

Explain the numbers then.
I followed *YOUR* instructions for disabling write caching.

  parent reply	other threads:[~2001-09-24 20:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-24 14:09 Beau Kuiper
2001-09-24 14:46 ` [reiserfs-list] " Chris Mason
2001-09-24 15:32 ` Matthias Andree
2001-09-24 15:45   ` Alan Cox
2001-09-24 15:47     ` Matthias Andree
2001-09-24 16:08       ` Alan Cox
2001-09-24 16:08         ` [reiserfs-list] " Chris Dukes
2001-09-24 16:54         ` Matthias Andree
2001-09-24 16:15   ` Nicholas Knight
2001-09-24 16:40     ` [reiserfs-list] " Lehmann 
2001-09-24 16:53     ` Matthias Andree
2001-09-24 16:57       ` [reiserfs-list] " Lehmann 
2001-09-25 14:04         ` bill davidsen
2001-09-25 17:39           ` bill davidsen
2001-09-24 20:05       ` Nicholas Knight [this message]
2001-09-25  0:11         ` Matthias Andree
2001-09-25  4:49           ` Nicholas Knight
2001-09-25  6:00             ` Beau Kuiper
2001-09-25  6:17               ` Nicholas Knight
2001-09-25 10:44               ` Matthias Andree
2001-09-25 11:01                 ` ben-lists
2001-09-25 10:42             ` Matthias Andree
2001-09-25 11:07               ` Nicholas Knight
2001-09-25 14:47           ` Alex Bligh - linux-kernel
2001-09-25 15:13             ` Matthias Andree
2001-09-25 15:23             ` John Alvord
2001-09-25 22:41               ` bill davidsen
2001-09-25 12:54     ` Jorge Nerín
2001-09-25 13:17       ` Matthias Andree
2001-09-25 13:06     ` [reiserfs-list] " Chris Mason
2001-09-24 21:58 Dieter Nützel
2001-09-25  0:19 ` Matthias Andree

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=20010924200537.SRVB23487.femail38.sdc1.sfba.home.com@there \
    --to=tegeran@home.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@stud.uni-dortmund.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®