X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C798BA.288014D0@onstor-exch02.onstor.net>; Thu, 17 May 2007 12:32:51 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C798BA.288014D0"
Content-class: urn:content-classes:message
Subject: RE: 2.2.2.5  w/n boot
Date: Thu, 17 May 2007 12:32:51 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E03C0C183@onstor-exch02.onstor.net>
In-Reply-To: <012f01c798aa$2c111dd0$0602a8c0@GH033>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: 2.2.2.5  w/n boot
Thread-Index: AceXyFGHaAMHX0y7RvaIs+G3KRP0owACV5LTAABqyEMABDU18AAAQurMAAE3k8QADAj6IAAAQCkQAAEUn30AHmW0UAAAswigAAA4R0AAAVbjIAAALJ8CAABoKIAAAHTNIAAAnW1gAARILCA=
From: "Paul Hammer" <paul.hammer@onstor.com>
To: "Victor Carrell (Glasshouse)" <vcarrell@css.glasshouse.com>,
	"Frontline Support" <support@cc.onstor.com>,
	"Ken Renshaw" <ken.renshaw@onstor.com>,
	"Huy Duong" <huy.duong@onstor.com>,
	"Rex Yuan" <rex.yuan@onstor.com>,
	"Erik Palomba" <erik.palomba@onstor.com>,
	"Raghu Murthy" <raghu.murthy@onstor.com>,
	"Danqing Jin" <danqing.jin@onstor.com>,
	"David Crispin" <david.crispin@onstor.com>,
	"dl-cstech" <dl-cstech@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C798BA.288014D0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All,

        We now understand what caused the issues found in the field with
the 2.2.2.5 and 1.3.3.16 patches.

The problem was caused by an inadvertent Perforce sync or file copy to
the wrong location in our build storage area /n/Build-Trees/BSD.=20

This caused two of our objects to become corrupted. That object was then
included in these patches.

The problem was not caught during testing due to a deviation from the
approved test work flow.

To fix this we are doing the following:

First: Awareness, folks need to verify where they are syncing to in
order to avoid corrupting the depot.

Second: Testing will correct the deviation in testing and only follow
the supported/documented workflow and test procedure.

Third: Build will wall off a golden version of the objects so that they
cannot be written to inadvertently. Build will also create delta BOMs
for every patch so we can audit which files changed and approve the list
prior to release.

Please let me know if you have any questions on this matter.

-Paul

=20

=20

________________________________

From: Victor Carrell (Glasshouse)=20
Sent: Thursday, May 17, 2007 10:38 AM
To: Frontline Support; Ken Renshaw; Huy Duong; Rex Yuan; Erik Palomba;
Raghu Murthy; Danqing Jin; David Crispin; dl-cstech
Subject: RE: 2.2.2.5 w/n boot

=20

Let me ask another way.  Will 2.2.2.7 have the cifsd fix included with
the ECC fix?  If not why?

=20

If so why would one go to 2.2.2.6 verses 2.2.2.7? Or why would 2.2.2.6
even be distributed if both fixes are in 2.2.2.7?

=20

From Ken's statement all three will be ready today.

=20

I'm just trying to understand the logic to best serve our customers.  I
have already been asked by Nissho which version to upgrade to.  Do I
tell them to wait a few days or  tell them to go to 2.2.2.4 knowing
there are 2 important fixes coming in a few days then upgrade again when
they crash?

=20

Thanks

Victor

=20

________________________________

From: support@cc.onstor.com [mailto:support@cc.onstor.com]=20
Sent: Thursday, May 17, 2007 1:16 PM
To: Frontline Support; Ken Renshaw; Huy Duong; Rex Yuan; Erik Palomba;
Raghu Murthy; Danqing Jin; David Crispin; dl-cstech
Subject: RE: 2.2.2.5 w/n boot

=20

When and why your customer want to upgrade?  2.2.2.6 fixes a cifsd
issue.

Patch 2.2.2.7 is for ECC errors.  It will take at least a few more days
of testing by the hardware folks.

=20

________________________________

From: Frontline Support=20
Sent: Thursday, May 17, 2007 9:59 AM
To: Ken Renshaw; Huy Duong; Rex Yuan; Erik Palomba; Raghu Murthy;
Danqing Jin; Ed Kwan; David Crispin; dl-cstech
Cc: Frontline Support
Subject: RE: 2.2.2.5 w/n boot

=20

If a customer asks which to load 2.2.2.6 or 2.2.2.7 what would be the
answer?

=20

Victor

=20

________________________________

From: Ken Renshaw [mailto:ken.renshaw@onstor.com]=20
Sent: Thursday, May 17, 2007 12:46 PM
To: Huy Duong; Rex Yuan; Erik Palomba; Raghu Murthy; Danqing Jin; Ed
Kwan; David Crispin; Victor Carrell (Glasshouse); dl-cstech
Cc: Frontline Support
Subject: Re: 2.2.2.5 w/n boot

=20

2.2.2.5 is being rebuilt as 2.2.2.6 right now. I'll fix 1.3.3.16 next,
then the ECC patch which hadn't shipped yet as 2.2.2.7.

All three should be ready today.

Thanks,

-Ken



-----Original Message-----
From: Huy Duong
To: Rex Yuan; Erik Palomba; Raghu Murthy; Ken Renshaw; Danqing Jin; Ed
Kwan; David Crispin; Victor Carrell (Glasshouse); dl-cstech
CC: Frontline Support
Sent: Thu May 17 09:42:48 2007
Subject: RE: 2.2.2.5  w/n boot

Did we determine how we are  re-spinning these patches?

-----Original Message-----
From: Rex Yuan
Sent: Thursday, May 17, 2007 9:04 AM
To: Erik Palomba; Raghu Murthy; Ken Renshaw; Danqing Jin; Ed Kwan; Huy
Duong; David Crispin; Victor Carrell (Glasshouse); dl-cstech
Cc: Frontline Support
Subject: RE: 2.2.2.5 w/n boot

1.3.3.16 has been pulled.

-----Original Message-----
From: Erik Palomba
Sent: Thursday, May 17, 2007 8:57 AM
To: Raghu Murthy; Ken Renshaw; Danqing Jin; Ed Kwan; Huy Duong; David
Crispin; Victor Carrell (Glasshouse); dl-cstech
Subject: RE: 2.2.2.5 w/n boot

I just confirmed that 1.3.3.16 has the same problem as 2.2.2.5. Please
pull the patch.

-----Original Message-----
From: Raghu Murthy
Sent: Thursday, May 17, 2007 8:43 AM
To: Ken Renshaw; Danqing Jin; Ed Kwan; Huy Duong; David Crispin; Victor
Carrell (Glasshouse); dl-cstech
Cc: Erik Palomba
Subject: RE: 2.2.2.5 w/n boot

Ken,

So do we have exposure on 1.3.3.16 as well?
Raghu
 ------------------
From: Alan Cooke (Glasshouse)
Sent: Thursday, May 17, 2007 5:37 AM
To: Alan Cooke (Glasshouse); dl-Customer-Engineering; Frontline Support;
dl-cstech
Subject: RE: Failure to boot OS may be in 1.3.3.16 too

Hi All,

Just confirmed this failure with trying to upgrade a Cheetah system in
the Glasshouse lab going from 1.3.3.14 to 1.3.3.16 We had to swap the CF
cards to get the system back.
This is a fairly conclusive failure so I would request this release is
removed from the FTP site ASAP please.

Thanks ... Alan.

-----Original Message-----
From: Ken Renshaw
Sent: Wednesday, May 16, 2007 6:06 PM
To: Danqing Jin; Raghu Murthy; Ed Kwan; Huy Duong; David Crispin; Victor
Carrell (Glasshouse); dl-cstech
Cc: Erik Palomba
Subject: Re: 2.2.2.5 w/n boot

Versions thru 2.2.2.4 do not have this issues.

-Ken



-----Original Message-----
From: Danqing Jin
To: Raghu Murthy; Ken Renshaw; Ed Kwan; Huy Duong; David Crispin; Victor
Carrell (Glasshouse); dl-cstech
CC: Erik Palomba
Sent: Wed May 16 17:35:47 2007
Subject: RE: 2.2.2.5  w/n boot

They are safe, as this issue occurs only in 2.2.2.5.

________________________________

From: Raghu Murthy
Sent: Wednesday, May 16, 2007 5:35 PM
To: Ken Renshaw; Ed Kwan; Huy Duong; David Crispin; Victor Carrell
(Glasshouse); dl-cstech
Cc: Danqing Jin; Erik Palomba
Subject: RE: 2.2.2.5 w/n boot



I know we have yanked 2.2.2.5 from the FTP site. Since 2.2.2.5 was
failing the upgrade process while the others 2.2.2.3 and 2.2.2.4 did
not, any idea what is the exposure for the sites that successfully
upgraded to 2.2.2.3 and 2.2.2.4 but still have the incorrect /etc files?



Raghu



________________________________

From: Ken Renshaw
Sent: Wednesday, May 16, 2007 11:44 AM
To: Ken Renshaw; Ed Kwan; Huy Duong; David Crispin; Victor Carrell
(Glasshouse); dl-cstech
Cc: Danqing Jin; Erik Palomba
Subject: RE: 2.2.2.5 w/n boot



From now on I will add a step in the build process for patches to do a
quick file delta from the previous patch and include that in the build
info. Hopefully that will help us flag these kinds of things before they
leave the building.



Thanks,



-Ken



________________________________

From: Ken Renshaw
Sent: Wed 5/16/2007 11:37 AM
To: Ed Kwan; Huy Duong; David Crispin; Victor Carrell (Glasshouse);
dl-cstech
Cc: Danqing Jin; Erik Palomba; Ken Renshaw
Subject: RE: 2.2.2.5 w/n boot

Hello.



The last four patches have all been done with the same build of bsd:



[build@k2 Build-Trees]$ strings
R2.2.2.3/R2.2.2.3-041807/nfx-tree/Build/bc/opt/Release/bsd | grep
OpenBSD| grep BOBCAT
    @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 13:34:43 PST 2007
[build@k2 Build-Trees]$ strings
R2.2.2.4/R2.2.2.4-042507/nfx-tree/Build/bc/opt/Release/bsd | grep
OpenBSD| grep BOBCAT
    @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 13:34:43 PST 2007
[build@k2 Build-Trees]$ strings
R2.2.2.5/R2.2.2.5-043007/nfx-tree/Build/bc/opt/Release/bsd | grep
OpenBSD| grep BOBCAT
    @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 13:34:43 PST 2007
[build@k2 Build-Trees]$ strings
R2.22.6/R2.2.2.6-051407/nfx-tree/Build/bc/opt/Release/bsd | grep
OpenBSD| grep BOBCAT
    @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 13:34:43 PST 2007



This is not a matter of using the wrong BSD to package the patch. It's a
case of someone corrupting the posted BSD images, probably by doing a p4
sync when /usr/openbsd.new was pointed to the 2.2.x BSD when they
thought it was pointed to DeLorean.



In the Notes section of CQ 19207 Danqing does a compare of the two files
/etc/rc and /etc/mdrive_fstab and found they had parts of recent
DeLorean changes grafted into them. These same pieces are in the posted
BSD build for 2.2.x:



/n/Build-Trees/BSD/openbsd-latest-22



I believe all we have to do to fix this is copy the correct 2.2.x /etc
files into the posted 2.2.x BSD build and rebuild the patch tarfiles.
Ed, you'd said spin 2.2.2.5 as 2.2.2.7, but isn't what we want to do is
respin 2.2.2.6 as 2.2.2.7 with the corrected /etc files so they stay
cumulative?



Please confirm, then I'll go ahead and do this.



Thanks,



-Ken



________________________________

From: Ed Kwan
Sent: Wed 5/16/2007 11:05 AM
To: Huy Duong; David Crispin; Victor Carrell (Glasshouse); dl-cstech
Cc: Ken Renshaw; Danqing Jin; Erik Palomba
Subject: RE: 2.2.2.5 w/n boot

TED 19207.  Need to re-spin 2.2.2.5 (as 2.2.2.7) with the correct BSD.

> -----Original Message-----
> From: Huy Duong
> Sent: Wednesday, May 16, 2007 9:01 AM
> To: David Crispin; Victor Carrell (Glasshouse); dl-cstech
> Subject: Re: 2.2.2.5 w/n boot
>
> Victor file a bug. This is very serious I will escalate it.
> -----------------------------------------
> Huy Duong
> ONStor Strategic Support Account Manager
> Phone 408.963.2478
> Cell    408.431.6803
> http://support.onstor.com/
> Sent From My Blackberry
>
>
> -----Original Message-----
> From: David Crispin
> To: Victor Carrell (Glasshouse); dl-cstech
> Sent: Wed May 16 08:48:45 2007
> Subject: Re: 2.2.2.5  w/n boot
>
> I had the same thing yesterday. System upgrade, compare then reboot -s
and
> it never came back. This was in a remote data centre. A real pain.
It's
> still down.
>
> Regards,
> David Crispin
> Technical Services Manager
> ONStor Ltd.
> 07940 547895
>
> Sent from my Blackberry
>
> -----Original Message-----
> From: Victor Carrell (Glasshouse)
> To: dl-cstech
> Sent: Wed May 16 07:41:42 2007
> Subject: 2.2.2.5  w/n boot
>
> Hi All,
>
>
>
>             Can some one tell me the super secret step needed to boot
a
> 22xx 2.2.2.5 after an upgrade?
>
>
>
> We tried upgrading LA Health yesterday 2 systems 1 system twice.
> Everything runs clean compare, md5 and version -s ok but will not boot
>
>
>
> I tried the same upgrade from a local ftp server to our systems
in-house
> w/same results.
>
>
>
> Thanks
>
> Victor


------_=_NextPart_001_01C798BA.288014D0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Re: 2.2.2.5 w/n boot</title>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>All,<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; We now understand what caused =
the
issues found in the field with the 2.2.2.5 and 1.3.3.16 =
patches.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'>The problem was caused by an <strong><b><font face=3D"Times New =
Roman"><span
style=3D'font-weight:normal'>inadvertent Perforce sync or file copy to =
the wrong
location in our build storage area =
/n/Build-Trees/BSD</span></font></b></strong><b><span
style=3D'font-weight:bold'>. <o:p></o:p></span></b></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'>This caused<b><span =
style=3D'font-weight:bold'>&nbsp;</span></b><strong><b><font
face=3D"Times New Roman"><span =
style=3D'font-weight:normal'>two</span></font></b></strong>
of our objects to become corrupted. That object was then included in =
these
patches.<br>
<br>
The problem was not caught during testing due to a deviation from the =
approved
test work flow.<br>
<br>
To fix this we are doing the following:<br>
<br>
First: Awareness, folks need to verify where they are syncing to in =
order to
avoid&nbsp;corrupting the depot.<br>
<br>
Second: Testing will correct the deviation in testing and only follow =
the
supported/documented workflow and test procedure.<br>
<br>
Third: Build will wall off a golden version of the objects so that they =
cannot
be written to inadvertently. <strong><b><font face=3D"Times New =
Roman"><span
style=3D'font-weight:normal'>Build will also create delta BOMs for every =
patch so
we can audit which files changed and approve the list prior to =
release.</span></font></b></strong><b><span
style=3D'font-weight:bold'><br>
</span></b><br>
Please let me know if you have any questions on this matter.<br>
<br>
-Paul</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Victor Carrell
(Glasshouse) <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, May 17, =
2007 10:38
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Frontline Support; =
Ken Renshaw;
Huy Duong; Rex Yuan; Erik Palomba; Raghu Murthy; Danqing Jin; David =
Crispin;
dl-cstech<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: 2.2.2.5 w/n =
boot</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Let me ask another way.&nbsp; Will =
2.2.2.7
have the cifsd fix included with the ECC fix?&nbsp; If not =
why?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>If so why would one go to 2.2.2.6 =
verses
2.2.2.7? Or why would 2.2.2.6 even be distributed if both fixes are in =
2.2.2.7?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>From Ken&#8217;s statement all =
three will be
ready today.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I&#8217;m just trying to understand =
the
logic to best serve our customers.&nbsp; I have already been asked by =
Nissho
which version to upgrade to.&nbsp; Do I tell them to wait a few days =
or&nbsp;
tell them to go to 2.2.2.4 knowing there are 2 important fixes coming in =
a few
days then upgrade again when they crash?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Victor<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
support@cc.onstor.com [mailto:support@cc.onstor.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, May 17, =
2007 1:16
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Frontline Support; =
Ken
Renshaw; Huy Duong; Rex Yuan; Erik Palomba; Raghu Murthy; Danqing Jin; =
David
Crispin; dl-cstech<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: 2.2.2.5 w/n =
boot</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>When and why your customer want to
upgrade?&nbsp; 2.2.2.6 fixes a cifsd issue.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Patch 2.2.2.7 is for ECC =
errors.&nbsp; It
will take at least a few more days of testing by the hardware =
folks.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
<st1:PersonName
w:st=3D"on">Frontline Support</st1:PersonName> <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, May 17, =
2007 9:59
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Ken Renshaw; Huy =
Duong; Rex
Yuan; Erik Palomba; <st1:PersonName w:st=3D"on">Raghu =
Murthy</st1:PersonName>; <st1:PersonName
w:st=3D"on">Danqing Jin</st1:PersonName>; Ed Kwan; <st1:PersonName =
w:st=3D"on">David
 Crispin</st1:PersonName>; dl-cstech<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName =
w:st=3D"on">Frontline
 Support</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: 2.2.2.5 w/n =
boot</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>If a customer asks which to load =
2.2.2.6
or 2.2.2.7 what would be the answer?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Victor<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Ken =
Renshaw
[mailto:ken.renshaw@onstor.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, May 17, =
2007 12:46
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Huy Duong; Rex Yuan; =
Erik
Palomba; <st1:PersonName w:st=3D"on">Raghu Murthy</st1:PersonName>; =
<st1:PersonName
w:st=3D"on">Danqing Jin</st1:PersonName>; Ed Kwan; <st1:PersonName =
w:st=3D"on">David
 Crispin</st1:PersonName>; <st1:PersonName w:st=3D"on">Victor =
Carrell</st1:PersonName>
(Glasshouse); dl-cstech<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName =
w:st=3D"on">Frontline
 Support</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: 2.2.2.5 w/n =
boot</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p style=3D'margin-bottom:12.0pt'><font size=3D2 face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt'>2.2.2.5 is being rebuilt as 2.2.2.6 right =
now. I'll
fix 1.3.3.16 next, then the ECC patch which hadn't shipped yet as =
2.2.2.7.<br>
<br>
All three should be ready today.<br>
<br>
Thanks,<br>
<br>
-Ken<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: Huy Duong<br>
To: Rex Yuan; Erik Palomba; <st1:PersonName w:st=3D"on">Raghu =
Murthy</st1:PersonName>;
Ken Renshaw; <st1:PersonName w:st=3D"on">Danqing Jin</st1:PersonName>; =
Ed Kwan; <st1:PersonName
w:st=3D"on">David Crispin</st1:PersonName>; <st1:PersonName =
w:st=3D"on">Victor
 Carrell</st1:PersonName> (Glasshouse); dl-cstech<br>
CC: <st1:PersonName w:st=3D"on">Frontline Support</st1:PersonName><br>
Sent: Thu May 17 09:42:48 2007<br>
Subject: RE: 2.2.2.5&nbsp; w/n boot<br>
<br>
Did we determine how we are&nbsp; re-spinning these patches?<br>
<br>
-----Original Message-----<br>
From: Rex Yuan<br>
Sent: Thursday, May 17, 2007 9:04 AM<br>
To: Erik Palomba; <st1:PersonName w:st=3D"on">Raghu =
Murthy</st1:PersonName>; Ken
Renshaw; <st1:PersonName w:st=3D"on">Danqing Jin</st1:PersonName>; Ed =
Kwan; Huy
Duong; <st1:PersonName w:st=3D"on">David Crispin</st1:PersonName>; =
<st1:PersonName
w:st=3D"on">Victor Carrell</st1:PersonName> (Glasshouse); dl-cstech<br>
Cc: <st1:PersonName w:st=3D"on">Frontline Support</st1:PersonName><br>
Subject: RE: 2.2.2.5 w/n boot<br>
<br>
1.3.3.16 has been pulled.<br>
<br>
-----Original Message-----<br>
From: Erik Palomba<br>
Sent: Thursday, May 17, 2007 8:57 AM<br>
To: <st1:PersonName w:st=3D"on">Raghu Murthy</st1:PersonName>; Ken =
Renshaw; <st1:PersonName
w:st=3D"on">Danqing Jin</st1:PersonName>; Ed Kwan; Huy Duong; =
<st1:PersonName
w:st=3D"on">David Crispin</st1:PersonName>; <st1:PersonName =
w:st=3D"on">Victor
 Carrell</st1:PersonName> (Glasshouse); dl-cstech<br>
Subject: RE: 2.2.2.5 w/n boot<br>
<br>
I just confirmed that 1.3.3.16 has the same problem as 2.2.2.5. Please =
pull the
patch.<br>
<br>
-----Original Message-----<br>
From: <st1:PersonName w:st=3D"on">Raghu Murthy</st1:PersonName><br>
Sent: Thursday, May 17, 2007 8:43 AM<br>
To: Ken Renshaw; <st1:PersonName w:st=3D"on">Danqing =
Jin</st1:PersonName>; Ed
Kwan; Huy Duong; <st1:PersonName w:st=3D"on">David =
Crispin</st1:PersonName>; <st1:PersonName
w:st=3D"on">Victor Carrell</st1:PersonName> (Glasshouse); dl-cstech<br>
Cc: Erik Palomba<br>
Subject: RE: 2.2.2.5 w/n boot<br>
<br>
Ken,<br>
<br>
So do we have exposure on 1.3.3.16 as well?<br>
Raghu<br>
&nbsp;------------------<br>
From: <st1:PersonName w:st=3D"on">Alan Cooke</st1:PersonName> =
(Glasshouse)<br>
Sent: Thursday, May 17, 2007 5:37 AM<br>
To: <st1:PersonName w:st=3D"on">Alan Cooke</st1:PersonName> =
(Glasshouse);
dl-Customer-Engineering; <st1:PersonName w:st=3D"on">Frontline =
Support</st1:PersonName>;
dl-cstech<br>
Subject: RE: Failure to boot OS may be in 1.3.3.16 too<br>
<br>
Hi All,<br>
<br>
Just confirmed this failure with trying to upgrade a Cheetah system in =
the
Glasshouse lab going from 1.3.3.14 to 1.3.3.16 We had to swap the CF =
cards to
get the system back.<br>
This is a fairly conclusive failure so I would request this release is =
removed
from the FTP site ASAP please.<br>
<br>
Thanks &#8230; Alan.<br>
<br>
-----Original Message-----<br>
From: Ken Renshaw<br>
Sent: Wednesday, May 16, 2007 6:06 PM<br>
To: <st1:PersonName w:st=3D"on">Danqing Jin</st1:PersonName>; =
<st1:PersonName
w:st=3D"on">Raghu Murthy</st1:PersonName>; Ed Kwan; Huy Duong; =
<st1:PersonName
w:st=3D"on">David Crispin</st1:PersonName>; <st1:PersonName =
w:st=3D"on">Victor
 Carrell</st1:PersonName> (Glasshouse); dl-cstech<br>
Cc: Erik Palomba<br>
Subject: Re: 2.2.2.5 w/n boot<br>
<br>
Versions thru 2.2.2.4 do not have this issues.<br>
<br>
-Ken<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: <st1:PersonName w:st=3D"on">Danqing Jin</st1:PersonName><br>
To: <st1:PersonName w:st=3D"on">Raghu Murthy</st1:PersonName>; Ken =
Renshaw; Ed
Kwan; Huy Duong; <st1:PersonName w:st=3D"on">David =
Crispin</st1:PersonName>; <st1:PersonName
w:st=3D"on">Victor Carrell</st1:PersonName> (Glasshouse); dl-cstech<br>
CC: Erik Palomba<br>
Sent: Wed May 16 17:35:47 2007<br>
Subject: RE: 2.2.2.5&nbsp; w/n boot<br>
<br>
They are safe, as this issue occurs only in 2.2.2.5.<br>
<br>
________________________________<br>
<br>
From: <st1:PersonName w:st=3D"on">Raghu Murthy</st1:PersonName><br>
Sent: Wednesday, May 16, 2007 5:35 PM<br>
To: Ken Renshaw; Ed Kwan; Huy Duong; <st1:PersonName w:st=3D"on">David =
Crispin</st1:PersonName>;
<st1:PersonName w:st=3D"on">Victor Carrell</st1:PersonName> =
(Glasshouse);
dl-cstech<br>
Cc: <st1:PersonName w:st=3D"on">Danqing Jin</st1:PersonName>; Erik =
Palomba<br>
Subject: RE: 2.2.2.5 w/n boot<br>
<br>
<br>
<br>
I know we have yanked 2.2.2.5 from the FTP site. Since 2.2.2.5 was =
failing the
upgrade process while the others 2.2.2.3 and 2.2.2.4 did not, any idea =
what is
the exposure for the sites that successfully upgraded to 2.2.2.3 and =
2.2.2.4
but still have the incorrect /etc files?<br>
<br>
<br>
<br>
Raghu<br>
<br>
<br>
<br>
________________________________<br>
<br>
From: Ken Renshaw<br>
Sent: Wednesday, May 16, 2007 11:44 AM<br>
To: Ken Renshaw; Ed Kwan; Huy Duong; <st1:PersonName w:st=3D"on">David =
Crispin</st1:PersonName>;
<st1:PersonName w:st=3D"on">Victor Carrell</st1:PersonName> =
(Glasshouse);
dl-cstech<br>
Cc: <st1:PersonName w:st=3D"on">Danqing Jin</st1:PersonName>; Erik =
Palomba<br>
Subject: RE: 2.2.2.5 w/n boot<br>
<br>
<br>
<br>
From now on I will add a step in the build process for patches to do a =
quick
file delta from the previous patch and include that in the build info.
Hopefully that will help us flag these kinds of things before they leave =
the
building.<br>
<br>
<br>
<br>
Thanks,<br>
<br>
<br>
<br>
-Ken<br>
<br>
<br>
<br>
________________________________<br>
<br>
From: Ken Renshaw<br>
Sent: Wed 5/16/2007 11:37 AM<br>
To: Ed Kwan; Huy Duong; <st1:PersonName w:st=3D"on">David =
Crispin</st1:PersonName>;
<st1:PersonName w:st=3D"on">Victor Carrell</st1:PersonName> =
(Glasshouse);
dl-cstech<br>
Cc: <st1:PersonName w:st=3D"on">Danqing Jin</st1:PersonName>; Erik =
Palomba; Ken
Renshaw<br>
Subject: RE: 2.2.2.5 w/n boot<br>
<br>
Hello.<br>
<br>
<br>
<br>
The last four patches have all been done with the same build of bsd:<br>
<br>
<br>
<br>
[build@k2 Build-Trees]$ strings
R2.2.2.3/R2.2.2.3-041807/nfx-tree/Build/bc/opt/Release/bsd | grep =
OpenBSD| grep
BOBCAT<br>
&nbsp;&nbsp;&nbsp; @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 13:34:43 PST =
2007<br>
[build@k2 Build-Trees]$ strings
R2.2.2.4/R2.2.2.4-042507/nfx-tree/Build/bc/opt/Release/bsd | grep =
OpenBSD| grep
BOBCAT<br>
&nbsp;&nbsp;&nbsp; @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 13:34:43 PST =
2007<br>
[build@k2 Build-Trees]$ strings =
R2.2.2.5/R2.2.2.5-043007/nfx-tree/Build/bc/opt/Release/bsd
| grep OpenBSD| grep BOBCAT<br>
&nbsp;&nbsp;&nbsp; @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 13:34:43 PST =
2007<br>
[build@k2 Build-Trees]$ strings
R2.22.6/R2.2.2.6-051407/nfx-tree/Build/bc/opt/Release/bsd | grep =
OpenBSD| grep
BOBCAT<br>
&nbsp;&nbsp;&nbsp; @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 13:34:43 PST =
2007<br>
<br>
<br>
<br>
This is not a matter of using the wrong BSD to package the patch. It's a =
case
of someone corrupting the posted BSD images, probably by doing a p4 sync =
when
/usr/openbsd.new was pointed to the 2.2.x BSD when they thought it was =
pointed
to DeLorean.<br>
<br>
<br>
<br>
In the Notes section of CQ 19207 Danqing does a compare of the two files
/etc/rc and /etc/mdrive_fstab and found they had parts of recent =
DeLorean
changes grafted into them. These same pieces are in the posted BSD build =
for
2.2.x:<br>
<br>
<br>
<br>
/n/Build-Trees/BSD/openbsd-latest-22<br>
<br>
<br>
<br>
I believe all we have to do to fix this is copy the correct 2.2.x /etc =
files
into the posted 2.2.x BSD build and rebuild the patch tarfiles. Ed, =
you'd said
spin 2.2.2.5 as 2.2.2.7, but isn't what we want to do is respin 2.2.2.6 =
as
2.2.2.7 with the corrected /etc files so they stay cumulative?<br>
<br>
<br>
<br>
Please confirm, then I'll go ahead and do this.<br>
<br>
<br>
<br>
Thanks,<br>
<br>
<br>
<br>
-Ken<br>
<br>
<br>
<br>
________________________________<br>
<br>
From: Ed Kwan<br>
Sent: Wed 5/16/2007 11:05 AM<br>
To: Huy Duong; <st1:PersonName w:st=3D"on">David =
Crispin</st1:PersonName>; <st1:PersonName
w:st=3D"on">Victor Carrell</st1:PersonName> (Glasshouse); dl-cstech<br>
Cc: Ken Renshaw; <st1:PersonName w:st=3D"on">Danqing =
Jin</st1:PersonName>; Erik
Palomba<br>
Subject: RE: 2.2.2.5 w/n boot<br>
<br>
TED 19207.&nbsp; Need to re-spin 2.2.2.5 (as 2.2.2.7) with the correct =
BSD.<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Huy Duong<br>
&gt; Sent: Wednesday, May 16, 2007 9:01 AM<br>
&gt; To: <st1:PersonName w:st=3D"on">David Crispin</st1:PersonName>; =
<st1:PersonName
w:st=3D"on">Victor Carrell</st1:PersonName> (Glasshouse); dl-cstech<br>
&gt; Subject: Re: 2.2.2.5 w/n boot<br>
&gt;<br>
&gt; Victor file a bug. This is very serious I will escalate it.<br>
&gt; -----------------------------------------<br>
&gt; Huy Duong<br>
&gt; ONStor Strategic Support Account Manager<br>
&gt; Phone 408.963.2478<br>
&gt; Cell&nbsp;&nbsp;&nbsp; 408.431.6803<br>
&gt; <a =
href=3D"http://support.onstor.com/">http://support.onstor.com/</a><br>
&gt; Sent From My Blackberry<br>
&gt;<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: <st1:PersonName w:st=3D"on">David =
Crispin</st1:PersonName><br>
&gt; To: <st1:PersonName w:st=3D"on">Victor Carrell</st1:PersonName>
(Glasshouse); dl-cstech<br>
&gt; Sent: Wed May 16 08:48:45 2007<br>
&gt; Subject: Re: 2.2.2.5&nbsp; w/n boot<br>
&gt;<br>
&gt; I had the same thing yesterday. System upgrade, compare then reboot =
-s and<br>
&gt; it never came back. This was in a remote data centre. A real pain. =
It's<br>
&gt; still down.<br>
&gt;<br>
&gt; Regards,<br>
&gt; <st1:PersonName w:st=3D"on">David Crispin</st1:PersonName><br>
&gt; Technical Services Manager<br>
&gt; ONStor Ltd.<br>
&gt; 07940 547895<br>
&gt;<br>
&gt; Sent from my Blackberry<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: <st1:PersonName w:st=3D"on">Victor Carrell</st1:PersonName>
(Glasshouse)<br>
&gt; To: dl-cstech<br>
&gt; Sent: Wed May 16 07:41:42 2007<br>
&gt; Subject: 2.2.2.5&nbsp; w/n boot<br>
&gt;<br>
&gt; Hi All,<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
Can some one tell me the super secret step needed to boot a<br>
&gt; 22xx 2.2.2.5 after an upgrade?<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; We tried upgrading LA Health yesterday 2 systems 1 system =
twice.<br>
&gt; Everything runs clean compare, md5 and version &#8211;s ok but will =
not
boot<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; I tried the same upgrade from a local ftp server to our systems =
in-house<br>
&gt; w/same results.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Thanks<br>
&gt;<br>
&gt; Victor</span></font><o:p></o:p></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C798BA.288014D0--
