public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: Andi Kleen <ak@muc.de>,
	linux-kernel@vger.kernel.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	long <tlnguyen@snoqualmie.dp.intel.com>,
	Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
	Greg KH <greg@kroah.com>, Paul Mackerras <paulus@samba.org>,
	linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
	linux-pci@atrey.karlin.mff.cuni.cz, johnrose@us.ibm.com
Subject: Re: [PATCH 7/13]: PCI Err: Symbios SCSI  driver recovery
Date: Sat, 2 Jul 2005 02:21:29 -0600	[thread overview]
Message-ID: <20050702082129.GD14091@colo.lackof.org> (raw)
In-Reply-To: <20050629163408.GI28499@austin.ibm.com>

On Wed, Jun 29, 2005 at 11:34:08AM -0500, Linas Vepstas wrote:
...
> requests get replayed, in a fashion similar to what would be needed
> after a host reset.  In particular, there shouldn't be and (permanent)
> file system corruption because any inconsistent state on the disk 
> would get over-written when the queued reqeusts get re-issued.

FS's that require some ordering (journal) should be handling
this sort of stuff already. I have the same expectations as
Linas does WRT design. FS's that don't, will have the same sort
of problems that they would have as if the OS crashed.

> FWIW, yes, I have heard of devices that "cheat", and report back that a
> transaction is complete, even though it is still pending in firmware
> somewhere, either  on the host or the disk.  Those devices get screwed.

See "Write Cache Enabled" (aka WCE or in HPUX speak "Immediate Reporting").
WCE must be disabled if data corruption can not be tolerated.
"Desktop" (ie unix workstations) systems typically have WCE enabled
so they look good on (stupid) performance benchmarks.

The only devices that lie about WCE have battery backed RAM buffers.
(e.g. SCSI RAID *devices* - multi-LUN, dual controller beasts)

> No doubt, this will happen to some giant banking customer,

It won't happen because of WCE. None of the major HW vendors will
sell or support HW with WCE enabled. Exactly for the reasons you
point out.

grant

      reply	other threads:[~2005-07-02  8:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28 23:59 [PATCH 7/13]: PCI Err: Symbios SCSI driver recovery Linas Vepstas
2005-06-29  1:51 ` Benjamin Herrenschmidt
2005-06-29 20:48   ` Linas Vepstas
2005-06-29 23:41     ` Benjamin Herrenschmidt
2005-06-29  3:02 ` Andi Kleen
2005-06-29 16:34   ` Linas Vepstas
2005-07-02  8:21     ` Grant Grundler [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=20050702082129.GD14091@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=ak@muc.de \
    --cc=benh@kernel.crashing.org \
    --cc=greg@kroah.com \
    --cc=johnrose@us.ibm.com \
    --cc=linas@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=tlnguyen@snoqualmie.dp.intel.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