X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C76658.F94C4FF4@onstor-exch02.onstor.net>; Wed, 14 Mar 2007 09:51:12 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: False ECC errors
Date: Wed, 14 Mar 2007 09:51:13 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02D8F34E@onstor-exch02.onstor.net>
In-Reply-To: <20070314095004.0d8f21dd@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: False ECC errors
Thread-Index: AcdmWNA63mGu3+5oQIGOUZt4oQ8aewAAA8Qg
References: <BB375AF679D4A34E9CA8DFA650E2B04E02D8F343@onstor-exch02.onstor.net> <20070314095004.0d8f21dd@ripper.onstor.net>
From: "Jonathan Goldick" <jonathan.goldick@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

I thought you discussed us using the ECC trap in more than just that
situation.  Oh well, I'll try and find the original source.

-----Original Message-----
From: Andy Sharp=20
Sent: Wednesday, March 14, 2007 9:50 AM
To: Jonathan Goldick
Subject: Re: False ECC errors

Wasn't me.  Max maybe?  Brian Stark?

Cheers,

a

On Wed, 14 Mar 2007 09:44:50 -0700 "Jonathan Goldick"
<jonathan.goldick@onstor.com> wrote:

> Andy,
>=20
> I seem to remember you mentioning that we report an ECC error when in
> reality this is an invalid pointer access.  Please confirm since we
> are still RMA'ing boxes for ECC errors that may not be real.
>=20
> Thanks,
>=20
> Jonathan
