X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7A72D.85DCA68F@onstor-exch02.onstor.net>; Mon, 4 Jun 2007 21:53:56 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7A72D.85DCA68F"
Content-class: urn:content-classes:message
Subject: RE: Delorean's status (6/4)
Date: Mon, 4 Jun 2007 21:53:56 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F1490E@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Delorean's status (6/4)
Thread-Index: AcenGC7e71WOi0fAQceS4GlNw7i+8QAD3PcQAAElmL0AACX49w==
References: <BB375AF679D4A34E9CA8DFA650E2B04E030B6044@onstor-exch02.onstor.net>
From: "Raj Kumar" <raj.kumar@onstor.com>
To: "Sandeep Randhawa" <sandeep.randhawa@onstor.com>,
	"Sandrine Boulanger" <sandrine.boulanger@onstor.com>,
	"dl-Delorean" <dl-Delorean@onstor.com>

This is a multi-part message in MIME format.

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

Snapshot that was reverted to, was taken when the volume size was 32 TB.
=20
Volume size was 33 TB when we reverted today.
=20
Revert time: 23 minutes 47 seconds
=20
************ ELOG ************
Jun  4 18:02:45 eng71 : 1:3:efs:WARNING: 394086: sourcevol snap revert =
1: begin
Jun  4 18:05:01 eng71 : 0:0:nfxsh:NOTICE: cmd[2]: vol show : status[0]
Jun  4 18:08:24 eng71 : 1:2:efs:INFO: 394087: sourcevol snap resume: =
recal refbyte snapcounts for 1
Jun  4 18:11:02 eng71 : 0:0:nfxsh:NOTICE: cmd[0]: -> support.sh (root): =
WARNING: Could not resolve uplo
ad server host name 'phd.onstor.com', trying IP addr '66.201.51.71'. : =
status[2]
Jun  4 18:26:32 eng71 : 1:3:efs:WARNING: 394088: sourcevol snap revert =
1: end


________________________________

From: Sandeep Randhawa
Sent: Mon 6/4/2007 9:44 PM
To: Sandrine Boulanger; dl-Delorean
Subject: Re: Delorean's status (6/4)



Just curious if we know how long did it take for the snap revert?
We get asked this qu in the field.


--------------------------
Sandeep
ONStor
408-476-3059
Sent via BBerry!


-----Original Message-----
From: Sandrine Boulanger
To: dl-Delorean
Sent: Mon Jun 04 21:28:59 2007
Subject: Delorean's status (6/4)

1. Defects:

Closed: 28

Opened: 9

Backlog: 14 (among which 4 in patches, 2 for sub#22)



2. Issues / Concerns:

1. S-Soak: After upgrading to Sub #21, we ran into the spm issue (SCSI =
discovered all LUNS but spm didnt) again. Killing ssc daemons and using =
scsi discover did not solve the problem, but it cleared up after 2 nodes =
were rebooted. We should try another upgrade tomorrow to try to =
reproduce since it usually shows up right after an upgrade.

2. FS corruption on 33 TB volume: We had a corruption on this volume =
last week, EEK'd and reverted to a good snapshot today and continuing =
the tests to reach 40 TB limit



3. Tasks:

(\\10.0.0.222\qe\Projects\Delorean\TestPlans\SubmittalPlans\Submittal_21_=
FCS_Tasks.htm =
<file:///\\10.0.0.222\qe\Projects\Delorean\TestPlans\SubmittalPlans\Submi=
ttal_21_FCS_Tasks.htm =
<file://10.0.0.222/qe/Projects/Delorean/TestPlans/SubmittalPlans/Submitta=
l_21_FCS_Tasks.htm> > )

All tasks are in progress. Status on tasks that are completed or closed =
to complete:



CIFS regressions - 80 % completed

Computer Management in Vista - Done

TTE: tests running with vsvr moves, no new defects

NCM (IE, FireFox in Windows, Linux) - Done

40 TB volume - Resumes tests, currently at 32 TB

CIFS shares clusterDB upgrade tests status:

            250: Passed

            500: Failed within the first 5 minutes, then succeeded an =
hour later

            1000: Failed, does not work at all, even after waiting an =
hour








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

<HTML dir=3Dltr><HEAD><TITLE>Re: Delorean's status (6/4)</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=3DidOWAReplyText57695 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Snapshot that =
was reverted to, was taken when the volume size was 32 TB.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Volume size =
was 33 TB when we reverted today.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Revert time: 23 minutes 47 =
seconds</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>************ ELOG =
************</FONT></DIV>=0A=
<DIV dir=3Dltr>Jun&nbsp; 4 18:02:45 eng71 : 1:3:efs:WARNING: 394086: =
sourcevol snap revert 1: <STRONG>begin</STRONG><BR>Jun&nbsp; 4 18:05:01 =
eng71 : 0:0:nfxsh:NOTICE: cmd[2]: vol show : status[0]<BR>Jun&nbsp; 4 =
18:08:24 eng71 : 1:2:efs:INFO: 394087: sourcevol snap resume: recal =
refbyte snapcounts for 1<BR>Jun&nbsp; 4 18:11:02 eng71 : =
0:0:nfxsh:NOTICE: cmd[0]: -&gt; support.sh (root): WARNING: Could not =
resolve uplo<BR>ad server host name 'phd.onstor.com', trying IP addr =
'66.201.51.71'. : status[2]<BR>Jun&nbsp; 4 18:26:32 eng71 : =
1:3:efs:WARNING: 394088: sourcevol snap revert 1: =
<STRONG>end</STRONG><BR></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Sandeep =
Randhawa<BR><B>Sent:</B> Mon 6/4/2007 9:44 PM<BR><B>To:</B> Sandrine =
Boulanger; dl-Delorean<BR><B>Subject:</B> Re: Delorean's status =
(6/4)<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Just curious if we know how long did it take for the =
snap revert?<BR>We get asked this qu in the =
field.<BR><BR><BR>--------------------------<BR>Sandeep<BR>ONStor<BR>408-=
476-3059<BR>Sent via BBerry!<BR><BR><BR>-----Original =
Message-----<BR>From: Sandrine Boulanger<BR>To: dl-Delorean<BR>Sent: Mon =
Jun 04 21:28:59 2007<BR>Subject: Delorean's status (6/4)<BR><BR>1. =
Defects:<BR><BR>Closed: 28<BR><BR>Opened: 9<BR><BR>Backlog: 14 (among =
which 4 in patches, 2 for sub#22)<BR><BR><BR><BR>2. Issues / =
Concerns:<BR><BR>1. S-Soak: After upgrading to Sub #21, we ran into the =
spm issue (SCSI discovered all LUNS but spm didnt) again. Killing ssc =
daemons and using scsi discover did not solve the problem, but it =
cleared up after 2 nodes were rebooted. We should try another upgrade =
tomorrow to try to reproduce since it usually shows up right after an =
upgrade.<BR><BR>2. FS corruption on 33 TB volume: We had a corruption on =
this volume last week, EEK'd and reverted to a good snapshot today and =
continuing the tests to reach 40 TB limit<BR><BR><BR><BR>3. =
Tasks:<BR><BR>(\\10.0.0.222\qe\Projects\Delorean\TestPlans\SubmittalPlans=
\Submittal_21_FCS_Tasks.htm &lt;<A =
href=3D"file://10.0.0.222/qe/Projects/Delorean/TestPlans/SubmittalPlans/S=
ubmittal_21_FCS_Tasks.htm">file:///\\10.0.0.222\qe\Projects\Delorean\Test=
Plans\SubmittalPlans\Submittal_21_FCS_Tasks.htm</A>&gt; )<BR><BR>All =
tasks are in progress. Status on tasks that are completed or closed to =
complete:<BR><BR><BR><BR>CIFS regressions - 80 % =
completed<BR><BR>Computer Management in Vista - Done<BR><BR>TTE: tests =
running with vsvr moves, no new defects<BR><BR>NCM (IE, FireFox in =
Windows, Linux) - Done<BR><BR>40 TB volume - Resumes tests, currently at =
32 TB<BR><BR>CIFS shares clusterDB upgrade tests =
status:<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; 250: =
Passed<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; 500: Failed within the first 5 minutes, then succeeded an hour =
later<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; 1000: Failed, does not work at all, even after waiting an =
hour<BR><BR><BR><BR><BR><BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C7A72D.85DCA68F--
