Masa's blog

Setting up JBOD with Fujitsu D2607 RAID Card on PRIMERGY Servers

Fujitsu does not officially support JBOD in Fujitsu 6Gb RAID 0/1 RAID card (D2607) on their PRIMERGY servers, and the JBOD mode is disabled by default. However you can enable it and use disks in JBOD with D2607.
Here is a procedure on how to enable JBOD in D2607.

Power on your PRIMERGY server.
Press the Control and Y keys during the RAID card initializaton (see below) to launch the command line interface.

Run the AdpGetProp command to check the current javascript:;setting.

Run the AdpSetProp command to enable JBOD if it is disabled.

Enter the 'q' key to exit the CLI.
Reboot.

If the drives which you want to use in JBOD are not shown as JBOD drives like "Unconfigured Good", you need to make the drives JBOD.

Please note that, as I said at the beginning, Fujitsu does not support the JBOD mode with the D2607 RAID card. You can enable and use it, but it should be done at your own risk. If you need D2607 JBOD support, please ask your Fujitsu contact for support.

Update on April 11th: I tested the above configuration on a previous generation of Fujitsu servers (S6 generation). I borrowed an S7 server (RX300 S7) with 16 HDDs and D2607, and did the same setting. The system hung when the RAID controller was being initialized.

When I used a later version of unsupported firmware, the system was able to boot with all the 16 drives in JBOD. I could install Solaris 10 and use all the drives in ZFS as JBOD. Therefore the issue would be caused by the Fujitsu firmware.

Bilding sysbench 0.4.12 on RHEL5

Here is what I got and what I did to compile sysbench 0.4.12 on my RHEL5 box. My system is running RHEL 5.4 x86_64 (kernel 2.6.18-164.el5).

The first step is to download the source code from the sysbench site, and run the normal commands as usual.

$ tar zxvf sysbench-0.4.12.tar.gz
$ cd tar zxvf sysbench-0.4.12
$ ./configure
$ make

Then I got the following error:

...
../libtool: line 838: X--tag=CC: command not found
../libtool: line 871: libtool: ignoring unknown tag : command not found
../libtool: line 838: X--mode=link: command not found
../libtool: line 1004: *** Warning: inferring the mode of operation is deprecated.: command not found
../libtool: line 1005: *** Future versions of Libtool will require --mode=MODE be specified.: command not found
../libtool: line 2231: X-g: command not found
../libtool: line 2231: X-O2: command not found
../libtool: line 2231: X-rdynamic: command not found
../libtool: line 1951: X-L/usr/lib64/mysql: No such file or directory
../libtool: line 1951: X-L/usr/lib64: No such file or directory
../libtool: line 2400: Xsysbench: command not found
...

As you see, there are many libtool errors, so I ran the autoreconf command to generate all build related files.

$ touch NEWS AUTHORS
$ autoreconf -ifv
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
Putting files in AC_CONFIG_AUX_DIR, `config'.
autoreconf: running: /usr/bin/autoconf --force
autoreconf: running: /usr/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
autoreconf: Leaving directory `.'

Ok. Let's re-run the commands.

$ ./configure
$ make

The errors are gone now. Next step is to install the compiled programs with the 'make install' command.

$ sudo make install

The last step is to run the sysbench command to make sure if it works ok.

$ sysbench --test=cpu run
sysbench 0.4.12:  multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 1

Doing CPU performance benchmark

Threads started!
Done.

Maximum prime number checked in CPU test: 10000


Test execution summary:
    total time:                          9.5088s
    total number of events:              10000
    total time taken by event execution: 9.5048
    per-request statistics:
         min:                                  0.95ms
         avg:                                  0.95ms
         max:                                  1.20ms
         approx.  95 percentile:               0.95ms

Threads fairness:
    events (avg/stddev):           10000.0000/0.00
    execution time (avg/stddev):   9.5048/0.00

Solaris Crash Analysis Tool 5.2

Solaris Crash Analysis Tool (SolarisCAT) 5.2 is released. You can download it from the Sun Download Center site. From the Release Notes, there is not much difference from the SolarisCAT 5.1.

How to swap the Caps Lock and Control keys on Solaris 10

Edit the ~/.xmodmap file.
Add the following lines to the file.

remove Lock = Caps_Lock
remove Control = Control_L
keysym Control_L = Caps_Lock
keysym Caps_Lock = Control_L
add Lock = Caps_Lock
add Control = Control_L

Edit the ~/.dtprofile file.
Add the following lines to the file.

if [ -f ~/.xmodmaprc ] ; then
/usr/openwin/bin/xmodmap ~/.xmodmaprc
fi

Solaris Crash Analysis Tool 5.1 GA

Solaris Crash Analysis Tool (Solaris CAT) 5.1 is released. You can download it from the SUN download site. Also you can read the release notes on this page.

How to check your PostgreSQL version

Switch to 'root' or a database admin user
```
$ su -
```

Issue the following command
```
# psql -V
```
or
```
# psql --version
```

Allowed memory size of 8388608 bytes exhausted on RHEL 5

When I tried to install the Fileinfo module from the PECL site, I got the following error message.

$ pecl -v install fileinfo
(snip)
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 143 bytes) in /usr/share/pear/PEAR/PackageFile/v2.php on line 1140

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 100 bytes) in /usr/share/pear/PEAR.php on line 765

Even though I set the memory_limit variable to 32M which is over 8M!

$ php -i | grep memory_limit
memory_limit => 32M => 32M

Here is a workaround for this issue.

Insert the following line to the /usr/share/pear/pearcmd.php file.

@ini_set('memory_limit', '32M');

Then, run the pecl command again. Now you can install the module without the above error message :-)