AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070611100134.0619e4ba@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<caeli.collins@onstor.com>,<dl-Delorean@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	BB375AF679D4A34E9CA8DFA650E2B04E041BF1B7@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 11 Jun 2007 10:01:45 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Caeli Collins" <caeli.collins@onstor.com>
Cc: "dl-Delorean" <dl-Delorean@onstor.com>
Subject: Re: 3.0 system config copy
Message-ID: <20070611100145.25a890eb@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E041BF1B7@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E041BF1B7@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

Such nonsense.  Please don't spread voodoo rumours like this.  99.999%
(5 nines) likely pilot error.  I don't care what "David swears."
Remember, if the card wasn't built the right way, it is just a regular
3.0 with no magical config copy capabilities.

On Mon, 11 Jun 2007 09:48:17 -0700 "Caeli Collins"
<caeli.collins@onstor.com> wrote:

> forwarding to a larger audience
>  
> 
> Caeli 
> 
>  
> 
> ________________________________
> 
> From: Eric Barrett 
> Sent: Monday, June 11, 2007 9:45 AM
> To: David Crispin; Carlos Mora; Caeli Collins
> Subject: RE: 3.0 system config copy
> 
> 
> I talked to David.  He's absolutely sure the first time the system
> loaded, using a prepared Delorean flash card, he got the ICT menu
> instead of an automatic copy.  Bad news!
>  
> David, as a workaround, I figured out how to "reset" the configuration
> copy after a system config reset.  Before doing the system config
> reset, run these two commands as root:
>  
> mount -uw /
> touch /etc/.autoupgrade
>  
> This will prepare the flash card for automatic copy again.  I haven't
> tested this procedure, but it's taken right from the installation
> script that Operations and Dev use.
>  
>  
> 
> 
> ________________________________
> 
> From: David Crispin 
> Sent: Monday, June 11, 2007 9:11 AM
> To: Eric Barrett; Carlos Mora
> Subject: FW: 3.0 system config copy
> 
> 
> 
> Eric, Carlos,
> 
>  
> 
> I should have copied you as well.
> 
>  
> 
> Dave.
> 
>  
> 
> From: David Crispin 
> Sent: 11 June 2007 17:10
> To: Doug Cook; Steffen Thuemmel; Tim O'Callaghan; Sudheesh Nair; dl-se
> Subject: RE: 3.0 system config copy
> 
>  
> 
> Guys,
> 
>  
> 
> I just did an upgrade today on a spare 2220 before I do it live
> tomorrow and this is what I found. Just doing a system reboot -s
> doesn't automatically copy the system config and upgrade you to 3.0.
> 
>  
> 
> I only saw this as I was running the system reboot -s command from the
> serial console. It comes up just like a new install with the ICT and
> you have new options to copy the system config. This needs to be put
> in the Release Notes in the Compact Flash Card Upgrade Procedure
> section.
> 
>  
> 
> Here is the text from the session:-
> 
>  
> 
> User pressed ENTER
> 
>  
> 
> gathering system info, please wait...
> 
>  
> 
>                  ONStor NAS Gateway Initial Configuration Tool
> 
>  
> 
>  
> 
>  
> 
>      1. Configure Administrative Settings
> 
>  
> 
>  
> 
>      2. Configure Network Settings
> 
>  
> 
>  
> 
>      3. Display Current Settings
> 
>  
> 
>  
> 
>      4. Commit Changes
> 
>  
> 
>  
> 
>      5. Help
> 
>  
> 
>  
> 
>      6. Copy Configuration Files From Secondary Flash
> 
>  
> 
>  
> 
>      7. Exit
> 
>  
> 
>  
> 
>     Enter Selection: 6
> 
>  
> 
> Value Entered is 6
> 
>  
> 
>  
> 
>                  Copy Configuration Files from Secondary Flash
> 
>  
> 
>  
> 
>  
> 
>      1. Copy Configuration and proceed with bringup
> 
>  
> 
>  
> 
>      2. No - return to main menu
> 
>  
> 
>  
> 
>     Enter Selection: 1
> 
>  
> 
> Value Entered is 1
> 
>  
> 
> Copying configuration...........................done.
> 
> starting network
> 
> add net default: gateway 192.168.0.1
> 
> starting system logger
> 
> starting rpc daemons: portmap ypserv ypbind.
> 
> sendto: Network is down
> 
> savecore: no core dump
> 
> building ps databases: kvm dev.
> 
> clearing /tmp
> 
> starting pre-securelevel daemons: tickadj.
> 
> setting kernel security level: kern.securelevel: 0 -> 1
> 
> remounting root read-only...done.
> 
> starting network daemons: inetd sshd.
> 
> starting local daemons: ntpdate ntpd.
> 
> starting agile daemons: mgmtbus0 pm.
> 
> created /tmp/ramdisk
> 
> starting mount_mfs: done
> 
> standard daemons: cron.
> 
> checking domain name [SANfiler]... passed
> 
> Mon Jun 11 16:53:09 BST 2007
> 
>  
> 
> login: admin
> 
> Password:
> 
> Last login: Mon Jun 11 16:47:22 on console
> 
> OpenBSD 2.8 (BOBCAT) #0: Mon Jun  4 14:42:17 PDT 2007
> 
>  
> 
>  
> 
> Welcome to the ONStor NAS Gateway.
> 
>  
> 
> Initialization in progress...
> 
> \
> 
> Timeout... Try logging in later - It now makes you wait until it is
> fully up!
> 
>  
> 
>  
> 
> login: admin
> 
> Password:
> 
> Last login: Mon Jun 11 16:53:30 on console
> 
> OpenBSD 2.8 (BOBCAT) #0: Mon Jun  4 14:42:17 PDT 2007
> 
>  
> 
>  
> 
> Welcome to the ONStor NAS Gateway.
> 
>  
> 
> bobcat> sys ver
> 
> 3.0.0.0
> 
> bobcat>
> 
>  
> 
>  
> 
>  
> 
>  
> 
> David Crispin
> 
> Technical Services Manager
> 
>  
> 
> ONStor, Inc.
> 
> office: +44(0)118 963 5866
> 
> mobile: +44(0)7940 547 895
> 
>  
> 
>  
> 
> david.crispin@onstor.com
> 
> http://www.onstor.com
> 
>       
> 
> -----Original Message-----
> From: Doug Cook 
> Sent: 08 June 2007 17:04
> To: Doug Cook; Steffen Thuemmel; Tim O'Callaghan; Sudheesh Nair; dl-se
> Subject: Re: 3.0 system config copy
> 
>  
> 
> Just a clarification.  After inserting the 3.0 flash, do a "system
> reboot
> 
> -s".
> 
>  
> 
> DC
> 
>  
> 
> > From: Doug Cook <doug.cook@onstor.com>
> 
> > Date: Fri, 08 Jun 2007 11:16:00 -0400
> 
> > To: Steffen Thuemmel <steffen.thuemmel@onstor.com>, Tim O'Callaghan
> 
> > <tim.ocallaghan@onstor.com>, Sudheesh Nair
> > <sudheesh.nair@onstor.com>,
> dl-se
> 
> > <dl-se@onstor.com>
> 
> > Subject: Re: 3.0 system config copy
> 
> > 
> 
> > Hey Everyone,
> 
> > 
> 
> > I believe that there is a fundamental misunderstanding of the
> > feature
> in 3.0
> 
> > that copies information from the pre-3.0 flash.  Let me explain it
> > the
> way I
> 
> > understand it and hope this clears the confusion.
> 
> > 
> 
> > In pre-3.0 versions of EverON the compact flashes are partitioned
> drives
> 
> > each with six partitions upon which a filesystem is created and the
> ONStor
> 
> > binaries are stored.  In Ever-ON 3.0 the compact flashes are
> partitioned
> 
> > with only 4 partitions.
> 
> > 
> 
> > In pre-3.0 version of EverON, commands such as "system config copy",
> "system
> 
> > copy all -I", and "system upgrade -s" are all dependent on, and look
> 
> > specifically for, the compact flashes with 6 partitions.  Hence, the
> only
> 
> > way to upgrade a running system from pre-3.0 to 3.0 is to use a new
> compact
> 
> > flash from corporate with 3.0 preloaded; a "system upgrade -s" will
> not
> 
> > work.  Once you swap the secondary flash with the new 3.0 flash,
> > there
> is no
> 
> > way to copy the current cluster configuration to the new flash -- a
> "system
> 
> > config copy" will not work since it doesn't understand the new
> partition
> 
> > layout.
> 
> > 
> 
> > So, how do you upgrade an existing system without rebuilding the
> cluster
> 
> > from scratch?  After swapping out the pre-3.0 secondary flash with
> > the
> 3.0
> 
> > flash, you are supposed to just reboot the filer.  Upon booting, the
> 3.0
> 
> > flash has the intelligence built in to grab the configuration files
> from the
> 
> > pre-3.0 flash and boot fully into a configured 3.0 system.  Note
> > that
> there
> 
> > are no changes to the remaining pre-3.0 flash.  And, until the last
> node in
> 
> > the cluster has been upgraded to 3.0, there are no permanent changes
> to the
> 
> > cluster database -- you can "revert" back to pre-3.0 just by doing a
> "system
> 
> > reboot -s".
> 
> > 
> 
> > Once all of the nodes are upgraded to 3.0 and the cluster database
> > has
> been
> 
> > upgraded, you lose the ability to revert to a pre-3.0 state UNLESS
> > you
> are
> 
> > willing to reboot every node simultaneously to the pre-3.0 flash.
> Note that
> 
> > any changes you have made (new vsvrs, new shares, etc) since
> > upgrading
> will
> 
> > be lost.  Plus, if you have done any "system config copy" commands,
> your
> 
> > revert window is closed.
> 
> > 
> 
> > Another major item to note is the introduction of a new command,
> "filesystem
> 
> > convert".  This command converts existing StorFS filesystem from
> version 26
> 
> > to version 28.  This supports some of the new underlying filesystem
> features
> 
> > introduced in 3.0.  Obviously, if you have a version 28 filesystem
> that was
> 
> > either newly created or recently upgraded, you cannot use this
> filesystem in
> 
> > a pre-3.0 cluster.  Once you create, or upgrade to, a version 28
> filesystem,
> 
> > you cannot "revert to a previous OS version".
> 
> > 
> 
> > Hope this helps.
> 
> > 
> 
> > Doug
> 
> > 
> 
> > 
> 
> > 
> 
> >> From: "Steffen Thuemmel" <steffen.thuemmel@onstor.com>
> 
> >> Date: Fri, 8 Jun 2007 05:50:16 -0700
> 
> >> To: "Tim O'Callaghan" <tim.ocallaghan@onstor.com>, "Sudheesh Nair"
> 
> >> <sudheesh.nair@onstor.com>, "dl-se" <dl-se@onstor.com>,
> >> "dl-Training"
> 
> >> <dl-Training@onstor.com>
> 
> >> Subject: RE: 3.0 system config copy
> 
> >> 
> 
> >> I'd like to emphasize what Tim says. The option to keep different
> versions
> 
> >> and
> 
> >> configurations on the second flash card is welcomed in sales
> >> calls. I
> hope
> 
> >> there is a switch to turn this automatic copy off.
> 
> >> 
> 
> >> st.
> 
> >> 
> 
> >> Steffen Thuemmel
> 
> >> 
> 
> >> ONStor GmbH
> 
> >> 
> 
> >> telf.      +49 6102 884 84-0
> 
> >> mobil.     +49 173 673 3434
> 
> >> mail.       steffen.thuemmel@onstor.com
> 
> >>   
> 
> >> 
> 
> >> -----Original Message-----
> 
> >> From: Tim O'Callaghan
> 
> >> Sent: Donnerstag, 7. Juni 2007 18:00
> 
> >> To: Sudheesh Nair; dl-se; dl-Training
> 
> >> Subject: Re: 3.0 system config copy
> 
> >> 
> 
> >> Isn't this a little unsound? It will remove our backout option
> 
> >> 
> 
> >> Tim 
> 
> >> Tim.OCallaghan@onstor.com
> 
> >> 
> 
> >> M:+44 7767435472
> 
> >> --------------------------
> 
> >> Sent using BlackBerry
> 
> >> 
> 
> >> 
> 
> >> -----Original Message-----
> 
> >> From: Sudheesh Nair
> 
> >> To: dl-se; dl-Training
> 
> >> Sent: Thu Jun 07 07:31:41 2007
> 
> >> Subject: 3.0 system config copy
> 
> >> 
> 
> >> Hi all:
> 
> >> 
> 
> >> In 3.0 system config copy is done automatically after reboots.
> 
> >> 
> 
> >> No need to manuall copy config from pri to second.
> 
> >> 
> 
> >> 
> 
> >> Regards,
> 
> >> Sudheesh
> 
> >> sudheesh.nair@onstor.com
> 
> >> 408-802-2856
> 
> >> --------------------------
> 
> >> Sent from my BlackBerry Wireless Handheld
> 
> > 
> 
> > 
> 
>  
> 
