X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C75212.7B87AD33@onstor-exch02.onstor.net>; Fri, 16 Feb 2007 14:36:13 -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: corruption and upgrade workflow for Lambo [and 1.3.3.?]
Date: Fri, 16 Feb 2007 14:36:13 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E027C1D39@onstor-exch02.onstor.net>
In-Reply-To: <20070216131848.4c238b19@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: corruption and upgrade workflow for Lambo [and 1.3.3.?]
Thread-Index: AcdSEAx3S52Rv7ogRZ+TLiGSjOypzgAAlEXw
From: "Jay Michlin" <jay.michlin@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Andy,

I don't know what others may say about this, but it seems like excellent
reasoning to me. I hope we follow it exactly as you laid it out.

jay=20

-----Original Message-----
From: Andy Sharp=20
Sent: Friday, February 16, 2007 1:19 PM
To: Caeli Collins; Eric Barrett; Ed Kwan; Jay Michlin; Tim Gardner;
Larry Scheer; Paul Hammer; dl-Software
Subject: corruption and upgrade workflow for Lambo [and 1.3.3.?]

Howdy,

Since I've been messing about with the upgrade code a bunch for
Delorean, I've been doing a lot of upgrades in the past several days in
the process of doing unit testing, and one thing I've noticed is that
upgrades from 1.3.3 to 2.2 or later always find several files that are
corrupted after the upgrade.

This is because the upgrade process has a corruption problem, as we all
know, which was fixed in 2.2 (and possibly some version of 1.3.3?).
However, when you upgrade to 2.2 you use the old, corruption prone,
upgrade process.

Therefore, I believe the workflow for upgrading from a non-upgrade-fixed
release to a fixed release requires that you actually upgrade twice.
You must be running the new version when you upgrade the second time.
So, for the sake of brevity, I will just mention
1.3.3 -> 2.2+ in the following:

1.  Upgrade from 1.3.3 or 2.1 to 2.2
2.  Boot 2.2
	Note: you may have problems at this point, since any file could
	conceivably be corrupted, including one of the .bin boot images
	for the TXRX or FP processors.  If necessary, log in quickly
	after rebooting and kill pm in order to keep the system from
	rebooting itself before you can execute the next step.
3.  Upgrade to 2.2 again.  You may use the same tar ball you did in
    step 1.

Please set aside a decent amount of time for this: upgrades in 2.2 are
not fast.  It downloads the tarball twice and verifies the entire system
twice for each upgrade.  I am fixing these issues in Delorean so we
won't have to live with this for too terribly long.

Cheers,

a
