<!-- Title: 15:06:42  Thu Nov  3 2005 -->
<!-- Crewchief: CDF CSL -->
<!-- Op1: &nbsp; -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>New CSL disk from DotHill</pre>


<!-- Date: Thu Nov 3 15:07:55 2005 -->
<pre>I wonder how this page figures out who to send the email to.</pre>
<!-- Author: jedong -->


<!-- Date: Thu Nov 3 15:42:08 2005 -->
<pre>Alright, here is the summary of the work today: 
 
John (from Fedtek) came in 9:45 AM and started working on the new disk. The rails were too long so I had to ask Dervin to cut it off. 
 
We removed the old /logger disk from the rack 3RR11E. The new disk was mounted there. (Q: What do I do with the old /logger disk? Give to someone? Throw it away?) 
 
The disks are 12x146 GB, 15K RPM. We are going to configure them as a RAID3 with 10 (data) + 1 (parity) + 1 (hot swap). Hopefully IRIX would have no problem with 1.4 TB partition. If it does, we are going to divide the RAID into two LUN's, which would be recognized as two partitions from the logger machines. We can run it as single (one in from b0dau32 and one out to fcdfsgi1, which we have been calling "dual channel".). I think it is also possible to run it as dual (two in's from b0dau32 and two out's to fcdfsgi1, which John calls a "dual".). I need more conversation with John to understand what we can and cannot do with this new disk. 
 
If we order another box in the future, it would be cheaper by ~$7K because our box can work as a master and the extra doesn't have to have a controller. I think we can add up to three no-brain boxes to the master. 
 
If we have a disk error, we want to contact DotHill for the replacement shipped overnight. The same for the power supply error, too. Parts are all hot-swappable. DotHill also have support team in the Chicago area. They may come in in case of PS error, etc. I think we have this service for three years. Hiroyuki may be able to confirm this. 
 
John strongly suggested to upgrade to FC switch, instead of the direct connections to b0dau32 or hub connections to fcdfsgi1. 
 
This new disk won't work with the VT220 terminal anymore. One way to configure the disks is to use serial connection with a laptop and use HyperTerminal with the following setup: 
 
  com1  38400 8 none 1 
 
Anothre would be to use IP connection and a telnet session. We have assigned the IP address 192.168.32.1 to the disk. Look at the DotHill documentation for further details. 
 
We set the block size to 64KB. I was not sure what would be the optimal. 
 
Fedtek initially shipped LC+LC cables, while we had ordered LC+SC. I asked them to whip LC+SC a couple of times, but they didn't. I expected John to bring the right ones, but he thought they were already shipped. He ordered the right cables via overnight with no extra charges and we are going to keep the LC+LC cables for free. He will come in 10 AM tomorrow to finish the installation with the cables. 
 
During the setup with the serial connection and John's laptop, we kept seeing the message about the internal battery error. John will try figure it out.</pre>
<!-- Author: Jedong & Geum Bong -->

<!-- Date: Thu Nov 3 23:10:13 2005 -->
<pre>
Testing the old technique...
</pre>
<!-- Author: mako -->
<!-- Comment: Thu Nov  3 23;10;47 comment by...mako -->
<pre>It still works!</pre>

<!-- Date: Fri Nov 4 00:07:41 2005 -->
Here are some of my comments to Jedong and Geum's
entry <a 
href="/cgi/elog/det-system-elog.pl?nb=cs-logger&action=view&page=4&anchor=15:42:08">above</a>.

<pre>

What exactly is the old /logger disk? Is that the
old Ciprico "control" disk or the slow UnisonInfo's
"disk3"?

If we have to split the new DotHill disk into two
partitions, we would be mounting both partitions
on both logger machines at the same time, which
would be what John calls "dual" AND what we have
been calling dual channel. We are not interested
in the "single" mode. We might even combine the
two partitions into one logical partition if that
is possible. We would not want to assign two high
streams to these two, for example.

Forget about saving $7K for the controller; we
need a controller for each disk so we can log in
parallel at high rates.

I do not think we want to use an FC switch, either;
we would always be writing through a single link
then... Replacing a hub with a switch on the FCC
side may be OK, but that is up to the DH group.

</pre>
<!-- Author: mako -->



<!-- Date: Fri Nov 4 14:15:46 2005 -->
<pre>After the rebooting, b0dau32 is running with the old kernel and 
NIC's are set to MTU=1500. Hopefully this may be more stable than the new kernel that supports MTU=9000. 
 
The installation of the new disk is not complete. Neither I 
nor John had enough knowledge about the IRIX disk management. 
I will talk to John for further support after the disk is visible 
from b0dau32. 
</pre>
<!-- Author: Jedong, Geum Bong & Tatsuya -->


<!-- Date: Fri Nov 4 14:45:13 2005 -->
<pre>We can contact dotHill support in any case... 
 
 DotHill support  1-877-368-7925 
 
The disks information are..  
 
 PN : DHS0460-01 
 SN : DHS1MIL-0526083506 
 Customer name : Fermilab 
</pre>
<!-- Author: Geumbong -->
<!-- Comment: Fri Nov  4 15;19;46 comment by...Jedong -->
<pre>(correction)

SN : DHSIMIL-0526083506</pre>


<!-- Date: Fri Dec 9 18:04:08 2005 -->
<pre>Building code in b0csl03.  
 
The first problem I met was following : 
 
=========================================================== 
54:b0csl03 % setup -q anonymous cvs 
WARNING:  '/cdf/code-common/cdfonline/upsii_database' is not a directory 
WARNING:  '/cdf/code-common/products/upsii_database' is not a directory 
WARNING:  '/cdf/code-common/cdfonline/upsii_database' is not a directory 
WARNING:  '/cdf/code-common/products/upsii_database' is not a directory 
WARNING:  '/cdf/code-common/cdfonline/upsii_database' is not a directory 
WARNING:  '/cdf/code-common/products/upsii_database' is not a directory 
================================================= 
 
Bill suggested to comment out following lines in /cdf/cdf.cshrc: 
 
================================================= 
  set tmp_ups = `echo "${PRODUCTS}" | /bin/awk '{split($0,a,":"); for(d in a){split(a[d],b,"/");if((b[3]=="code-common")&&(b[4]=="cdfonline")){print "yes"; exit}}}'` 
  if ( "$tmp_ups" != "yes" ) then 
     setenv PRODUCTS "${PRODUCTS}:/cdf/code-common/cdfonline/upsii_database" 
  endif 
  set tmp_ups = `echo "${PRODUCTS}" | /bin/awk '{split($0,a,":"); for(d in a){split(a[d],b,"/");if((b[3]=="code-common")&&(b[4]=="products")){print "yes"; exit}}}'` 
  if ( "$tmp_ups" != "yes" ) then 
     setenv PRODUCTS "${PRODUCTS}:/cdf/code-common/products/upsii_database" 
  endif 
==================================================== 
 
I commented out and went well through the instructions and has another problem with source /csh/setup_csl.csh : 
 
==================================================== 
57:b0csl03 % cd cs-logger 
58:b0csl03 % source csh/setup_csl.csh 
/cdf/code-Linux/cdfoffline/cdf2.cshrc: No such file or directory. 
==================================================== 
 
 
 
</pre>
<!-- Author: Geumbong -->
<!-- Comment: Mon Dec 12 09;38;38 comment by...Geumbong -->
<pre>A bunch of changes of code (from Jedong) in b0csl03.

--------------------------------------------------------------------
Do the following with setup_csl.csh
--------------------------------------------------------------------
Try commenting out the lines:

  source ~cdfsoft/cdf2.cshrc
  setup kai v4_0f
  setup root v3_05_07c -qKCC_4_0

Add a line:

  setup root v4_00_08g -qGCC_3_4_3

Replace these lines:

if ("$SYS_NAME" =~ IRIX64 ) then
    setenv CDFSOFT2_INCLUDEDIR \
        "/cdf/code/cdfoffline/dist/releases/5.2.0/include"
    setenv CDFSOFT2_LIBDIR \
        "/cdf/code/cdfoffline/dist/releases/5.2.0/lib/IRIX6-KCC_4_0"
    setup smartsockets v5_5
else
    setenv CDFSOFT2_INCLUDEDIR \
        "/cdf/code/cdfoffline/dist/releases/5.3.1/include"
    setenv CDFSOFT2_LIBDIR \
        "/cdf/code/cdfoffline/dist/releases/5.3.1/lib/Linux2-KCC_4_0"
    setup smartsockets v6_0
endif

with the lines:

setenv CDFSOFT2_INCLUDEDIR \
    "/cdf/onln/code/cdfsoft/dist/releases/6.1.2/include"
setenv CDFSOFT2_LIBDIR \
    "/cdf/onln/code/cdfsoft/dist/releases/6.1.2/lib/Linux2_SL-GCC_3_4"
--------------------------------------------------------------------


--------------------------------------------------------------------
Edit the file cs-logger/make/GNUmakefile
--------------------------------------------------------------------
Replace line 547:

        $(CXX) $&lt; $(CXXFLAGS) $(CPPFLAGS) -s $(CXX_LDFLAGS) -o $(BINDIR)/$@

with:

        $(CXX) -c $&lt; $(CXXFLAGS) $(CPPFLAGS) -s $(CXX_LDFLAGS) -o $(BINDIR)/$@
--------------------------------------------------------------------


--------------------------------------------------------------------
Edit the file cs-logger/make/cs_header.gmk
--------------------------------------------------------------------
line 185:

replace "KCC" with "gcc"

line 190:

replace "-m486" with "-march=i486"

line 197:

remove "--no_exceptions"
--------------------------------------------------------------------

 ==&gt; I tried to "source csh/setup_csl.csh" again and got those messages. 

==================================================
58:b0csl03 % source csh/setup_csl.csh
ERROR: Found no match for product 'rfm'
ERROR: Action parsing failed on "unsetuprequired(-j rfm)"
ERROR: Found no match for product 'rfm'
ERROR: Action parsing failed on "setupRequired("-j rfm")"
ERROR: Found no match for product 'rfm'
ERROR: Action parsing failed on "setupRequired("-j rfm")"
setup-ppc: assuming PowerPC 603 processor
==================================================
</pre>

<!-- Comment: Tue Dec 13 13;31;18 comment by...Geumbong -->
<pre>By Radu's work, the ERRORs are gone.
-- comments from Radu
It looks like Bill has just removed the obsolete rfm product.
Now "setup fer" on b0cslXX machines seems to be working without producing any error messages.
------------------------------------------

And the other changes in codes are following:

In cs-logger/make/cs_header.gmk:
   replace every "-ldb-3.3" with "-ldb".

In cs-logger/src/library/csl_lock.c & csl_lock.h :
   delete all lines except csl_lock_mutex

-------------------------------------------------------

During building csl_report, it founds two missing l3 files:

home/gbyu/build_csl_2005_1207/cs-logger/src/library/csl_report.c:151:81: l3_misc_defns.h: No such file or directory
/home/gbyu/build_csl_2005_1207/cs-logger/src/library/csl_report.c:152:81: l3_msgbuf.h: No such file or directory

There's no where having those among include directories. </pre>