AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070502103139.3e86662c@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<charissa.willard@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#mh/Mailbox/clearcrap	0	BB375AF679D4A34E9CA8DFA650E2B04E038C9573@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 2 May 2007 10:31:50 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Charissa Willard" <charissa.willard@onstor.com>
Subject: Re: Defect  TED00018399 system halted when reconfig the filer after
 system config reset
Message-ID: <20070502103150.4812211b@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E038C9573@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E038C9364@onstor-exch02.onstor.net>
	<20070501183548.423fde08@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E038C9573@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

flash_install

system config copy

reboot -s

Once submittal n+1 is released, submittal n is essentially
dead/obsolete.  It may contain bugs, it may be partially or wholly
incompatible (from an upgrade point of view) etc, and it shouldn't even
be run.

Obviously or not-obviously, I'm only speaking for the upgrade process
itself, not for clusterdb or anything else.

Cheers,

a


On Wed, 2 May 2007 09:54:36 -0700 "Charissa Willard"
<charissa.willard@onstor.com> wrote:

> John updated from submittal 11 to 12. May upgraded from submittal 10
> to 11. The steps May was instructed to do were:
> 
>  
> 
> 1) filer is upgraded to Delorean sub #11.
> 
> 2) system copy init
> 
> 3) system copy all
> 
> 4) system config copy
> 
> 5) system config reset
> 
>  
> 
> How should we update from one submittal to the next?
> 
>  
> 
> -Charissa
> 
>  
> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Tuesday, May 01, 2007 6:36 PM
> To: Charissa Willard
> Subject: Re: Defect TED00018399 system halted when reconfig the filer
> after system config reset
> 
>  
> 
> Upgrading to submittal 12 from what?  I keep trying to impress upon
> 
> people that upgrading between submittals is not supported and may
> 
> entertain numerous bugs and yet still they do it.  Sigh, sigh.
> 
>  
> 
> Cheers,
> 
>  
> 
> a
> 
>  
> 
> On Tue, 1 May 2007 18:20:00 -0700 "Charissa Willard"
> 
> <charissa.willard@onstor.com> wrote:
> 
>  
> 
> > Andy,
> 
> > 
> 
> >  
> 
> > 
> 
> > I wasn't able to reproduce this bug when loading submittal 12 on
> > g1r6.
> 
> > John K. ran into the same problem when upgrading to submittal 12 and
> 
>  
> 
> from what?
> 
>  
> 
> > then doing a "system config reset". He opened bug 18559 for this
> > issue
> 
> > which was marked a duplicate of this one. For now, I intend to mark
> 
> > this for more info since we really need elogs to tell us why we did
> > a
> 
> > shutdown in addition to why "some processes would not die" - see
> 
> > console output below.
> 
> > 
> 
> >  
> 
> > 
> 
> > Just off hand though, do you know what would cause rc.shutdown to be
> 
> > called by rc after we exit from rc.initial:
> 
> > 
> 
> >  
> 
> > 
> 
> > Rc line38:
> 
> > 
> 
> > ----------
> 
> > 
> 
> > if [ $1x = shutdownx ]; then
> 
> > 
> 
> >       dd if=/dev/urandom of=/var/db/host.random bs=1024 count=64
> 
> > >/dev/null 2>&1
> 
> > 
> 
> >       chmod 600 /var/db/host.random >/dev/null 2>&1
> 
> > 
> 
> >       if [ $? -eq 0 -a -f /etc/rc.shutdown ]; then
> 
> > 
> 
> >             echo /etc/rc.shutdown in progress...
> 
> > 
> 
> >             . /etc/rc.shutdown
> 
> > 
> 
> >             echo /etc/rc.shutdown complete.
> 
> > 
> 
> >             if [ "X${powerdown}" = X"YES" ]; then
> 
> > 
> 
> >                   exit 2
> 
> > 
> 
> >             fi
> 
> > 
> 
> >       else
> 
> > 
> 
> >             echo single user: not running /etc/rc.shutdown
> 
> > 
> 
> >       fi
> 
> > 
> 
> >       exit 0
> 
> > 
> 
> > fi
> 
> > 
> 
> >  
> 
> > 
> 
> >  
> 
> > 
> 
> > This is the console output:
> 
> > 
> 
> >  
> 
> > 
> 
> > Are you sure you do want to exit without configuring
> 
> > 
> 
> > these settings? (Yes or No) yes
> 
> > 
> 
> > starting network
> 
> > 
> 
> > add net default: gateway 10.2.0.1
> 
> > 
> 
> > starting system logger
> 
> > 
> 
> > starting rpc daemons: portmap ypserv ypbind.
> 
> > 
> 
> > 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.  <== hostidd not started
> 
> > 
> 
> > starting local daemons: ntpdate ntpd.
> 
> > 
> 
> > starting agile daemons: mgmtbus0 pm.
> 
> > 
> 
> > standard daemons: cron.
> 
> > 
> 
> > checking domain name [SANfiler]... passed
> 
> > 
> 
> > Thu Apr  5 09:25:54 PDT 2007
> 
> > 
> 
> >  
> 
> > 
> 
> > login: /etc/rc.shutdown in progress...
> 
> > 
> 
> > /etc/rc.shutdown complete.
> 
> > 
> 
> > Apr  5 09:26:56 init: some processes would not die; ps axl advised
> 
> > 
> 
> > syncing disks... done
> 
> > 
> 
> > System halted.
> 
> > 
> 
> >  
> 
> > 
> 
> > (Note: we didn't start the hostidd network daemon which means "uname
> 
> > -v" did not contain SSC_I)
> 
> > 
> 
> >  
> 
> > 
> 
> > Thanks,
> 
> > 
> 
> > Charissa
> 
> > 
> 
> >  
> 
> > 
> 
> > -----Original Message-----
> 
> > From: brian.deforest@onstor.com [mailto:brian.deforest@onstor.com] 
> 
> > Sent: Monday, April 30, 2007 11:29 PM
> 
> > To: Charissa Willard; May Ma
> 
> > Subject: Defect TED00018399 system halted when reconfig the filer
> 
> > after system config reset
> 
> > 
> 
> >  
> 
> > 
> 
> > id: TED00018399
> 
> > 
> 
> > Headline: system halted when reconfig the filer after system config
> 
> > reset
> 
> > 
> 
> > State: Assigned
> 
> > 
> 
> > Submitter: maym
> 
> > 
> 
> > Severity: 2-Major
> 
> > 
> 
> > Note_Entry: 
> 
> > 
> 
> > Area_of_problem: SW-System
> 
> > 
> 
> > Release_Project: Delorean
> 
> > 
> 
> >  
> 
> > 
> 
