X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C864FF.CBEC16FF@onstor-exch02.onstor.net>; Fri, 1 Feb 2008 11:25:18 -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: data corruption problem in submittal 5
Date: Fri, 1 Feb 2008 11:25:18 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E080AF340@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0812A962@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: data corruption problem in submittal 5
Thread-Index: Achk75KPUo/xNMLbSjyeVikik3qHnQACaiRgAAAqLtAAAVwMsA==
From: "Jeff Miller" <IMCEAEX-_O=ONSTOR_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=JEFF+2EMILLER@onstor.com>
To: "Eric Barrett" <eric.barrett@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>,
	"dl-Escalation" <escal@onstor.com>

Note that this problem (change 27562) only occurs on Cougar hardware.
It was a problem in PCI hardware setup done by software, and is not
relevant to Bobcat or Cheetah at all.
Jeff


-----Original Message-----
From: Eric Barrett=20
Sent: Friday, February 01, 2008 9:43 AM
To: Jeff Miller; dl-Cougar; dl-Escalation
Subject: RE: data corruption problem in submittal 5

P4 change 27562?
=20

-----Original Message-----
From: Eric Barrett=20
Sent: Friday, February 01, 2008 9:40 AM
To: Jeff Miller; dl-Cougar; dl-Escalation
Subject: RE: data corruption problem in submittal 5

Your question is good and I'd like to see it answered.  As an aside, was
this problem in R98?  Do you know the defect or change # that fixes it?
We are fighting a probable user data corruption issue in 3.2.0.0 and
there's even been talk of a stop ship.  If it's been found and fixed
already, it will help tremendously.


-----Original Message-----
From: Jeff Miller=20
Sent: Friday, February 01, 2008 8:29 AM
To: dl-Cougar
Subject: data corruption problem in submittal 5

Change 27512, which went in after submittal 5, solves a serious data
corruption problem.  The corruption would occur during write to disk and
a few bytes (probably 16) would be incorrect in the data received by the
disk.  This problem showed up in Max's spec testing.

How much data integrity testing are we doing?  Can this problem be
easily reproduced somehow using sub5, and the fix then verified with
sub6?

Another thing to keep in mind is that an data written before submittal 6
may be
corrupted.

Jeff

