X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8B05D.D0F44A98@onstor-exch02.onstor.net>; Wed, 7 May 2008 09:17:16 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B05D.D0F44A98"
Content-class: urn:content-classes:message
Subject: RE: I'm closing the Cougar data corruption bug
Date: Wed, 7 May 2008 09:17:15 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E09CA61CA@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E09CA605B@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I'm closing the Cougar data corruption bug
Thread-Index: Aciv/9QTuAAv6RwgQeC8U63WtDoIbgAW3xXQ
References: <BB375AF679D4A34E9CA8DFA650E2B04E09CA605B@onstor-exch02.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Jonathan Goldick" <jonathan.goldick@onstor.com>
Cc: "dl-Cougar" <dl-Cougar@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B05D.D0F44A98
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

In my 7 years here at ONStor, this has been the hardest bug that I've
worked on.  The problem started with a statement that 16 bytes of data
was being corrupted once every couple of hours.  The hardest part was
that there was no idea where the corruption was happening in the system,
which is pretty daunting given the complexity of the system!  We were
finally able to come up with a solution through a concerted team effort
to narrow the problem down.  It was also critical that we were able to
make the corruption happen within a few minutes by using Jonathan's
nfsperftest. =20

Now that this bug has been cleared off the table, let's get the rest of
the bugs fixed so that we can ship Cougar!


Brian


> _____________________________________________=20
> From: 	Jonathan Goldick =20
> Sent:	Tuesday, May 06, 2008 10:04 PM
> To:	Brian Stark
> Cc:	dl-Cougar
> Subject:	I'm closing the Cougar data corruption bug
> Importance:	High
>=20
> Yes, this means what you think.  The maximum write load test
> simulating 800 clients didn't corrupt anything in the ~800GB of data
> written.  Spec ran without errors.  I think Brian got it.
>=20
> And a round of applause for Brian :-)
>=20
>=20

------_=_NextPart_001_01C8B05D.D0F44A98
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>RE: I'm closing the Cougar data corruption bug</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">In my 7 years here at ONStor, this has =
been the hardest bug that I've worked on.&nbsp; The problem started with =
a statement that 16 bytes of data was being corrupted once every couple =
of hours.&nbsp; The hardest part was that there was no idea where the =
corruption was happening in the system, which is pretty daunting given =
the complexity of the system!&nbsp; We were finally able to come up with =
a solution through a concerted team effort to narrow the problem =
down.&nbsp; It was also critical that we were able to make the =
corruption happen within a few minutes by using Jonathan's =
nfsperftest.&nbsp; </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Now that this bug has been cleared off =
the table, let's get the rest of the bugs fixed so that we can ship =
Cougar!</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Brian</FONT>
</P>
<BR>
<UL>
<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Jonathan Goldick&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Tuesday, May 06, 2008 10:04 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Brian Stark</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">dl-Cougar</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">I'm closing the Cougar data =
corruption bug</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Importance:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">High</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Yes, this means what you think.&nbsp; =
The maximum write load test simulating 800 clients didn&#8217;t corrupt =
anything in the ~800GB of data written.&nbsp; Spec ran without =
errors.&nbsp; I think Brian got it.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">And a round of applause for =
Brian</FONT> <FONT SIZE=3D2 FACE=3D"Wingdings">J</FONT>
</P>
<BR>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C8B05D.D0F44A98--
