X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C797ED.2A8D080E@onstor-exch02.onstor.net>; Wed, 16 May 2007 12:05:28 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C797ED.2A8D080E"
References: <BB375AF679D4A34E9CA8DFA650E2B04E01440474@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E023B3CF0@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E02F3D0B7@onstor-exch02.onstor.net>
Content-class: urn:content-classes:message
Subject: FW: 2.2.2.5  w/n boot
Date: Wed, 16 May 2007 12:04:23 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D0B9@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: 2.2.2.5  w/n boot
Thread-Index: AceXyFGHaAMHX0y7RvaIs+G3KRP0owACV5LTAABqyEMABDU18AAAQurMAAFhHaUAAE/t6QAAISk8AAAgAkk=
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Larry Scheer" <larry.scheer@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C797ED.2A8D080E
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

FYI, Jerry wants it to never happen again, so that's one piece of your =
inner child restored Andy.
=20
-Ken

________________________________

From: Ken Renshaw
Sent: Wed 5/16/2007 12:00 PM
To: Paul Hammer
Subject: RE: 2.2.2.5 w/n boot


Definitely. It will take building a new BSD for each and every build and =
keeping them in a lockbox where none but build can access them. The two =
loads that go up are time; adding 2-3 hours to each and every patch =
build no matter how small, and storage; adding 2-3Gb for every patch =
build, again no matter how small.
=20
This won't keep the developers from stomping on the public copies I =
provide, but at least it will keep our releases clean.
=20
If this works for you and Ed ( I'll inform him patch build time has now =
doubled ) then I'll start this with the 2.2.2.5/2.2.2.6/2.2.3.0 patch =
train rolling through right now.
=20
Thanks,
=20
-Ken

________________________________

From: Paul Hammer
Sent: Wed 5/16/2007 11:57 AM
To: Ken Renshaw
Subject: FW: 2.2.2.5 w/n boot


FYI: Is this possible.

________________________________

From: Jerry Lopatin
Sent: Wed 5/16/2007 11:48 AM
To: Jay Michlin; Paul Hammer
Subject: Fw: 2.2.2.5 w/n boot



Jay, Paul,

Please fix this so that it can never happen again

--------------------------
Sent from my Blackberry; please excuse my typing!

-----Original Message-----
From: Ken Renshaw
To: Ed Kwan; Huy Duong; David Crispin; Victor Carrell (Glasshouse); =
dl-cstech
CC: Danqing Jin; Erik Palomba; Ken Renshaw
Sent: Wed May 16 11:37:43 2007
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.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

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_01C797ED.2A8D080E
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Fw: 2.2.2.5 w/n boot</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.2853" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText49013 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>FYI, Jerry =
wants it to never happen again, so that's one piece of your inner child =
restored Andy.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>-Ken</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Ken Renshaw<BR><B>Sent:</B> =
Wed 5/16/2007 12:00 PM<BR><B>To:</B> Paul Hammer<BR><B>Subject:</B> RE: =
2.2.2.5 w/n boot<BR></FONT><BR></DIV>=0A=
<DIV dir=3Dltr>=0A=
<DIV id=3DidOWAReplyText59524 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Definitely. =
It will take building a new BSD for each and every build and keeping =
them in a lockbox where none but build can access them. The two loads =
that go up are time; adding 2-3 hours to each and every patch build no =
matter how small, and storage; adding 2-3Gb for every patch build, again =
no matter how small.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>This won't keep the =
developers from stomping on the public copies I provide, but at least it =
will keep our releases clean.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>If this works for you and Ed =
( I'll inform him patch build time has now doubled ) then I'll start =
this with the 2.2.2.5/2.2.2.6/2.2.3.0 patch train rolling through right =
now.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>-Ken</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Paul Hammer<BR><B>Sent:</B> =
Wed 5/16/2007 11:57 AM<BR><B>To:</B> Ken Renshaw<BR><B>Subject:</B> FW: =
2.2.2.5 w/n boot<BR></FONT><BR></DIV>=0A=
<DIV dir=3Dltr>=0A=
<DIV id=3DidOWAReplyText95013 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>FYI: Is this =
possible.</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Jerry Lopatin<BR><B>Sent:</B> =
Wed 5/16/2007 11:48 AM<BR><B>To:</B> Jay Michlin; Paul =
Hammer<BR><B>Subject:</B> Fw: 2.2.2.5 w/n boot<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Jay, Paul,<BR><BR>Please fix this so that it can never =
happen again<BR><BR>--------------------------<BR>Sent from my =
Blackberry; please excuse my typing!<BR><BR>-----Original =
Message-----<BR>From: Ken Renshaw<BR>To: Ed Kwan; Huy Duong; David =
Crispin; Victor Carrell (Glasshouse); dl-cstech<BR>CC: Danqing Jin; Erik =
Palomba; Ken Renshaw<BR>Sent: Wed May 16 11:37:43 2007<BR>Subject: RE: =
2.2.2.5&nbsp; w/n boot<BR><BR>Hello.<BR><BR>The last four patches have =
all been done with the same build of bsd:<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.2.2.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>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>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>/n/Build-Trees/BSD/openbsd-latest-22<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>Please confirm, then I'll go ahead and do =
this.<BR><BR>Thanks,<BR><BR>-Ken<BR><BR>________________________________<=
BR><BR>From: Ed Kwan<BR>Sent: Wed 5/16/2007 11:05 AM<BR>To: Huy Duong; =
David Crispin; Victor Carrell (Glasshouse); dl-cstech<BR>Cc: Ken =
Renshaw; Danqing Jin; Erik Palomba<BR>Subject: RE: 2.2.2.5 w/n =
boot<BR><BR><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: David Crispin; Victor Carrell (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: David Crispin<BR>&gt; To: Victor Carrell =
(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; David Crispin<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: Victor Carrell =
(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;&nbsp; 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<BR><BR><BR><BR></FONT></P></DIV></DIV></DIV></BODY></HTML>
------_=_NextPart_001_01C797ED.2A8D080E--
