X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C797EC.6725536A@onstor-exch02.onstor.net>; Wed, 16 May 2007 12:00:00 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C797EC.6725536A"
References: <BB375AF679D4A34E9CA8DFA650E2B04EEACB42@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E03C0BB39@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E02F3D0B0@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E02F3D0B3@onstor-exch02.onstor.net> <20070516115005.0d9e996a@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: 2.2.2.5  w/n boot
Date: Wed, 16 May 2007 12:00:00 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D0B6@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: 2.2.2.5  w/n boot
Thread-Index: AceX6wSQJl5xjo+jRGWYkAB1NmbxeAAABihF
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C797EC.6725536A
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

My first inclination was to ignore you Andy, but then when I heard of =
your troubled childhood I felt bad, so I undeleted your message.
=20
My only real answer is either impatience, laziness, or time constraints; =
adding the openbsd build triples the build time and there's always =
pressure to get the patch out, get the submittal into test., etc. The =
other reason is that then I'd also have to keep every bloomin' copy I =
ever built, and while disks are cheap, having dozens and dozens of BSD's =
around would probably cause a bigger mess.
=20
So I try and just rebuild for submittals, and otherwise just when =
someone has checked in changes. Unfortunately that doesn't stop people =
from doing what just happened.
=20
However, I had a troubled childhood as well so I can relate, and the =
more of this crap that happens the more I lean towards building =
everytime and telling them it'll take hours longer, and making sure IT =
has autogrow turned on for the /n/Build-Trees partition.
=20
We already rebuild for every submittal, so let me tell Ed that his =
patches will now take longer, but that he can have more confidence in =
them. At this point I'm sure he's up for the tradeoff as well.
=20
Thanks Andy,
=20
-Ken

________________________________

From: Andy Sharp
Sent: Wed 5/16/2007 11:50 AM
To: Ken Renshaw
Cc: Larry Scheer
Subject: Re: 2.2.2.5 w/n boot



Hi Guys,

I'm sure I'm being ignorant again, but I still don't see why we don't
build BSD along with everything else, from scratch, for each and every
release, submittal, nightly build, freckle on my @ss, and so on.  Is
there some reason we don't just move to that model, so we won't ever
have these problems ever again?  My ignorance is a product of a troubled
childhood, so don't be insensitive you guys.  You know how you are.

a


On Wed, 16 May 2007 11:43:31 -0700 "Ken Renshaw"
<ken.renshaw@onstor.com> wrote:

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

<HTML dir=3Dltr><HEAD><TITLE>Re: 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=3DidOWAReplyText87506 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>My first =
inclination was to ignore you Andy, but then when I heard of your =
troubled childhood I felt bad, so I undeleted your message.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>My only real answer is either =
impatience, laziness,&nbsp;or time constraints; adding the openbsd build =
triples the build time and there's always pressure to get the patch out, =
get the submittal into test., etc. The other reason is that then I'd =
also have to keep every bloomin' copy I ever built, and while disks are =
cheap, having dozens and dozens of BSD's around would probably cause a =
bigger mess.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>So I try and just rebuild for =
submittals, and otherwise just when someone has checked in changes. =
Unfortunately that doesn't stop people from doing what just =
happened.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>However, I had a troubled =
childhood as well so I can relate, and the more of this crap that =
happens the more I lean towards building everytime and telling them =
it'll take hours longer, and making sure IT has autogrow turned on for =
the /n/Build-Trees partition.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>We already rebuild for every =
submittal, so let me tell Ed that his patches will now take longer, but =
that he can have more confidence in them. At this point I'm sure he's up =
for the tradeoff as well.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Thanks 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> Andy Sharp<BR><B>Sent:</B> Wed =
5/16/2007 11:50 AM<BR><B>To:</B> Ken Renshaw<BR><B>Cc:</B> Larry =
Scheer<BR><B>Subject:</B> Re: 2.2.2.5 w/n boot<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Hi Guys,<BR><BR>I'm sure I'm being ignorant again, but =
I still don't see why we don't<BR>build BSD along with everything else, =
from scratch, for each and every<BR>release, submittal, nightly build, =
freckle on my @ss, and so on.&nbsp; Is<BR>there some reason we don't =
just move to that model, so we won't ever<BR>have these problems ever =
again?&nbsp; My ignorance is a product of a troubled<BR>childhood, so =
don't be insensitive you guys.&nbsp; You know how you =
are.<BR><BR>a<BR><BR><BR>On Wed, 16 May 2007 11:43:31 -0700 "Ken =
Renshaw"<BR>&lt;ken.renshaw@onstor.com&gt; wrote:<BR><BR>&gt; From now =
on I will add a step in the build process for patches to do<BR>&gt; a =
quick file delta from the previous patch and include that in the<BR>&gt; =
build info. Hopefully that will help us flag these kinds of =
things<BR>&gt; before they leave the building. Thanks,<BR>&gt; =
-Ken<BR>&gt;<BR>&gt; ________________________________<BR>&gt;<BR>&gt; =
From: Ken Renshaw<BR>&gt; Sent: Wed 5/16/2007 11:37 AM<BR>&gt; To: Ed =
Kwan; Huy Duong; David Crispin; Victor Carrell (Glasshouse);<BR>&gt; =
dl-cstech Cc: Danqing Jin; Erik Palomba; Ken Renshaw<BR>&gt; Subject: =
RE: 2.2.2.5 w/n boot<BR>&gt;<BR>&gt;<BR>&gt; =
Hello.<BR>&gt;&nbsp;<BR>&gt; The last four patches have all been done =
with the same build of bsd:<BR>&gt;&nbsp;<BR>&gt; [build@k2 =
Build-Trees]$ strings<BR>&gt; =
R2.2.2.3/R2.2.2.3-041807/nfx-tree/Build/bc/opt/Release/bsd | =
grep<BR>&gt; OpenBSD| grep BOBCAT @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan =
18 13:34:43<BR>&gt; PST 2007 [build@k2 Build-Trees]$ strings<BR>&gt; =
R2.2.2.4/R2.2.2.4-042507/nfx-tree/Build/bc/opt/Release/bsd | =
grep<BR>&gt; OpenBSD| grep BOBCAT @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan =
18 13:34:43<BR>&gt; PST 2007 [build@k2 Build-Trees]$ strings<BR>&gt; =
R2.2.2.5/R2.2.2.5-043007/nfx-tree/Build/bc/opt/Release/bsd | =
grep<BR>&gt; OpenBSD| grep BOBCAT @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan =
18 13:34:43<BR>&gt; PST 2007 [build@k2 Build-Trees]$ strings<BR>&gt; =
R2.2.2.6/R2.2.2.6-051407/nfx-tree/Build/bc/opt/Release/bsd | =
grep<BR>&gt; OpenBSD| grep BOBCAT @(#)OpenBSD 2.8 (BOBCAT) #0: Thu Jan =
18 13:34:43<BR>&gt; PST 2007 This is not a matter of using the wrong BSD =
to package the<BR>&gt; patch. It's a case of someone corrupting the =
posted BSD images,<BR>&gt; probably by doing a p4 sync when =
/usr/openbsd.new was pointed to the<BR>&gt; 2.2.x BSD when they thought =
it was pointed to DeLorean.<BR>&gt;<BR>&gt; In the Notes section of CQ =
19207 Danqing does a compare of the two<BR>&gt; files /etc/rc and =
/etc/mdrive_fstab and found they had parts of<BR>&gt; recent DeLorean =
changes grafted into them. These same pieces are in<BR>&gt; the posted =
BSD build for 2.2.x: /n/Build-Trees/BSD/openbsd-latest-22<BR>&gt; I =
believe all we have to do to fix this is copy the correct<BR>&gt; 2.2.x =
/etc files into the posted 2.2.x BSD build and rebuild the<BR>&gt; patch =
tarfiles. Ed, you'd said spin 2.2.2.5 as 2.2.2.7, but isn't<BR>&gt; what =
we want to do is respin 2.2.2.6 as 2.2.2.7 with the<BR>&gt; corrected =
/etc files so they stay cumulative? Please confirm, then<BR>&gt; I'll go =
ahead and do this. Thanks,<BR>&gt; -Ken<BR>&gt;<BR>&gt; =
________________________________<BR>&gt;<BR>&gt; From: Ed Kwan<BR>&gt; =
Sent: Wed 5/16/2007 11:05 AM<BR>&gt; To: Huy Duong; David Crispin; =
Victor Carrell (Glasshouse); dl-cstech<BR>&gt; Cc: Ken Renshaw; Danqing =
Jin; Erik Palomba<BR>&gt; Subject: RE: 2.2.2.5 w/n =
boot<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; TED 19207.&nbsp; Need to re-spin =
2.2.2.5 (as 2.2.2.7) with the correct BSD.<BR>&gt;<BR>&gt; &gt; =
-----Original Message-----<BR>&gt; &gt; From: Huy Duong<BR>&gt; &gt; =
Sent: Wednesday, May 16, 2007 9:01 AM<BR>&gt; &gt; To: David Crispin; =
Victor Carrell (Glasshouse); dl-cstech<BR>&gt; &gt; Subject: Re: 2.2.2.5 =
w/n boot<BR>&gt; &gt;<BR>&gt; &gt; Victor file a bug. This is very =
serious I will escalate it.<BR>&gt; &gt; =
-----------------------------------------<BR>&gt; &gt; Huy Duong<BR>&gt; =
&gt; ONStor Strategic Support Account Manager<BR>&gt; &gt; Phone =
408.963.2478<BR>&gt; &gt; Cell&nbsp;&nbsp;&nbsp; 408.431.6803<BR>&gt; =
&gt; <A =
href=3D"http://support.onstor.com/">http://support.onstor.com/</A><BR>&gt=
; &gt; Sent From My Blackberry<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; =
-----Original Message-----<BR>&gt; &gt; From: David Crispin<BR>&gt; &gt; =
To: Victor Carrell (Glasshouse); dl-cstech<BR>&gt; &gt; Sent: Wed May 16 =
08:48:45 2007<BR>&gt; &gt; Subject: Re: 2.2.2.5&nbsp; w/n boot<BR>&gt; =
&gt;<BR>&gt; &gt; I had the same thing yesterday. System upgrade, =
compare then reboot<BR>&gt; &gt; -s and it never came back. This was in =
a remote data centre. A real<BR>&gt; &gt; pain. It's still down.<BR>&gt; =
&gt;<BR>&gt; &gt; Regards,<BR>&gt; &gt; David Crispin<BR>&gt; &gt; =
Technical Services Manager<BR>&gt; &gt; ONStor Ltd.<BR>&gt; &gt; 07940 =
547895<BR>&gt; &gt;<BR>&gt; &gt; Sent from my Blackberry<BR>&gt; =
&gt;<BR>&gt; &gt; -----Original Message-----<BR>&gt; &gt; From: Victor =
Carrell (Glasshouse)<BR>&gt; &gt; To: dl-cstech<BR>&gt; &gt; Sent: Wed =
May 16 07:41:42 2007<BR>&gt; &gt; Subject: 2.2.2.5&nbsp; w/n =
boot<BR>&gt; &gt;<BR>&gt; &gt; Hi All,<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; =
&gt;<BR>&gt; =
&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<BR>&gt; &gt; =
boot a 22xx 2.2.2.5 after an upgrade?<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; =
&gt;<BR>&gt; &gt; We tried upgrading LA Health yesterday 2 systems 1 =
system twice.<BR>&gt; &gt; Everything runs clean compare, md5 and =
version -s ok but will not<BR>&gt; &gt; boot<BR>&gt; &gt;<BR>&gt; =
&gt;<BR>&gt; &gt;<BR>&gt; &gt; I tried the same upgrade from a local ftp =
server to our systems<BR>&gt; &gt; in-house w/same results.<BR>&gt; =
&gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; Thanks<BR>&gt; &gt;<BR>&gt; =
&gt; Victor<BR>&gt;<BR>&gt;<BR>&gt;<BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C797EC.6725536A--
