X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7AC7A.5EF1DBD3@onstor-exch02.onstor.net>; Mon, 11 Jun 2007 15:46:38 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: FW: 3.0 system config copy
Date: Mon, 11 Jun 2007 15:46:38 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E041BF4D6@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: 3.0 system config copy
Thread-Index: Acep5pv9gtJz6XfeTzahbqIvDiJXngCWwpfAAABWMDAAANcScAAAeiOwAABP/rAAARnrwAAAmq8QAAluY5IAADaKcAAAIKjg
From: "Jay Michlin" <jay.michlin@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Larry Scheer" <larry.scheer@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>
Cc: "Brian DeForest" <brian.deforest@onstor.com>

Hi guys,

As you can see from Sudheesh's message, some of our comments were a
little tough on the SEs. I don't really have an opinion about whether
they screwed up or not, and I'm not spending a lot of time deciding. I
figure they have a tough life out there, dealing with demanding
customers and our Delorean release being late. I'll bet from their point
of view they are not even sure when we will ship Delorean, and fear
something scary is going on that we aren't telling them. So I want to be
as considerate as I can for them.

At the same time, I know we have a tough time too. We didn't ask for
this upgrade program assignment, and especially not so late in the
project. It has disrupted our other work, and other parts of the
organization have been inconsiderate of us. So we're rightly frustrated
and tense on the topic.

Life's a bitch, huh? But let's do our best to practice the Golden Rule
and treat others with care and consideration, even if they don't do the
same for us. If we do that, we'll think better of our ourselves as
professionals and as people. Beyond that, I don't care what anyone else
thinks.

jay


-----Original Message-----
From: Jay Michlin=20
Sent: Monday, June 11, 2007 3:24 PM
To: Sudheesh Nair
Cc: Tom Gallivan
Subject: RE: 3.0 system config copy

Sudheesh,

Thanks for understanding and asking your team to forgive our comments.
There's a lot of stress here, and I think that was behind it.

The bottom line is this:

1. We don't really think anyone on your team caused this, no matter what
those "shooting from the hip" messages said.

2. We stand ready to help in any way we can.

jay
=20

-----Original Message-----
From: Sudheesh Nair
Sent: Monday, June 11, 2007 3:16 PM
To: Jay Michlin
Cc: Tom Gallivan
Subject: Re: 3.0 system config copy

Jay

Both Andy's and Larry's email was quick to point fingers at SEs, while
in this case we just took the flash cards from OPs and followed the
instructions sent to us from QE.=20

Please take care of this and let's me know how to solve this without
more fingerpointing. I am on the road, but willing to help in any way I
can.=20

I asked my team to ignore all the "uncalled-for" blame coming towards us
for now.=20


Regards,
Sudheesh
sudheesh.nair@onstor.com
408-802-2856
--------------------------
Sent from my BlackBerry Wireless Handheld=20

-----Original Message-----
From: Jay Michlin
To: Sudheesh Nair; Caeli Collins
CC: Paul Hammer; Andy Sharp; Larry Scheer; Tim Gardner; Brian DeForest
Sent: Mon Jun 11 10:47:43 2007
Subject: FW: 3.0 system config copy

Sudheesh, Caeli,
=20
Larry's comment below, and Andy's more pointed comment earlier, suggest
there may be some confusion. If it would be of use to you, we would be
happy to have a brief meeting to discuss and resolve any issues and get
everybody on a productive track. If that's of interest, please let me
know. If not, just delete.
=20
jay

________________________________

From: Larry Scheer
Sent: Monday, June 11, 2007 10:35 AM
To: Jay Michlin
Cc: Andy Sharp; Tim Gardner
Subject: RE: 3.0 system config copy



The SEs are really confused about the flash install. It sounds like they
made their own flashes incorrectly and are propagating the bad set
amongst their ranks. This is pure speculation on my part. Do we need to
grab Sudheesh and perhaps some other lead SEs and educate them?

=20

Larry

=20

________________________________

From: Jay Michlin
Sent: Monday, June 11, 2007 9:58 AM
To: Andy Sharp; Larry Scheer; Tim Gardner
Subject: FW: 3.0 system config copy

=20

FYI.

(Brian is already cc'd via dl-Delorean)

=20

________________________________

From: Caeli Collins
Sent: Monday, June 11, 2007 9:48 AM
To: dl-Delorean
Subject: FW: 3.0 system config copy

forwarding to a larger audience

=20

Caeli=20

=20

=20

________________________________

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!

=20

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:

=20

mount -uw /

touch /etc/.autoupgrade

=20

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.

=20

=20

=20

________________________________

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,

=20

I should have copied you as well.

=20

Dave.

=20

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

=20

Guys,

=20

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.

=20

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.

=20

Here is the text from the session:-

=20

User pressed ENTER

=20

gathering system info, please wait...

=20

                 ONStor NAS Gateway Initial Configuration Tool

=20

=20

=20

     1. Configure Administrative Settings

=20

=20

     2. Configure Network Settings

=20

=20

     3. Display Current Settings

=20

=20

     4. Commit Changes

=20

=20

     5. Help

=20

=20

     6. Copy Configuration Files From Secondary Flash

=20

=20

     7. Exit

=20

=20

    Enter Selection: 6

=20

Value Entered is 6

=20

=20

                 Copy Configuration Files from Secondary Flash

=20

=20

=20

     1. Copy Configuration and proceed with bringup

=20

=20

     2. No - return to main menu

=20

=20

    Enter Selection: 1

=20

Value Entered is 1

=20

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

=20

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

=20

=20

Welcome to the ONStor NAS Gateway.

=20

Initialization in progress...

\

Timeout... Try logging in later - It now makes you wait until it is
fully up!

=20

=20

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

=20

=20

Welcome to the ONStor NAS Gateway.

=20

bobcat> sys ver

3.0.0.0

bobcat>

=20

=20

=20

=20

David Crispin

Technical Services Manager

=20

ONStor, Inc.

office: +44(0)118 963 5866

mobile: +44(0)7940 547 895

=20

=20

david.crispin@onstor.com

http://www.onstor.com

     =20

-----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

=20

Just a clarification.  After inserting the 3.0 flash, do a "system
reboot

-s".

=20

DC

=20

> 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

>=20

> Hey Everyone,

>=20

> I believe that there is a fundamental misunderstanding of the feature=20
> 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.

>=20

> In pre-3.0 versions of EverON the compact flashes are partitioned=20
> drives

> each with six partitions upon which a filesystem is created and the=20
> ONStor

> binaries are stored.  In Ever-ON 3.0 the compact flashes are=20
> partitioned

> with only 4 partitions.

>=20

> In pre-3.0 version of EverON, commands such as "system config copy",=20
> "system

> copy all -I", and "system upgrade -s" are all dependent on, and look

> specifically for, the compact flashes with 6 partitions.  Hence, the=20
> only

> way to upgrade a running system from pre-3.0 to 3.0 is to use a new=20
> compact

> flash from corporate with 3.0 preloaded; a "system upgrade -s" will=20
> 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=20
> "system

> config copy" will not work since it doesn't understand the new=20
> partition

> layout.

>=20

> So, how do you upgrade an existing system without rebuilding the=20
> 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=20
> 3.0

> flash has the intelligence built in to grab the configuration files=20
> from the

> pre-3.0 flash and boot fully into a configured 3.0 system.  Note that=20
> there

> are no changes to the remaining pre-3.0 flash.  And, until the last=20
> node in

> the cluster has been upgraded to 3.0, there are no permanent changes=20
> to the

> cluster database -- you can "revert" back to pre-3.0 just by doing a=20
> "system

> reboot -s".

>=20

> 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. =20
> 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,=20
> your

> revert window is closed.

>=20

> Another major item to note is the introduction of a new command,=20
> "filesystem

> convert".  This command converts existing StorFS filesystem from=20
> version 26

> to version 28.  This supports some of the new underlying filesystem=20
> features

> introduced in 3.0.  Obviously, if you have a version 28 filesystem=20
> that was

> either newly created or recently upgraded, you cannot use this=20
> filesystem in

> a pre-3.0 cluster.  Once you create, or upgrade to, a version 28=20
> filesystem,

> you cannot "revert to a previous OS version".

>=20

> Hope this helps.

>=20

> Doug

>=20

>=20

>=20

>> 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

>>=20

>> I'd like to emphasize what Tim says. The option to keep different=20
>> 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.

>>=20

>> st.

>>=20

>> Steffen Thuemmel

>>=20

>> ONStor GmbH

>>=20

>> telf.      +49 6102 884 84-0

>> mobil.     +49 173 673 3434

>> mail.       steffen.thuemmel@onstor.com

>>  =20

>>=20

>> -----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

>>=20

>> Isn't this a little unsound? It will remove our backout option

>>=20

>> Tim

>> Tim.OCallaghan@onstor.com

>>=20

>> M:+44 7767435472

>> --------------------------

>> Sent using BlackBerry

>>=20

>>=20

>> -----Original Message-----

>> From: Sudheesh Nair

>> To: dl-se; dl-Training

>> Sent: Thu Jun 07 07:31:41 2007

>> Subject: 3.0 system config copy

>>=20

>> Hi all:

>>=20

>> In 3.0 system config copy is done automatically after reboots.

>>=20

>> No need to manuall copy config from pri to second.

>>=20

>>=20

>> Regards,

>> Sudheesh

>> sudheesh.nair@onstor.com

>> 408-802-2856

>> --------------------------

>> Sent from my BlackBerry Wireless Handheld

>=20

>=20

=20

