X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8B5DF.84B83538@onstor-exch02.onstor.net>; Wed, 14 May 2008 09:28:18 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B5DF.84B83538"
References: <20080514002156.2d050856@ripper.onstor.net> <20080514005858.1eb9d489@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: sub#22 prolly needs respin
Date: Wed, 14 May 2008 09:28:18 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E042F0186@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: sub#22 prolly needs respin
Thread-Index: Aci1mF5ez0POJSCaSBGpk6Z7MazTggAReH0S
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Tim Gardner" <tim.gardner@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B5DF.84B83538
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Andy,
   Let's talk about what you were seeing when I get in. The sub22 beta =
build has dmalloc enabled and I saw a couple of crashes, one immediately =
on reboot the other was with cluster controller when I tried to run a =
snapshot. When you say messed up what is the nature of the messyness? =
Check the cores in /var/run and see if they are all due to dmalloc.

After a reboot I didn't see the first crash. Because of this behavior I =
wonder if Max's change really was the fix? When you did your own =
personal build dmalloc would have been turned off. Perhaps it is dmalloc =
that is ruining your buzz.

I will be respinning the cougar builds with dmalloc turned off by =
commenting out the DMALLOC variable in /etc/defaults/onstor.

Larry



-----Original Message-----
From: Andy Sharp
Sent: Wed 5/14/2008 12:58 AM
To: Andy Sharp
Cc: Larry Scheer; Tim Gardner
Subject: Re: sub#22 prolly needs respin
=20
On Wed, 14 May 2008 00:21:56 -0700 Andrew Sharp <andy.sharp@onstor.com>
wrote:

> Just an FYI,
>=20
> I'm trying to run sub#22 beta equivalent on my cougar, and it's quite
> a mess.  I think we need to integrate max's change # 29211 into beta
> branch.  I'm going to try that now to see if it works.


Yup, that fixed it.


------_=_NextPart_001_01C8B5DF.84B83538
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.7653.38">
<TITLE>RE: sub#22 prolly needs respin</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Andy,<BR>
&nbsp;&nbsp; Let's talk about what you were seeing when I get in. The =
sub22 beta build has dmalloc enabled and I saw a couple of crashes, one =
immediately on reboot the other was with cluster controller when I tried =
to run a snapshot. When you say messed up what is the nature of the =
messyness? Check the cores in /var/run and see if they are all due to =
dmalloc.<BR>
<BR>
After a reboot I didn't see the first crash. Because of this behavior I =
wonder if Max's change really was the fix? When you did your own =
personal build dmalloc would have been turned off. Perhaps it is dmalloc =
that is ruining your buzz.<BR>
<BR>
I will be respinning the cougar builds with dmalloc turned off by =
commenting out the DMALLOC variable in /etc/defaults/onstor.<BR>
<BR>
Larry<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Andy Sharp<BR>
Sent: Wed 5/14/2008 12:58 AM<BR>
To: Andy Sharp<BR>
Cc: Larry Scheer; Tim Gardner<BR>
Subject: Re: sub#22 prolly needs respin<BR>
<BR>
On Wed, 14 May 2008 00:21:56 -0700 Andrew Sharp =
&lt;andy.sharp@onstor.com&gt;<BR>
wrote:<BR>
<BR>
&gt; Just an FYI,<BR>
&gt;<BR>
&gt; I'm trying to run sub#22 beta equivalent on my cougar, and it's =
quite<BR>
&gt; a mess.&nbsp; I think we need to integrate max's change # 29211 =
into beta<BR>
&gt; branch.&nbsp; I'm going to try that now to see if it works.<BR>
<BR>
<BR>
Yup, that fixed it.<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C8B5DF.84B83538--
