X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C78B9C.E78B164C@onstor-exch02.onstor.net>; Mon, 30 Apr 2007 20:00:41 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C78B9C.E78B164C"
Content-class: urn:content-classes:message
Subject: RE: Don't sync up with current Delorean code base
Date: Mon, 30 Apr 2007 19:56:58 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F14612@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Don't sync up with current Delorean code base
Thread-Index: AceLmzffix+uD4aTTp+mB3P4Al115AAASo9y
References: <BB375AF679D4A34E9CA8DFA650E2B04E0F5634@onstor-exch02.onstor.net>
From: "Raj Kumar" <raj.kumar@onstor.com>
To: "James Kahn" <james.kahn@onstor.com>,
	"dl-Delorean" <dl-Delorean@onstor.com>

This is a multi-part message in MIME format.

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

This sounds like the issue that took the S-Soak down:
=20
id: TED00018824
Headline: Devices are seen at the SCSI layer but not the evm layer


________________________________

From: James Kahn
Sent: Mon 4/30/2007 7:48 PM
To: dl-Delorean
Subject: Don't sync up with current Delorean code base



I sych'ed up with current Delorean code base and I get the bsd panic =
alloc crash

With my filer sitting idle.

There appears to be no communication between the FC and SPM.  FC is

Seeing luns; but SPM does not report having any.

Watch out!

-Jim


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

<HTML dir=3Dltr><HEAD><TITLE>Don't sync up with current Delorean code =
base</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2800.1555" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText53435 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>This sounds =
like the issue that took the S-Soak down:</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><SPAN style=3D"FONT-SIZE: 10pt">id: =
TED00018824<BR>Headline: Devices are seen at the SCSI layer but not the =
evm layer<BR></SPAN></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> James Kahn<BR><B>Sent:</B> Mon =
4/30/2007 7:48 PM<BR><B>To:</B> dl-Delorean<BR><B>Subject:</B> Don't =
sync up with current Delorean code base<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial size=3D2>I =
sych</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT =
face=3DArial size=3D2>&#8217;</FONT></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us><FONT face=3DArial size=3D2>ed up =
with current Delorean code base and I get</FONT></SPAN><SPAN =
lang=3Den-us></SPAN><SPAN lang=3Den-us> <FONT face=3DArial size=3D2>the =
bsd panic alloc crash</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us></SPAN></P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial size=3D2>With my =
filer sitting idle.</FONT></SPAN></P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial size=3D2>There =
appears to be no communication between the FC and SPM.&nbsp; FC =
is</FONT></SPAN></P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Seeing =
luns; but SPM does not report having any.</FONT></SPAN></P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Watch =
out!</FONT></SPAN></P>=0A=
<P align=3Dleft><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>-Jim</FONT></SPAN><SPAN lang=3Den-us></SPAN><SPAN =
lang=3Den-us></SPAN></P></DIV></BODY></HTML>
------_=_NextPart_001_01C78B9C.E78B164C--
