X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C88C5E.781699B0@onstor-exch02.onstor.net>; Sat, 22 Mar 2008 13:51:14 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: sub13 issues
Date: Sat, 22 Mar 2008 13:51:14 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08FC3939@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E08FC3937@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: sub13 issues
Thread-Index: AciL5vhUs+/0FYfqQtu0SHCR0dTVzwAU5CZCAAins4AAAFFO8A==
References: <BB375AF679D4A34E9CA8DFA650E2B04E03B5B70E@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E03B5B712@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E08FC3937@onstor-exch02.onstor.net>
From: "Jonathan Goldick" <jonathan.goldick@onstor.com>
To: "Vikas Saini" <vikas.saini@onstor.com>,
	"dl-QA" <dl-qa@onstor.com>,
	"dl-hcl-qa" <dl-hcl-qa@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>

Nevermind, I have generated this on my box.  Will look into it.

-----Original Message-----
From: Jonathan Goldick=20
Sent: Saturday, March 22, 2008 1:44 PM
To: Vikas Saini; dl-QA; dl-hcl-qa; dl-Cougar
Subject: RE: sub13 issues

For cases where ops drops to 0, check 'fscmd errstats' so we can see if
we are hitting some resource shortage.


-----Original Message-----
From: Vikas Saini=20
Sent: Saturday, March 22, 2008 9:43 AM
To: Vikas Saini; dl-QA; dl-hcl-qa; dl-Cougar
Subject: sub13 issues
Importance: High

Hi All,
   so far we have seen following issues on sub13

1) An issue where "vol create" failed with timeout error message. elogs
displayed lun label read problem. defect 22921 and 22923

2) OPS dropping to zero problem resurfaced on John K system(g6r10,g5r10)
and g11r204(system is still in that state incase someone wants to have a
look)

3) Manny also saw an issue where OPS are dropping to zero for a second
or two.(on g10r204).

4) TXRX crash causing FP crash problem is still happening. this needs to
be fixed ASAP. defect 22448

5) A couple of issues with system upgrade. defect 22919 and a few
others.

Apart from these, 22821 where John K's cluster is still messed and not
able ping each other. we need some resolution on that.
=20

Thanks
Vikas





