X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C73222.21AFA43C@onstor-exch02.onstor.net>; Sat, 6 Jan 2007 22:07:37 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C73222.21AFA43C"
References: <BB375AF679D4A34E9CA8DFA650E2B04E0A90EC@onstor-exch02.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: Something that we might need to recommend to CS
Date: Sat, 6 Jan 2007 22:06:17 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E578AEE@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Something that we might need to recommend to CS
thread-index: Accx3CWf4mN5DYMHS8KsVs2ZNEpJIAARcv4F
From: "Jay Michlin" <jay.michlin@onstor.com>
To: "Larry Scheer" <larry.scheer@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C73222.21AFA43C
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This is consistent with the point I've been making about enlisting QA =
and CS as partners in whatever fix we recommend. I think that's in =
everyone's interest, ours, QA's, CS's, the company's, and the =
customers'.

________________________________

From: Larry Scheer
Sent: Sat 1/6/2007 2:03 PM
To: Jay Michlin; Tim Gardner; Andy Sharp
Subject: Something that we might need to recommend to CS



I just wanted to send this idea to you for further discussion while I =
was thinking about it.

I have been testing upgrade and various upgrade simulations. One of the =
things I am seeing regularly is ssc panics when memory gets low/maxed.

One of the things we might want to recommend to QA and Customer Service =
is to have users shut down pm even if they are upgrading the secondary =
flash. Low memory could be one of the reasons for the file corruption, =
but that is just speculation at this time. However, the real issue is, =
because the distribution is so big a system with any kind of SSC memory =
load could  run out of memory during an install.

I am running both a debug version of BSD and NFX code so I am using 152 =
Mbytes of ram every time I run an upgrade or a
simulation of upgrade. With every upgrade the system will start using =
swap and frequently the SSC will run out of memory and panic and this is =
when the only activity on the filer is idle ssc daemons and the upgrade =
program. (I have my virtual servers disabled on one filer all volumes =
off-line on the other.)

Let's talk some about what else can be done next week.

Larry






------_=_NextPart_001_01C73222.21AFA43C
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Something that we might need to recommend =
to CS</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText33229 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>This is =
consistent with the point I've been making about enlisting QA and CS as =
partners in whatever fix we recommend. I think that's in everyone's =
interest, ours, QA's, CS's, the company's, and the =
customers'.</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Larry Scheer<BR><B>Sent:</B> =
Sat 1/6/2007 2:03 PM<BR><B>To:</B> Jay Michlin; Tim Gardner; Andy =
Sharp<BR><B>Subject:</B> Something that we might need to recommend to =
CS<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>I just wanted to send this idea to you for further =
discussion while I was thinking about it.<BR><BR>I have been testing =
upgrade and various upgrade simulations. One of the things I am seeing =
regularly is ssc panics when memory gets low/maxed.<BR><BR>One of the =
things we might want to recommend to QA and Customer Service is to have =
users shut down pm even if they are upgrading the secondary flash. Low =
memory could be one of the reasons for the file corruption, but that is =
just speculation at this time. However, the real issue is, because the =
distribution is so big a system with any kind of SSC memory load =
could&nbsp; run out of memory during an install.<BR><BR>I am running =
both a debug version of BSD and NFX code so I am using 152 Mbytes of ram =
every time I run an upgrade or a<BR>simulation of upgrade. With every =
upgrade the system will start using swap and frequently the SSC will run =
out of memory and panic and this is when the only activity on the filer =
is idle ssc daemons and the upgrade program. (I have my virtual servers =
disabled on one filer all volumes off-line on the other.)<BR><BR>Let's =
talk some about what else can be done next =
week.<BR><BR>Larry<BR><BR><BR><BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C73222.21AFA43C--
