mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: 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 17:47:45 +0200	[thread overview]
Message-ID: <20010924174745.A8230@emma1.emma.line.org> (raw)
In-Reply-To: <20010924173210.A7630@emma1.emma.line.org> <E15lXup-0002uj-00@the-village.bc.nu>
In-Reply-To: <E15lXup-0002uj-00@the-village.bc.nu>

On Mon, 24 Sep 2001, Alan Cox wrote:

> > > better. Decent write caching on IDE devices (like the 2meg buffer on the IBM) 
> > > can completely hide this issue.
> > 
> > Decent write caching on IDE devices can eat your whole file system.
> 
> YM bad write caching 8)

Well, drives do reorder their cache flushes, otherwise, they don't need
the cache.

> > 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].
> 
> You can't turn it off and on many drives you can't flush the cache either
> the operation is not implemented.

Those drives should be blacklisted and rejected as soon as someone tries
to mount those pieces rw. Either the drive can make guarantees when a
write to permanent storage has COMPLETED (either by switching off the
cache or by a flush operation) or it belongs ripped out of the boxes and
stuffed down the throat of the idiot who built it.

-- 
Matthias Andree

"Those who give up essential liberties for temporary safety deserve
neither liberty nor safety." - Benjamin Franklin

  reply	other threads:[~2001-09-24 15:47 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 [this message]
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
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=20010924174745.A8230@emma1.emma.line.org \
    --to=matthias.andree@stud.uni-dortmund.de \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome