All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: axboe@suse.de,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	jgarzik@pobox.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: journalling filesystems, linux 2.4.22, SATA drives
Date: Tue, 21 Sep 2004 16:49:43 +0100	[thread overview]
Message-ID: <1095781763.31269.9.camel@localhost.localdomain> (raw)
In-Reply-To: <4150485E.6000501@nortelnetworks.com>

On Maw, 2004-09-21 at 16:27, Chris Friesen wrote:
> use a journalled filesystem.  However the hardware guy says that turning off the 
> write cache also turns off the automatic error correction on writes, so the 
> write may return an error rather than being remapped silently.

I don't know how vendors handle this however he may be right, or it
may be vendor dependant. Have you asked which vendors do this and which
don't. Maybe you just need the right drive vendor. 

The Linux IDE layer will retry a failed write not sure about the 2.4.22
SATA code although the early versions probably were not business ready
anyway.

> What's the best way for me to deal with this?

For IDE you either

1. turn off write caching
2. buy a hardware raid card (which will turn off write caching or
   have battery backup or both 8))
3. accept that its unlikely to get burned in normal usage especially 
   with a UPS.

Alan


      reply	other threads:[~2004-09-21 16:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21 15:27 journalling filesystems, linux 2.4.22, SATA drives Chris Friesen
2004-09-21 15:49 ` Alan Cox [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=1095781763.31269.9.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=axboe@suse.de \
    --cc=cfriesen@nortelnetworks.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.