All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Francisco Javier Cabello <fjcabello@visual-tools.com>
Cc: reiserfs-list@namesys.com
Subject: Re: reiserfs and IDE write cache
Date: Fri, 18 Aug 2006 10:45:04 -0500	[thread overview]
Message-ID: <44E5E080.5040603@slaphack.com> (raw)
In-Reply-To: <200608180922.23867.fjcabello@visual-tools.com>

Francisco Javier Cabello wrote:
> Hello,
> I have been 'googling' and I have found a lot of people warning about the 
> problems with IDE write cache and journaling filesystems. 

These problems exist with ANY filesystem, journaling or not.  They also 
exist with no filesystem at all.

> Should I disable write cache in my systems using reiserfs3+2.4.25?

I'm not sure if it will help.  At least with IDE drives, I often cannot 
get the write cache disabled -- it's as if it ignores hdparm.

So, like Toby says, get a UPS.  Or get a laptop instead, if that makes 
any sense.

      parent reply	other threads:[~2006-08-18 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18  7:22 reiserfs and IDE write cache Francisco Javier Cabello
2006-08-18 14:20 ` Toby Thain
2006-08-18 14:20   ` Toby Thain
2006-08-18 15:45 ` David Masover [this message]

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=44E5E080.5040603@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=fjcabello@visual-tools.com \
    --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.