X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7A8B7.35B053E7@onstor-exch02.onstor.net>; Wed, 6 Jun 2007 20:52:03 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7A8B7.35B053E7"
Content-class: urn:content-classes:message
Subject: DeLorean Submittal 22 Ready for Acceptance Testing - Was: RE: Please include this in sub #22
Date: Wed, 6 Jun 2007 20:52:03 -0700
Message-ID: <6041AEBD8A3E264785ABDA2F60B52DB45FCF0A10@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E040F0338@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: DeLorean Submittal 22 Ready for Acceptance Testing - Was: RE: Please include this in sub #22
Thread-Index: Acen5nuoEYeuTUAkRBCqKqEjQ2vuAAADz/5wABK8ZnQABh3D0AABv9UqAABRq9AAADdViQAAF/LQAAAi/FYAAyY1zAAARo9AAADlqJAAA8VE0A==
X-Priority: 1
Priority: Urgent
Importance: high
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Brian DeForest" <brian.deforest@onstor.com>,
	"Raj Kumar" <raj.kumar@onstor.com>
Cc: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>,
	"Ken Renshaw" <ken.renshaw@onstor.com>,
	"Paul Hammer" <paul.hammer@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

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

Here is submittal 22 for DeLorean 3.0.0.0 including the cw_install =
standalone install script that facilitates one-step upgrades from 1.3.x =
and 2.x to 3.0.

The changes since sub21 are these three:

Change 24169 by andys@ripper on 2007/06/04 09:59:34

      Nice down "tar -zx" process to increase responsiveness of =
managment processor
      during upgrades, hopefully putting an end to silent reboots during =
upgrades.

      TED00018378 - "Cheetah Upgrade of 2nd flash from =
1.3.3.15->Delorean#11: Silent reboot"=20

Change 24171 by andys@ripper on 2007/06/04 13:56:21

      First checkin of standalone Install script and related changes.
      If we've all been living clean lives, the last checkin.

      TED00018276 - "Upgrade from 2221 to 2.3 on secondary flash fails =
to copy files"

Change 24188 by jobia@jobi:jobi on 2007/06/05 12:22:27

         Fix a watchdog timeout in fs_buddy_bnum_in_free_region().

         Defect TED00019400.

EverON images ( prior sub21 images have been renamed with a '-sub21' =
suffix ):

Cheetah optimized:

ftp://upgrade@10.2.0.2/home/upgrade/EverON-3.0.0.0.tar.gz

Bobcat optimized:

ftp://upgrade@10.2.0.2/home/upgrade/EverON-3.0.0.0BC.tar.gz

Cheetah debug:=20

ftp://upgrade@10.2.0.2/home/upgrade/EverON-3.0.0.0DBG.tar.gz

Bobcat debug:

ftp://upgrade@10.2.0.2/home/upgrade/EverON-3.0.0.0BCDBG.tar.gz

IMPORTANT NOTE: To test the cw_install.sh script you must use the =
version corresponding to
the EverON variant you are using., i.e. cheetah debug, bobcat opt, etc. =
At the moment, the
cw_install.sh script is built into the tarball it's supposed to support, =
so there
must be workflows designed and tested to extract the file, etc. for the =
customer. Right now their are
four versions of the file cw_install.sh that have different contents and =
must be managed separately.

In lieu of that, internally I am posting all versions of the script on =
both the FTP server and under
Build-Trees for build distribution.

Bobcat optimized:

ftp://upgrade@10.2.0.2/home/upgrade/DeLorean/sub22/bc-opt/cw_install.sh
/n/Build-Trees/R3.0.0.0/R3.0.0.0-060607/nfx-tree/Build/bc/opt/Release/cw_=
install.sh

Cheetah optimized:

ftp://upgrade@10.2.0.2/home/upgrade/DeLorean/sub22/ch-opt/cw_install.sh
/n/Build-Trees/R3.0.0.0/R3.0.0.0-060607/nfx-tree/Build/ch/opt/Release/cw_=
install.sh

Bobcat debug:

ftp://upgrade@10.2.0.2/home/upgrade/DeLorean/sub22/bc-dbg/cw_install.sh
/n/Build-Trees/R3.0.0.0/R3.0.0.0-060607/nfx-tree/Build/bc/dbg/Release/cw_=
install.sh

Cheetah debug:

ftp://upgrade@10.2.0.2/home/upgrade/DeLorean/sub22/ch-dbg/cw_install.sh
/n/Build-Trees/R3.0.0.0/R3.0.0.0-060607/nfx-tree/Build/ch-dbg/Release/cw_=
install.sh

Source tree:

/n/Build-Trees/R3.0.0.0/R3.0.0.0-060607/nfx-tree

Perforce sync info:

//depot/FB-DELOREAN/...@24204 modulo one nfx-tree/Makefile change for =
the 'make release' target support for cw_install

Thanks,

-Ken

=20

=20

________________________________

From: Brian DeForest=20
Sent: Wednesday, June 06, 2007 1:00 PM
To: Ken Renshaw; Raj Kumar
Cc: Sandrine Boulanger
Subject: RE: Please include this in sub #22

=20

We need 2 things for sub22:

=20

1.	the P4 changelist #24171 includes a changed openbsd file.   Since it =
doesn't need to be compiled (/etc/rc) I suggest simply patching this =
into the latest BSD build rather than do a full BSD build, if Ken agrees =
after reviewing the changelist.
2.	merge the fix for CQ #19400 from Zonda to Delorean & have Jobi review =
the merge

=20

________________________________

From: Ken Renshaw=20
Sent: Wednesday, June 06, 2007 12:30 PM
To: Raj Kumar; Brian DeForest
Cc: Sandrine Boulanger
Subject: RE: Please include this in sub #22

=20

I need to finish a build for Ed first, but I can build sub22 later this =
afternoon.

=20

-Ken

=20

________________________________

From: Raj Kumar=20
Sent: Wednesday, June 06, 2007 12:21 PM
To: Raj Kumar; Brian DeForest
Cc: Sandrine Boulanger; Ken Renshaw
Subject: RE: Please include this in sub #22

=20

When should we start the build?

=20

________________________________

From: Raj Kumar
Sent: Wed 6/6/2007 10:50 AM
To: Brian DeForest
Cc: Sandrine Boulanger
Subject: RE: Please include this in sub #22

yeah thats my suggestion.

=20

________________________________

From: Brian DeForest
Sent: Wed 6/6/2007 10:48 AM
To: Raj Kumar
Cc: Sandrine Boulanger
Subject: RE: Please include this in sub #22

I'll confirm w/ Andy that this is ready.    So that would be 2 builds, =
sub22 this week and sub23 next week w/ more MF fixes.

=20

________________________________

From: Raj Kumar=20
Sent: Wednesday, June 06, 2007 10:44 AM
To: Brian DeForest
Cc: Sandrine Boulanger
Subject: RE: Please include this in sub #22

=20

I like to complete 40 TB by 6/15. So we need a build ASAP since it takes =
time to create data.

=20

Also Paul has asked us to start with CW-install tests, so we need to =
build.

=20

________________________________

From: Brian DeForest
Sent: Wed 6/6/2007 10:39 AM
To: Raj Kumar
Cc: Sandrine Boulanger
Subject: RE: Please include this in sub #22

But is the 40TB testing happening this week or could this wait for the =
next build, likely early next week?

=20

I'd prefer to do one more build, if possible, but we may need 2 if you =
need this fix sooner.

=20

________________________________

From: Raj Kumar=20
Sent: Wednesday, June 06, 2007 10:29 AM
To: Brian DeForest; Jobi Ariyamannil
Cc: May Ma; Sandrine Boulanger
Subject: RE: Please include this in sub #22

=20

I think completing the 40TB test should give us enough test coverage for =
this change. We should take this

=20

________________________________

From: Brian DeForest
Sent: Wed 6/6/2007 9:40 AM
To: Raj Kumar; Jobi Ariyamannil
Cc: May Ma; Sandrine Boulanger
Subject: RE: Please include this in sub #22

I had been considering this one, and Sandrine and I had discussed it as =
a possibility.   On the other hand, I also want to stabilize the code =
base and minimize the checkins.

=20

What is the test impact?

=20

________________________________

From: Raj Kumar=20
Sent: Wednesday, June 06, 2007 6:44 AM
To: Jobi Ariyamannil
Cc: May Ma; Sandrine Boulanger; Brian DeForest; Ken Renshaw
Subject: Please include this in sub #22

=20

Hi,

=20

Like to pull this into sub #22.

=20

Thanks.

=20

________________________________

From: Jobi Ariyamannil
Sent: Tue 6/5/2007 9:51 PM
To: Raj Kumar
Cc: May Ma; Sandrine Boulanger
Subject: RE: Defect TED00019400 FP watchdog timeout on almost full =
filesystem (33TB) in fs_buddy_bnum_in_free_region()

Is your filesystem becoming almost full frequently?

If your intention is to populate 40TB, you may temporarily disable the =
snapshots.

Also if this is an absolute showstopper for you, we may port the fix to =
delorean.

Regards,
Jobi

-----Original Message-----
From: raj.kumar@onstor.com [mailto:raj.kumar@onstor.com]
Sent: Tuesday, June 05, 2007 7:58 PM
To: Jobi Ariyamannil; Jobi Ariyamannil; May Ma
Cc: May Ma; Sandrine Boulanger
Subject: Defect TED00019400 FP watchdog timeout on almost full =
filesystem (33TB) in fs_buddy_bnum_in_free_region()

Headline: FP watchdog timeout on almost full filesystem (33TB)  in =
fs_buddy_bnum_in_free_region()
id: TED00019400
Note_Entry: Jobi,

ENG7 (40 TB setup) is continously crashing due to FS issue. Here is the =
trace, is this trace same issue as this defect?

#0  0x8304ae50 in fs_buddy_bnum_in_free_region (context=3D0x1ae3e000,
    bnum=3D4266274790, len=3D1, isFull=3D0xffffffff85621118) at =
fs-buddy.c:2235
#1  0x8304a550 in fs_buddyFindExtent (context=3D0x1ae3e000, len=3D1, =
target=3D
      {block =3D 4266274790}, isFirstFileExtent=3D0, noSnap=3Dfalse)
    at fs-inlines.c:99
#2  0x83038744 in fs_allocateBuddyExtent (context=3D0x101ae3e000, =
requested=3D1,
    target=3D{block =3D 4266274790}, anySize=3D0, noSnap=3D0, =
isFirstFileExtent=3D0)
    at fs-alloc.c:856
#3  0x83035d94 in fs_allocateExtent (context=3D0x101ae3e000, =
inode=3D0x1025e442d0,
    page=3D14069157, len32=3D1, anySize=3D0, contigAlloc=3D0) at =
fs-alloc.c:1280
#4  0x83057998 in fs_bufAllocDoBufs (context=3D0x101ae3e000, =
inode=3D0x1025e442d0,
    numInBufs=3D1, bufs=3D0xffffffff856217d8, commitInode=3Dtrue, =
contigAlloc=3Dfalse)
    at fs-buf.c:6870
#5  0x830e40a0 in fs_writeThread (context=3D0x101ae3e000) at =
fs-nfs.c:4856
#6  0x83067fa4 in fs_threadBegin (handle=3D10223717, arg=3D0x101ae3e000)
    at fs-context.c:2781
#7  0x8301d2a8 in esmthread_start (handle=3D448921600, nextState=3D0, =
event=3D
          {event =3D 0, p1 =3D {u =3D {dw =3D 18446744071612824480, w =
=3D 2198240160, p =3D                                               =
0xffffffff83067ba0}}, p2 =3D {u =3D {dw =3D 18446744072094767276, w =3D =
2680182956, p =3D                                               =
0xffffffff9fc058ac}}}, userInfo=3D0x101ae3e000) at thread-api.c:311
#8  0x8301a5c4 in esm_threadMain (arg=3D0x1000a33f20) at esm-nfx.c:224
#9  0x8301a568 in esm_threadMain (arg=3D0x1000a33f20) at esm-nfx.c:195
State: Assigned
history: 33706857       May 31 2007  3:31PM     maym    Submit  no_value =
       Opened
33706861        May 31 2007  3:51PM     jobia   Need_more_info  Opened  =
More_Info
33706874        May 31 2007  5:10PM     jobia   Back_to_triage  =
More_Info       Re-opened
33706892        May 31 2007 10:38PM     jobia   Modify  Re-opened       =
Re-opened
33707130        Jun  4 2007  2:13PM     jobia   Modify  Re-opened       =
Re-opened
33707215        Jun  4 2007  9:37PM     sandrineb       Review  =
Re-opened       Reviewed
33707284        Jun  5 2007  1:20PM     jobia   Assign  Reviewed        =
Assigned
33707347        Jun  5 2007  7:48PM     sandrineb       Modify  Assigned =
       Assigned
33707348        06/05/2007 19:57:53 PM  rajk    Modify  Assigned        =
Assigned



------_=_NextPart_001_01C7A8B7.35B053E7
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.7652.24">
<TITLE>DeLorean Submittal 22 Ready for Acceptance Testing - Was: RE: =
Please include this in sub #22</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Here is submittal 22 for DeLorean 3.0.0.0 including =
the cw_install standalone install script that facilitates one-step =
upgrades from 1.3.x and 2.x to 3.0.<BR>
<BR>
The changes since sub21 are these three:<BR>
<BR>
Change 24169 by andys@ripper on 2007/06/04 09:59:34<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Nice down &quot;tar -zx&quot; process to =
increase responsiveness of managment processor<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; during upgrades, hopefully putting an end =
to silent reboots during upgrades.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TED00018378 - &quot;Cheetah Upgrade of =
2nd flash from 1.3.3.15-&gt;Delorean#11: Silent reboot&quot;<BR>
<BR>
Change 24171 by andys@ripper on 2007/06/04 13:56:21<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; First checkin of standalone Install =
script and related changes.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If we've all been living clean lives, the =
last checkin.<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TED00018276 - &quot;Upgrade from 2221 to =
2.3 on secondary flash fails to copy files&quot;<BR>
<BR>
Change 24188 by jobia@jobi:jobi on 2007/06/05 12:22:27<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fix a watchdog timeout =
in fs_buddy_bnum_in_free_region().<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Defect TED00019400.<BR>
<BR>
EverON images ( prior sub21 images have been renamed with a '-sub21' =
suffix ):<BR>
<BR>
Cheetah optimized:<BR>
<BR>
<A =
HREF=3D"ftp://upgrade@10.2.0.2/home/upgrade/EverON-3.0.0.0.tar.gz">ftp://=
upgrade@10.2.0.2/home/upgrade/EverON-3.0.0.0.tar.gz</A><BR>
<BR>
Bobcat optimized:<BR>
<BR>
<A =
HREF=3D"ftp://upgrade@10.2.0.2/home/upgrade/EverON-3.0.0.0BC.tar.gz">ftp:=
//upgrade@10.2.0.2/home/upgrade/EverON-3.0.0.0BC.tar.gz</A><BR>
<BR>
Cheetah debug:<BR>
<BR>
<A =
HREF=3D"ftp://upgrade@10.2.0.2/home/upgrade/EverON-3.0.0.0DBG.tar.gz">ftp=
://upgrade@10.2.0.2/home/upgrade/EverON-3.0.0.0DBG.tar.gz</A><BR>
<BR>
Bobcat debug:<BR>
<BR>
<A =
HREF=3D"ftp://upgrade@10.2.0.2/home/upgrade/EverON-3.0.0.0BCDBG.tar.gz">f=
tp://upgrade@10.2.0.2/home/upgrade/EverON-3.0.0.0BCDBG.tar.gz</A><BR>
<BR>
IMPORTANT NOTE: To test the cw_install.sh script you must use the =
version corresponding to<BR>
the EverON variant you are using., i.e. cheetah debug, bobcat opt, etc. =
At the moment, the<BR>
cw_install.sh script is built into the tarball it's supposed to support, =
so there<BR>
must be workflows designed and tested to extract the file, etc. for the =
customer. Right now their are<BR>
four versions of the file cw_install.sh that have different contents and =
must be managed separately.<BR>
<BR>
In lieu of that, internally I am posting all versions of the script on =
both the FTP server and under<BR>
Build-Trees for build distribution.<BR>
<BR>
Bobcat optimized:<BR>
<BR>
<A =
HREF=3D"ftp://upgrade@10.2.0.2/home/upgrade/DeLorean/sub22/bc-opt/cw_inst=
all.sh">ftp://upgrade@10.2.0.2/home/upgrade/DeLorean/sub22/bc-opt/cw_inst=
all.sh</A><BR>
/n/Build-Trees/R3.0.0.0/R3.0.0.0-060607/nfx-tree/Build/bc/opt/Release/cw_=
install.sh<BR>
<BR>
Cheetah optimized:<BR>
<BR>
<A =
HREF=3D"ftp://upgrade@10.2.0.2/home/upgrade/DeLorean/sub22/ch-opt/cw_inst=
all.sh">ftp://upgrade@10.2.0.2/home/upgrade/DeLorean/sub22/ch-opt/cw_inst=
all.sh</A><BR>
/n/Build-Trees/R3.0.0.0/R3.0.0.0-060607/nfx-tree/Build/ch/opt/Release/cw_=
install.sh<BR>
<BR>
Bobcat debug:<BR>
<BR>
<A =
HREF=3D"ftp://upgrade@10.2.0.2/home/upgrade/DeLorean/sub22/bc-dbg/cw_inst=
all.sh">ftp://upgrade@10.2.0.2/home/upgrade/DeLorean/sub22/bc-dbg/cw_inst=
all.sh</A><BR>
/n/Build-Trees/R3.0.0.0/R3.0.0.0-060607/nfx-tree/Build/bc/dbg/Release/cw_=
install.sh<BR>
<BR>
Cheetah debug:<BR>
<BR>
<A =
HREF=3D"ftp://upgrade@10.2.0.2/home/upgrade/DeLorean/sub22/ch-dbg/cw_inst=
all.sh">ftp://upgrade@10.2.0.2/home/upgrade/DeLorean/sub22/ch-dbg/cw_inst=
all.sh</A><BR>
/n/Build-Trees/R3.0.0.0/R3.0.0.0-060607/nfx-tree/Build/ch-dbg/Release/cw_=
install.sh<BR>
<BR>
Source tree:<BR>
<BR>
/n/Build-Trees/R3.0.0.0/R3.0.0.0-060607/nfx-tree<BR>
<BR>
Perforce sync info:<BR>
<BR>
//depot/FB-DELOREAN/...@24204 modulo one nfx-tree/Makefile change for =
the 'make release' target support for cw_install<BR>
<BR>
Thanks,<BR>
<BR>
-Ken<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
________________________________<BR>
<BR>
From: Brian DeForest<BR>
Sent: Wednesday, June 06, 2007 1:00 PM<BR>
To: Ken Renshaw; Raj Kumar<BR>
Cc: Sandrine Boulanger<BR>
Subject: RE: Please include this in sub #22<BR>
<BR>
<BR>
<BR>
We need 2 things for sub22:<BR>
<BR>
<BR>
<BR>
1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the P4 changelist #24171 includes a =
changed openbsd file.&nbsp;&nbsp; Since it doesn't need to be compiled =
(/etc/rc) I suggest simply patching this into the latest BSD build =
rather than do a full BSD build, if Ken agrees after reviewing the =
changelist.<BR>
2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; merge the fix for CQ #19400 from Zonda =
to Delorean &amp; have Jobi review the merge<BR>
<BR>
<BR>
<BR>
________________________________<BR>
<BR>
From: Ken Renshaw<BR>
Sent: Wednesday, June 06, 2007 12:30 PM<BR>
To: Raj Kumar; Brian DeForest<BR>
Cc: Sandrine Boulanger<BR>
Subject: RE: Please include this in sub #22<BR>
<BR>
<BR>
<BR>
I need to finish a build for Ed first, but I can build sub22 later this =
afternoon.<BR>
<BR>
<BR>
<BR>
-Ken<BR>
<BR>
<BR>
<BR>
________________________________<BR>
<BR>
From: Raj Kumar<BR>
Sent: Wednesday, June 06, 2007 12:21 PM<BR>
To: Raj Kumar; Brian DeForest<BR>
Cc: Sandrine Boulanger; Ken Renshaw<BR>
Subject: RE: Please include this in sub #22<BR>
<BR>
<BR>
<BR>
When should we start the build?<BR>
<BR>
<BR>
<BR>
________________________________<BR>
<BR>
From: Raj Kumar<BR>
Sent: Wed 6/6/2007 10:50 AM<BR>
To: Brian DeForest<BR>
Cc: Sandrine Boulanger<BR>
Subject: RE: Please include this in sub #22<BR>
<BR>
yeah thats my suggestion.<BR>
<BR>
<BR>
<BR>
________________________________<BR>
<BR>
From: Brian DeForest<BR>
Sent: Wed 6/6/2007 10:48 AM<BR>
To: Raj Kumar<BR>
Cc: Sandrine Boulanger<BR>
Subject: RE: Please include this in sub #22<BR>
<BR>
I'll confirm w/ Andy that this is ready.&nbsp;&nbsp;&nbsp; So that would =
be 2 builds, sub22 this week and sub23 next week w/ more MF fixes.<BR>
<BR>
<BR>
<BR>
________________________________<BR>
<BR>
From: Raj Kumar<BR>
Sent: Wednesday, June 06, 2007 10:44 AM<BR>
To: Brian DeForest<BR>
Cc: Sandrine Boulanger<BR>
Subject: RE: Please include this in sub #22<BR>
<BR>
<BR>
<BR>
I like to complete 40 TB by 6/15. So we need a build ASAP since it takes =
time to create data.<BR>
<BR>
<BR>
<BR>
Also Paul has asked us to start with CW-install tests, so we need to =
build.<BR>
<BR>
<BR>
<BR>
________________________________<BR>
<BR>
From: Brian DeForest<BR>
Sent: Wed 6/6/2007 10:39 AM<BR>
To: Raj Kumar<BR>
Cc: Sandrine Boulanger<BR>
Subject: RE: Please include this in sub #22<BR>
<BR>
But is the 40TB testing happening this week or could this wait for the =
next build, likely early next week?<BR>
<BR>
<BR>
<BR>
I'd prefer to do one more build, if possible, but we may need 2 if you =
need this fix sooner.<BR>
<BR>
<BR>
<BR>
________________________________<BR>
<BR>
From: Raj Kumar<BR>
Sent: Wednesday, June 06, 2007 10:29 AM<BR>
To: Brian DeForest; Jobi Ariyamannil<BR>
Cc: May Ma; Sandrine Boulanger<BR>
Subject: RE: Please include this in sub #22<BR>
<BR>
<BR>
<BR>
I think completing the 40TB test should give us enough test coverage for =
this change. We should take this<BR>
<BR>
<BR>
<BR>
________________________________<BR>
<BR>
From: Brian DeForest<BR>
Sent: Wed 6/6/2007 9:40 AM<BR>
To: Raj Kumar; Jobi Ariyamannil<BR>
Cc: May Ma; Sandrine Boulanger<BR>
Subject: RE: Please include this in sub #22<BR>
<BR>
I had been considering this one, and Sandrine and I had discussed it as =
a possibility.&nbsp;&nbsp; On the other hand, I also want to stabilize =
the code base and minimize the checkins.<BR>
<BR>
<BR>
<BR>
What is the test impact?<BR>
<BR>
<BR>
<BR>
________________________________<BR>
<BR>
From: Raj Kumar<BR>
Sent: Wednesday, June 06, 2007 6:44 AM<BR>
To: Jobi Ariyamannil<BR>
Cc: May Ma; Sandrine Boulanger; Brian DeForest; Ken Renshaw<BR>
Subject: Please include this in sub #22<BR>
<BR>
<BR>
<BR>
Hi,<BR>
<BR>
<BR>
<BR>
Like to pull this into sub #22.<BR>
<BR>
<BR>
<BR>
Thanks.<BR>
<BR>
<BR>
<BR>
________________________________<BR>
<BR>
From: Jobi Ariyamannil<BR>
Sent: Tue 6/5/2007 9:51 PM<BR>
To: Raj Kumar<BR>
Cc: May Ma; Sandrine Boulanger<BR>
Subject: RE: Defect TED00019400 FP watchdog timeout on almost full =
filesystem (33TB) in fs_buddy_bnum_in_free_region()<BR>
<BR>
Is your filesystem becoming almost full frequently?<BR>
<BR>
If your intention is to populate 40TB, you may temporarily disable the =
snapshots.<BR>
<BR>
Also if this is an absolute showstopper for you, we may port the fix to =
delorean.<BR>
<BR>
Regards,<BR>
Jobi<BR>
<BR>
-----Original Message-----<BR>
From: raj.kumar@onstor.com [<A =
HREF=3D"mailto:raj.kumar@onstor.com">mailto:raj.kumar@onstor.com</A>]<BR>=

Sent: Tuesday, June 05, 2007 7:58 PM<BR>
To: Jobi Ariyamannil; Jobi Ariyamannil; May Ma<BR>
Cc: May Ma; Sandrine Boulanger<BR>
Subject: Defect TED00019400 FP watchdog timeout on almost full =
filesystem (33TB) in fs_buddy_bnum_in_free_region()<BR>
<BR>
Headline: FP watchdog timeout on almost full filesystem (33TB)&nbsp; in =
fs_buddy_bnum_in_free_region()<BR>
id: TED00019400<BR>
Note_Entry: Jobi,<BR>
<BR>
ENG7 (40 TB setup) is continously crashing due to FS issue. Here is the =
trace, is this trace same issue as this defect?<BR>
<BR>
#0&nbsp; 0x8304ae50 in fs_buddy_bnum_in_free_region =
(context=3D0x1ae3e000,<BR>
&nbsp;&nbsp;&nbsp; bnum=3D4266274790, len=3D1, =
isFull=3D0xffffffff85621118) at fs-buddy.c:2235<BR>
#1&nbsp; 0x8304a550 in fs_buddyFindExtent (context=3D0x1ae3e000, =
len=3D1, target=3D<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {block =3D 4266274790}, =
isFirstFileExtent=3D0, noSnap=3Dfalse)<BR>
&nbsp;&nbsp;&nbsp; at fs-inlines.c:99<BR>
#2&nbsp; 0x83038744 in fs_allocateBuddyExtent (context=3D0x101ae3e000, =
requested=3D1,<BR>
&nbsp;&nbsp;&nbsp; target=3D{block =3D 4266274790}, anySize=3D0, =
noSnap=3D0, isFirstFileExtent=3D0)<BR>
&nbsp;&nbsp;&nbsp; at fs-alloc.c:856<BR>
#3&nbsp; 0x83035d94 in fs_allocateExtent (context=3D0x101ae3e000, =
inode=3D0x1025e442d0,<BR>
&nbsp;&nbsp;&nbsp; page=3D14069157, len32=3D1, anySize=3D0, =
contigAlloc=3D0) at fs-alloc.c:1280<BR>
#4&nbsp; 0x83057998 in fs_bufAllocDoBufs (context=3D0x101ae3e000, =
inode=3D0x1025e442d0,<BR>
&nbsp;&nbsp;&nbsp; numInBufs=3D1, bufs=3D0xffffffff856217d8, =
commitInode=3Dtrue, contigAlloc=3Dfalse)<BR>
&nbsp;&nbsp;&nbsp; at fs-buf.c:6870<BR>
#5&nbsp; 0x830e40a0 in fs_writeThread (context=3D0x101ae3e000) at =
fs-nfs.c:4856<BR>
#6&nbsp; 0x83067fa4 in fs_threadBegin (handle=3D10223717, =
arg=3D0x101ae3e000)<BR>
&nbsp;&nbsp;&nbsp; at fs-context.c:2781<BR>
#7&nbsp; 0x8301d2a8 in esmthread_start (handle=3D448921600, =
nextState=3D0, event=3D<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {event =3D 0, p1 =
=3D {u =3D {dw =3D 18446744071612824480, w =3D 2198240160, p =
=3D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
0xffffffff83067ba0}}, p2 =3D {u =3D {dw =3D 18446744072094767276, w =3D =
2680182956, p =
=3D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
0xffffffff9fc058ac}}}, userInfo=3D0x101ae3e000) at thread-api.c:311<BR>
#8&nbsp; 0x8301a5c4 in esm_threadMain (arg=3D0x1000a33f20) at =
esm-nfx.c:224<BR>
#9&nbsp; 0x8301a568 in esm_threadMain (arg=3D0x1000a33f20) at =
esm-nfx.c:195<BR>
State: Assigned<BR>
history: 33706857&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; May 31 2007&nbsp; =
3:31PM&nbsp;&nbsp;&nbsp;&nbsp; maym&nbsp;&nbsp;&nbsp; Submit&nbsp; =
no_value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Opened<BR>
33706861&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; May 31 2007&nbsp; =
3:51PM&nbsp;&nbsp;&nbsp;&nbsp; jobia&nbsp;&nbsp; Need_more_info&nbsp; =
Opened&nbsp; More_Info<BR>
33706874&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; May 31 2007&nbsp; =
5:10PM&nbsp;&nbsp;&nbsp;&nbsp; jobia&nbsp;&nbsp; Back_to_triage&nbsp; =
More_Info&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Re-opened<BR>
33706892&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; May 31 2007 =
10:38PM&nbsp;&nbsp;&nbsp;&nbsp; jobia&nbsp;&nbsp; Modify&nbsp; =
Re-opened&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Re-opened<BR>
33707130&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Jun&nbsp; 4 =
2007&nbsp; 2:13PM&nbsp;&nbsp;&nbsp;&nbsp; jobia&nbsp;&nbsp; Modify&nbsp; =
Re-opened&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Re-opened<BR>
33707215&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Jun&nbsp; 4 =
2007&nbsp; 9:37PM&nbsp;&nbsp;&nbsp;&nbsp; =
sandrineb&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Review&nbsp; =
Re-opened&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Reviewed<BR>
33707284&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Jun&nbsp; 5 =
2007&nbsp; 1:20PM&nbsp;&nbsp;&nbsp;&nbsp; jobia&nbsp;&nbsp; Assign&nbsp; =
Reviewed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Assigned<BR>
33707347&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Jun&nbsp; 5 =
2007&nbsp; 7:48PM&nbsp;&nbsp;&nbsp;&nbsp; =
sandrineb&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Modify&nbsp; =
Assigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Assigned<BR>
33707348&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 06/05/2007 19:57:53 =
PM&nbsp; rajk&nbsp;&nbsp;&nbsp; Modify&nbsp; =
Assigned&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Assigned<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7A8B7.35B053E7--
