AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20071212142132.0b884415@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<eric.barrett@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	BB375AF679D4A34E9CA8DFA650E2B04E07099F06@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 12 Dec 2007 14:22:45 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Eric Barrett" <eric.barrett@onstor.com>
Subject: Re: Directory and file name cleanup (ex. agile)
Message-ID: <20071212142245.4eb6aca3@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E07099F06@onstor-exch02.onstor.net>
References: <20071212130803.1f3558ea@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E05C73DD7@onstor-exch02.onstor.net>
	<20071212134518.5ea6b5d6@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E07099F06@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

On Wed, 12 Dec 2007 13:58:45 -0800 "Eric Barrett"
<eric.barrett@onstor.com> wrote:

> Curious -- if Linux/Cougar doesn't have crashdump files, what do we
> get instead?  They're a fairly important middle step between nada and
> full cores.

I have our kernel set up to issue a full symbolic stack trace and
register and stack dump upon panic/oops.  This is actually much better
and more reliable than a dump in most cases as it is done directly on
the machine in question so there is no need to match up kernels from
releases and what not.  This information goes into the log
file /var/log/messages (if you're living a clean life) and is therefore
retrievable with a system get all after a reboot.

On BSD, all we were able to do with a crash dump was get a stack trace,
and then only about half the time, I'm told.  So this is more than an
equivalent of previous capabilities.

Cheers,

a

> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Wednesday, December 12, 2007 1:45 PM
> To: Sandrine Boulanger
> Cc: dl-designreview
> Subject: Re: Directory and file name cleanup (ex. agile)
> 
> On Wed, 12 Dec 2007 13:16:38 -0800 "Sandrine Boulanger"
> <sandrine.boulanger@onstor.com> wrote:
> 
> >  
> > 
> > -----Original Message-----
> > From: Andy Sharp 
> > Sent: Wednesday, December 12, 2007 1:08 PM
> > To: dl-designreview
> > Subject: Directory and file name cleanup (ex. agile)
> > 
> >  
> > 
> > I have prepared a changelist that cleans up the use of the word
> > 'agile'
> > 
> > in file and directory names, and also removes /usr/local/agile from
> > our
> > 
> > software.  Here are the details:
> > 
> >  
> > 
> > 1. /usr/local/agile as a directory has not existed now for several
> > 
> > releases, so it's time to eradicate it.  Change all references to
> > that
> > 
> > directory to /onstor where the files really live.
> > 
> >  
> > 
> > 2. agile.conf is a dead file, remove references to it and remove it
> > 
> > from the build.
> > 
> >  
> > 
> > 3. /var/agile will be split into two different
> > directories: /var/onstor
> > 
> > for trace files and core dumps (although there is some claim core
> > dumps
> > 
> > go in /var/run anyway); 
> > 
> > [Sandrine] yes, all deamons cores go to /var/run (except nfxsh,
> > which cores wherever it's run from)
> 
> Fair enough.  No reason for that to change, and in addition I believe
> it is already the same for Cougar/Linux.
> 
> Eric Barnett mentioned BSD kernel crash dumps going into /var/crash.
> That will not be changed as I believe that is the standard place
> for that in the BSD operating system.  Linux/Cougar will not have
> kernel crash dump files.
> 
> > and /var/log/onstor for log files, including the
> > 
> > elog messages file, which will now be /var/log/onstor/messages.
> > This is
> > 
> > because /var/agile had become an arbitrary dumping ground without
> > any
> > 
> > paradigm or logically intuitive organization.
> > 
> > [Sandrine] where would the bsd|linux syslog messages go? Right now
> > we have /var/agile/messages* for elogs and /var/log/messages* for
> > bsd syslog
> 
> Every log file that was in /var/agile will be in heirarchacly (sp?)
> moved to /var/log/onstor, so elog will be in /var/log/onstor/messages
> 
> > Scope:
> > 
> >  
> > 
> > All work necessary to complete this should already be done and
> > viewable
> > 
> > in the changelist 26643.  There should be no extra changes necessary
> > by
> > 
> > anyone else, except of course documentation changes.  If you see
> > 
> > something is missing, please inform me.
> > 
> >  
> > 
> > Timeline:
> > 
> >  
> > 
> > This will go into the release following R98 as well as Cougar, so
> > 
> > the soonest it will hit customers is in about 3.5 months.  The idea
> > is
> > 
> > to get some general use testing of the change in Development, QA and
> > 
> > Support to fine tune any rough spots prior to release.  In addition
> > the
> > 
> > 3 months should and provide plenty of acclimation time.
> > 
> >  
> > 
> > Data points:
> > 
> >  
> > 
> > Upgrading.  This may require that we obsolete the previous upgrade
> > 
> > method (system upgrade), and all upgrades for S-W use the upgrade
> > 
> > script.
> > 
> >  
> > 
> > Implications for data warehouse?  Should be none, but ....
> > 
