X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C79349.8872FBA2@onstor-exch02.onstor.net>; Thu, 10 May 2007 14:24:03 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Blocker issue for MD upgrade to 3.0
Date: Thu, 10 May 2007 14:24:02 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E03A8E083@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E022157BD@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Blocker issue for MD upgrade to 3.0
Thread-Index: AceTRlraRHTMuW5bSQWRCiid6ggKQQAAG5GwAACNcMA=
References: <20070510140118.409f1ab0@ripper.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E022157BD@onstor-exch02.onstor.net>
From: "Brian DeForest" <brian.deforest@onstor.com>
To: "Larry Scheer" <larry.scheer@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>
Cc: "Tim Gardner" <tim.gardner@onstor.com>,
	"Jay Michlin" <jay.michlin@onstor.com>

MD is the customer.   What do we tell them to do?   Sandrine's
suggestions weren't addressed.  =20

-----Original Message-----
From: Larry Scheer=20
Sent: Thursday, May 10, 2007 2:15 PM
To: Andy Sharp; Brian DeForest
Cc: Tim Gardner; Jay Michlin
Subject: RE: Blocker issue for MD upgrade to 3.0

You can't upgrade a blank flash prior to Delorean. So doing a system
copy init won't buy you anything. The upgrade will fail because it can't
find a versions file on the secondary flash.

Using upgrade from 2.2.2.x -> 3.0 on a bobcat will most likely succeed
just takes about 45 minutes to complete, IF you don't run into space
issues.

Upgrading from 2.2.2.x -> 3.0 on a cheetah is iffy.

A workaround to speed up both installs is to copy the Delorean version
of /usr/local/agile/bin/verify_install.sh to the 2.2.2.X host and then
run the upgrade. But you will be running 3.0 with the old flash layout
which is not what we want.

What QA was testing was a flash install they wanted to get the system
configuration onto the secondary flash and it failed. They were hoping
to do this on Mightdog, but hit this problem.

-----Original Message-----
From: Andy Sharp=20
Sent: Thursday, May 10, 2007 2:01 PM
To: Brian DeForest
Cc: Larry Scheer; Tim Gardner; Jay Michlin
Subject: Re: Blocker issue for MD upgrade to 3.0


This is something that has been discussed a million times.  You can
upgrade from 2.2 -> 3.0, but it might fail due to being out of space on
the CF. If you are running 2.2.2.x or earlier, you have to upgrade to
2.2.3, boot and run 2.2.3, do a _system copy init_ followed by a system
upgrade in order to use the dynamic flash partition layout.

In the absence of a 2.2.3 release, you have to do the same thing but to
3.0 instead of 2.2.3, and hope that you don't run out of space on the
CF.  Then do a _system copy all -i_ and _reboot -s_ to switch over to
the dynamic flash layout.

Cheers,

a

On Thu, 10 May 2007 13:09:06 -0700 "Brian DeForest"
<brian.deforest@onstor.com> wrote:

> Guys, the goal is to upgrade MD today if possible.   Apparently QA
> never tested a 2.2->3.0 upgrade.    This needs to be higher priority
> than other Delorean defects.    Please review this.   Thanks.
>=20
> =20
>=20
> ________________________________
>=20
> From: Sandrine Boulanger=20
> Sent: Thursday, May 10, 2007 1:04 PM
> To: dl-Delorean Core Team
> Subject: Blocker issue for MD upgrade to 3.0
>=20
> =20
>=20
> We just ran into this issue when trying to copy the config files from
> our 2.2 cluster to 3.0 brand new flash running sub#16. This is related
> to old and new CF layout.
>=20
> =20
>=20
> System config copy is not looking at the standby flash fstab to mount
> the devices it needs to copy the active flash configuration files.
>=20
> Since the names of the devices have changed between the 2 layouts,
> it's trying to mount a device that does not exist on the standby
> flash.
>=20
> =20
>=20
> When we tested this command earlier, we did not run into this issue
> because we were using 2.3 old and new layout, and I just found out
> that the system config copy command has been fixed in 2.3now3.0 to
> look at the fstab from the standby flash.
>=20
> =20
>=20
> Workaround would be:
>=20
> - mount each device manually to copy the config files
>=20
> Or
>=20
> - run system upgrade -s (this one should work since 2.2 already had
> the bom file and first upgrade changes) but we would run 3.0 with old
> CF layout
>=20
> =20
>=20
> Final solution could be:=20
>=20
> - rename the partitions of the new layout to map with fstab of earlier
> releases, if possible
>=20
> =20
>=20
> ________________________________
>=20
> From: John Keiffer=20
> Sent: Thursday, May 10, 2007 12:49 PM
> To: Sandrine Boulanger; Raj Kumar
> Subject: new blocker bug 19122
>=20
> =20
>=20
> 19122   Opened 1-Critical           Can't "system config copy" from
> 2.2 to 3.0           5/10/2007 12:42:46 PM
>=20
> =20
>=20
> Thank you,
>=20
> John Keiffer
>=20
> =20
>=20
> =20
>=20
