AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070516134855.14f6e5fd@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<ken.renshaw@onstor.com>,<larry.scheer@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E02F3D0B9@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 16 May 2007 13:50:07 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Ken Renshaw" <ken.renshaw@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>
Subject: Re: 2.2.2.5  w/n boot
Message-ID: <20070516135007.4407ee2a@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D0B9@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E01440474@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E023B3CF0@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E02F3D0B7@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E02F3D0B9@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Wow, that helps a lot.  I'll text my therapist.  What also helps is
getting in my truck and running over small import cars.  Really really
helps a lot.  Specially if they have one of those coffee can mufflers.
</sniff>

a

PS Hope I didn't come off like I'm telling people how to do their jobs,
if so, my bad.  Just trying to throw out ideas in case 1/10 is
helpful.  BTW, who is Jerry?  This email will self destruct...

On Wed, 16 May 2007 12:04:23 -0700 "Ken Renshaw"
<ken.renshaw@onstor.com> wrote:

> FYI, Jerry wants it to never happen again, so that's one piece of
> your inner child restored Andy. 
> -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. This won't keep the
> developers from stomping on the public copies I provide, but at least
> it will keep our releases clean. 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. Thanks, -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
> 
> 
> 
> 
> 
