X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C731DE.7FE48A28@onstor-exch02.onstor.net>; Sat, 6 Jan 2007 14:03:30 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C731DE.7FE48A28"
Content-class: urn:content-classes:message
Subject: Something that we might need to recommend to CS
Date: Sat, 6 Jan 2007 14:03:30 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0A90EC@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: Accx3CWf4mN5DYMHS8KsVs2ZNEpJIA==
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Jay Michlin" <jay.michlin@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_01C731DE.7FE48A28
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

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.)=20

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

Larry




------_=_NextPart_001_01C731DE.7FE48A28
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7650.28">
<TITLE>Something that we might need to recommend to CS</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<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>

</BODY>
</HTML>
------_=_NextPart_001_01C731DE.7FE48A28--
