X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C78842.B3790CFC@onstor-exch02.onstor.net>; Thu, 26 Apr 2007 13:37:26 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-class: urn:content-classes:message
Content-Transfer-Encoding: quoted-printable
Subject: RE: Defect  TED00018693 "system reboot -s" does not shut down filer
Date: Thu, 26 Apr 2007 13:37:26 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E036D388F@onstor-exch02.onstor.net>
In-Reply-To: <20070426133151.76a9c9b4@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Defect  TED00018693 "system reboot -s" does not shut down filer
Thread-Index: AceIQewjiCby/K+7S42I20D7jhPANwAAKccw
References: <ONSTOR-EXCH017n0swX00000de9@onstor-exch01.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E036D386D@onstor-exch02.onstor.net> <20070426133151.76a9c9b4@ripper.onstor.net>
From: "Brian DeForest" <brian.deforest@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

If you set it to not reproducible, it will be in their "court" to
reproduce it or close it.  =20

-----Original Message-----
From: Andy Sharp=20
Sent: Thursday, April 26, 2007 1:32 PM
To: Brian DeForest
Subject: Re: Defect TED00018693 "system reboot -s" does not shut down
filer

I wanted to give QA a chance to contradict me if they cared to.
Like if they can reproduce it frequently or something.

a


On Thu, 26 Apr 2007 13:19:41 -0700 "Brian DeForest"
<brian.deforest@onstor.com> wrote:

> Should be resolved as not reproducible.
>=20
> -----Original Message-----
> From: andy.sharp@onstor.com [mailto:andy.sharp@onstor.com]=20
> Sent: Wednesday, April 25, 2007 7:59 PM
> To: Andy Sharp; Brian DeForest; May Ma
> Cc: May Ma
> Subject: Defect TED00018693 "system reboot -s" does not shut down
> filer
>=20
> Headline: "system reboot -s" does not shut down filer
> id: TED00018693
> Note_Entry: "Not sure how you can tell /var is full."
>=20
> I'm psychic? ~:^)
>=20
> That is the only thing (that I can find) in this bug that even looks
> error like, so that is
> how I called it.  I can't reproduce this, and I'm not hearing that it
> is generally reproduceable.
>=20
> No doubt whatsoever that it is annoying.  And ugly.  But based on the
> fact that I can't reproduce
> it and therefore can't think of anything I could do to fix it, it's at
> best a P2.  If it starts to
> happen consistently, or it already does happen consistently, that
> would be a different matter.
>=20
> My guess is that a full /var caused some program that is executed
> during the shutdown process
> to bomb out, stopping the shutdown after it went most of the way
> already.  This is a somewhat
> wild guess, and I can't find anything in a quick code inspection to
> back it up, or fix.
>=20
> State: Assigned
> history: 33698546	Apr 18 2007  4:37PM	maym
> Submit	no_value Opened
> 33698559	Apr 18 2007  5:39PM	maym	Modify
> Opened	Opened 33698584	Apr 18 2007  6:48PM
> rajk	Review	Opened	Reviewed 33698601	Apr
> 18 2007 11:33PM	briand	Assign	Reviewed Assigned
> 33699265	Apr 20 2007 11:32AM	andrews
> Modify	Assigned Assigned
> 33699372	Apr 20 2007 11:31PM	briand
> Back_to_triage	Assigned Re-opened
> 33700088	Apr 25 2007  7:38PM	sandrineb	Assign
> Re-opened	Assigned
> 33700092	04/25/2007 19:58:50 PM	andrews
> Modify	Assigned Assigned
>=20
