AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070510140115.6483adfd@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.deforest@onstor.com>,<larry.scheer@onstor.com>,<tim.gardner@onstor.com>,<jay.michlin@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	10004	BB375AF679D4A34E9CA8DFA650E2B04E03A8DFD9@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 10 May 2007 14:01:18 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Brian DeForest" <brian.deforest@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>, "Tim Gardner"
 <tim.gardner@onstor.com>, "Jay Michlin" <jay.michlin@onstor.com>
Subject: Re: Blocker issue for MD upgrade to 3.0
Message-ID: <20070510140118.409f1ab0@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E03A8DFD9@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E02679C93@onstor-exch02.onstor.net>
 <BB375AF679D4A34E9CA8DFA650E2B04E03A8DFD9@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


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.
> 
>  
> 
> ________________________________
> 
> From: Sandrine Boulanger 
> Sent: Thursday, May 10, 2007 1:04 PM
> To: dl-Delorean Core Team
> Subject: Blocker issue for MD upgrade to 3.0
> 
>  
> 
> 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.
> 
>  
> 
> System config copy is not looking at the standby flash fstab to mount
> the devices it needs to copy the active flash configuration files.
> 
> 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.
> 
>  
> 
> 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.
> 
>  
> 
> Workaround would be:
> 
> - mount each device manually to copy the config files
> 
> Or
> 
> - 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
> 
>  
> 
> Final solution could be: 
> 
> - rename the partitions of the new layout to map with fstab of earlier
> releases, if possible
> 
>  
> 
> ________________________________
> 
> From: John Keiffer 
> Sent: Thursday, May 10, 2007 12:49 PM
> To: Sandrine Boulanger; Raj Kumar
> Subject: new blocker bug 19122
> 
>  
> 
> 19122   Opened 1-Critical           Can't "system config copy" from
> 2.2 to 3.0           5/10/2007 12:42:46 PM
> 
>  
> 
> Thank you,
> 
> John Keiffer
> 
>  
> 
>  
> 
