AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070216131433.63c0de48@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<caeli.collins@onstor.com>,<eric.barrett@onstor.com>,<ed.kwan@onstor.com>,<jay.michlin@onstor.com>,<tim.gardner@onstor.com>,<larry.scheer@onstor.com>,<paul.hammer@onstor.com>,<dl-software@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 16 Feb 2007 13:18:48 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: Caeli Collins <caeli.collins@onstor.com>, Eric Barrett
 <eric.barrett@onstor.com>, Ed Kwan <ed.kwan@onstor.com>, Jay Michlin
 <jay.michlin@onstor.com>, Tim Gardner <tim.gardner@onstor.com>, Larry
 Scheer <larry.scheer@onstor.com>, Paul Hammer <paul.hammer@onstor.com>,
 dl-software@onstor.com
Subject: corruption and upgrade workflow for Lambo [and 1.3.3.?]
Message-ID: <20070216131848.4c238b19@ripper.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

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
