X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7981B.4FF1FD00@onstor-exch02.onstor.net>; Wed, 16 May 2007 17:35:47 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7981B.4FF1FD00"
Content-class: urn:content-classes:message
Subject: RE: 2.2.2.5  w/n boot
Date: Wed, 16 May 2007 17:35:47 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E03AEAC44@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E03C0BDF6@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: 2.2.2.5  w/n boot
Thread-Index: AceXyFGHaAMHX0y7RvaIs+G3KRP0owACV5LTAABqyEMABDU18AAAQurMAAE3k8QADAj6IAAAQCkQ
From: "Danqing Jin" <danqing.jin@onstor.com>
To: "Raghu Murthy" <raghu.murthy@onstor.com>,
	"Ken Renshaw" <ken.renshaw@onstor.com>,
	"Ed Kwan" <ed.kwan@onstor.com>,
	"Huy Duong" <huy.duong@onstor.com>,
	"David Crispin" <david.crispin@onstor.com>,
	"Victor Carrell (Glasshouse)" <vcarrell@css.glasshouse.com>,
	"dl-cstech" <dl-cstech@onstor.com>
Cc: "Erik Palomba" <erik.palomba@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7981B.4FF1FD00
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

________________________________

From: Raghu Murthy=20
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?

=20

Raghu=20

=20

________________________________

From: Ken Renshaw=20
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

=20

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.

=20

Thanks,

=20

-Ken

=20

________________________________

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.

=20

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

=20

[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.2.2.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

=20

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.=20

=20

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:

=20

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

=20

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?

=20

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

=20

Thanks,

=20

-Ken

=20

________________________________

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_01C7981B.4FF1FD00
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD><TITLE>RE: 2.2.2.5 =
w/n boot</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.3790.2706" name=3DGENERATOR><!--[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]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	FONT-WEIGHT: normal; COLOR: black; FONT-STYLE: normal; FONT-FAMILY: =
Arial; TEXT-DECORATION: none; mso-style-type: personal-reply
}
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 vLink=3Dblue link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D971173500-17052007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>They are safe, as this issue occurs only in=20
2.2.2.5.</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Raghu Murthy <BR><B>Sent:</B> =
Wednesday,=20
May 16, 2007 5:35 PM<BR><B>To:</B> Ken Renshaw; Ed Kwan; Huy Duong; =
David=20
Crispin; Victor Carrell (Glasshouse); dl-cstech<BR><B>Cc:</B> Danqing =
Jin; Erik=20
Palomba<BR><B>Subject:</B> RE: 2.2.2.5 w/n boot<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I know we =
have yanked=20
2.2.2.5 from the FTP site. Since 2.2.2.5 was failing the upgrade process =
while=20
the others 2.2.2.3 and 2.2.2.4 did not, any idea what is the exposure =
for the=20
sites that successfully upgraded to 2.2.2.3 and 2.2.2.4 but still have =
the=20
incorrect /etc files?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Raghu=20
</SPAN></FONT><FONT color=3Dblack><SPAN=20
style=3D"COLOR: black"><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack =
size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: =
black">&nbsp;</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =

face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
<st1:PersonName w:st=3D"on">Ken Renshaw</st1:PersonName> <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, May 16, 2007 =
11:44=20
AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
<st1:PersonName=20
w:st=3D"on">Ken Renshaw</st1:PersonName>; <st1:PersonName w:st=3D"on">Ed =

Kwan</st1:PersonName>; Huy Duong; <st1:PersonName w:st=3D"on">David=20
Crispin</st1:PersonName>; <st1:PersonName w:st=3D"on">Victor=20
Carrell</st1:PersonName> (Glasshouse); dl-cstech<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> <st1:PersonName =
w:st=3D"on">Danqing=20
Jin</st1:PersonName>; Erik Palomba<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: 2.2.2.5 w/n=20
boot</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV id=3DidOWAReplyText67500>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">From now on =
I will add=20
a step in the build process for patches to do a quick file delta from =
the=20
previous patch and include that in the build info. Hopefully that will =
help us=20
flag these kinds of things before they leave the=20
building.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks,</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-Ken</SPAN></FONT><o:p></o:p></P></DIV></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =

face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
<st1:PersonName w:st=3D"on">Ken Renshaw</st1:PersonName><BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wed 5/16/2007 11:37 =
AM<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></B> <st1:PersonName =
w:st=3D"on">Ed=20
Kwan</st1:PersonName>; Huy Duong; <st1:PersonName w:st=3D"on">David=20
Crispin</st1:PersonName>; <st1:PersonName w:st=3D"on">Victor=20
Carrell</st1:PersonName> (Glasshouse); dl-cstech<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> <st1:PersonName =
w:st=3D"on">Danqing=20
Jin</st1:PersonName>; Erik Palomba; <st1:PersonName w:st=3D"on">Ken=20
Renshaw</st1:PersonName><BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: 2.2.2.5 w/n=20
boot</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<DIV id=3DidOWAReplyText30617>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Hello.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The last four patches have =
all been=20
done with the same build of bsd:</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">[build@k2 Build-Trees]$ =
strings=20
R2.2.2.3/R2.2.2.3-041807/nfx-tree/Build/bc/opt/Release/bsd | grep =
OpenBSD| grep=20
BOBCAT<BR>&nbsp;&nbsp;&nbsp; @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 =
13:34:43=20
PST 2007<BR>[build@k2 Build-Trees]$ strings=20
R2.2.2.4/R2.2.2.4-042507/nfx-tree/Build/bc/opt/Release/bsd | grep =
OpenBSD| grep=20
BOBCAT<BR>&nbsp;&nbsp;&nbsp; @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 =
13:34:43=20
PST 2007<BR>[build@k2 Build-Trees]$ strings=20
R2.2.2.5/R2.2.2.5-043007/nfx-tree/Build/bc/opt/Release/bsd | grep =
OpenBSD| grep=20
BOBCAT<BR>&nbsp;&nbsp;&nbsp; @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 =
13:34:43=20
PST 2007<BR>[build@k2 Build-Trees]$ strings=20
R2.2.2.6/R2.2.2.6-051407/nfx-tree/Build/bc/opt/Release/bsd | grep =
OpenBSD| grep=20
BOBCAT<BR>&nbsp;&nbsp;&nbsp; @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan 18 =
13:34:43=20
PST 2007</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">This is not a matter of =
using the=20
wrong BSD to package the patch. It's a case of someone corrupting the =
posted BSD=20
images, probably by doing a p4 sync when /usr/openbsd.new was pointed to =
the=20
2.2.x BSD when they thought it was pointed to DeLorean.=20
<o:p></o:p></SPAN></FONT></P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">In the Notes section of CQ =
19207=20
Danqing does a compare of the two files /etc/rc and /etc/mdrive_fstab =
and found=20
they had parts of recent DeLorean changes grafted into them. These same =
pieces=20
are in the posted BSD build for =
2.2.x:</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">/n/Build-Trees/BSD/openbsd-latest-22</SPAN></FONT><o:p></o:p></P><=
/DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I believe all we have to =
do to fix=20
this is copy the correct 2.2.x /etc files into the posted 2.2.x BSD =
build and=20
rebuild the patch tarfiles. Ed, you'd said spin 2.2.2.5 as 2.2.2.7, but =
isn't=20
what we want to do is respin 2.2.2.6 as 2.2.2.7 with the corrected /etc =
files so=20
they stay cumulative?</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Please confirm, then I'll =
go ahead=20
and do this.</SPAN></FONT><FONT face=3DArial><SPAN=20
style=3D"FONT-FAMILY: Arial"><o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks,</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-Ken<o:p></o:p></SPAN></FONT></P></DIV></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =

face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
<st1:PersonName w:st=3D"on">Ed Kwan</st1:PersonName><BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wed 5/16/2007 11:05 =
AM<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Huy Duong; <st1:PersonName=20
w:st=3D"on">David Crispin</st1:PersonName>; <st1:PersonName =
w:st=3D"on">Victor=20
Carrell</st1:PersonName> (Glasshouse); dl-cstech<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> <st1:PersonName =
w:st=3D"on">Ken=20
Renshaw</st1:PersonName>; <st1:PersonName w:st=3D"on">Danqing=20
Jin</st1:PersonName>; Erik Palomba<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: 2.2.2.5 w/n=20
boot</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P style=3D"MARGIN-BOTTOM: 12pt"><FONT face=3D"Times New Roman" =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">TED 19207.&nbsp; Need to re-spin 2.2.2.5 (as =
2.2.2.7)=20
with the correct BSD.<BR><BR>&gt; -----Original Message-----<BR>&gt; =
From: Huy=20
Duong<BR>&gt; Sent: Wednesday, May 16, 2007 9:01 AM<BR>&gt; To: =
<st1:PersonName=20
w:st=3D"on">David Crispin</st1:PersonName>; <st1:PersonName =
w:st=3D"on">Victor=20
Carrell</st1:PersonName> (Glasshouse); dl-cstech<BR>&gt; Subject: Re: =
2.2.2.5=20
w/n boot<BR>&gt;<BR>&gt; Victor file a bug. This is very serious I will =
escalate=20
it.<BR>&gt; -----------------------------------------<BR>&gt; Huy =
Duong<BR>&gt;=20
ONStor Strategic Support Account Manager<BR>&gt; Phone =
408.963.2478<BR>&gt;=20
Cell&nbsp;&nbsp;&nbsp; 408.431.6803<BR>&gt; <A=20
href=3D"http://support.onstor.com/">http://support.onstor.com/</A><BR>&gt=
; Sent=20
From My Blackberry<BR>&gt;<BR>&gt;<BR>&gt; -----Original =
Message-----<BR>&gt;=20
From: <st1:PersonName w:st=3D"on">David Crispin</st1:PersonName><BR>&gt; =
To:=20
<st1:PersonName w:st=3D"on">Victor Carrell</st1:PersonName> =
(Glasshouse);=20
dl-cstech<BR>&gt; Sent: Wed May 16 08:48:45 2007<BR>&gt; Subject: Re:=20
2.2.2.5&nbsp; w/n boot<BR>&gt;<BR>&gt; I had the same thing yesterday. =
System=20
upgrade, compare then reboot -s and<BR>&gt; it never came back. This was =
in a=20
remote data centre. A real pain. It's<BR>&gt; still =
down.<BR>&gt;<BR>&gt;=20
Regards,<BR>&gt; <st1:PersonName w:st=3D"on">David=20
Crispin</st1:PersonName><BR>&gt; Technical Services Manager<BR>&gt; =
ONStor=20
Ltd.<BR>&gt; 07940 547895<BR>&gt;<BR>&gt; Sent from my=20
Blackberry<BR>&gt;<BR>&gt; -----Original Message-----<BR>&gt; From:=20
<st1:PersonName w:st=3D"on">Victor Carrell</st1:PersonName> =
(Glasshouse)<BR>&gt;=20
To: dl-cstech<BR>&gt; Sent: Wed May 16 07:41:42 2007<BR>&gt; Subject:=20
2.2.2.5&nbsp; w/n boot<BR>&gt;<BR>&gt; Hi=20
All,<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Can some one tell me the super secret step needed to boot a<BR>&gt; 22xx =
2.2.2.5=20
after an upgrade?<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; We tried upgrading LA =
Health=20
yesterday 2 systems 1 system twice.<BR>&gt; Everything runs clean =
compare, md5=20
and version &#8211;s ok but will not =
boot<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; I tried the=20
same upgrade from a local ftp server to our systems in-house<BR>&gt; =
w/same=20
results.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; Thanks<BR>&gt;<BR>&gt;=20
Victor</SPAN></FONT><o:p></o:p></P></DIV></DIV></DIV></BODY></HTML>

------_=_NextPart_001_01C7981B.4FF1FD00--
