General troubleshooting
If you have a problem with the CCI software, first make sure that the
problem is not being caused by the UNIX/PC server hardware or software,
and try restarting the server.
Problem
Recommended action
Deprecated
SCSI ioctl
The following
message is
output to syslog
file(/var/log/
messages) with
every ioctl():
program
horcmgr is
using a
deprecated
SCSI ioctl,
please convert
it to SG_IO
CCI currently uses the ioctl(SCSI_IOCTL_SEND_COMMAND) for
sending the control command to the command device. However, in
RHEL 4.0 using kernel 2.6.9.
xx
, the following message is output to
syslog file(/var/log/messages) with every ioctl():
program horcmgr is using a deprecated SCSI ioctl, please
convert it to SG_IO
This can originate from the following kernel code in drivers/scsi/
scsi_ioctl.c as way of warning that ioctl(SCSI_IOCTL_…) of kernel
2.6.9.
xx
does not properly handle an error of the HBA driver.
--------------------------------------------------------------
--------
/* Check for deprecated ioctls ... all the ioctls that do not
follow
the new unique numbering scheme are deprecated */
switch (cmd) {
case SCSI_IOCTL_SEND_COMMAND:
case SCSI_IOCTL_TEST_UNIT_READY:
case SCSI_IOCTL_BENCHMARK_COMMAND:
case SCSI_IOCTL_SYNC:
case SCSI_IOCTL_START_UNIT:
case SCSI_IOCTL_STOP_UNIT:
printk(KERN_WARNING "program %s is using a
deprecated SCSI "
"ioctl, please convert it to SG_IO\n",
current->comm);
--------------------------------------------------------------
-------
Thus, CCI supports a way to change to the ioctl(SG_IO)
automatically, if Linux kernel supports the ioctl(SG_IO) for horcmgr
and
inqraid
command. However, CCI might encounter Linux kernel
that does not support the ioctl(SG_IO) fully, so CCI also supports by
defining either following environment variable or "/HORCM/etc/
USE_OLD_IOCTL" file(size=0) that uses the
ioctl(SCSI_IOCTL_SEND_COMMAND) forcibly. For example:
export USE_OLD_IOCTL=1
horcmstart.sh 10
HORCM/etc:
-rw-r--r-- 1 root root 0 Nov 11 11:12 USE_OLD_IOCTL
-r--r--r-- 1 root sys 32651 Nov 10 20:02 horcm.conf
-r-xr--r-- 1 root sys 282713 Nov 10 20:02 horcmgr
CCI cannot be
started because
horcmstart
command fails
If you have changed the configuration definition file settings: make
sure that the configuration definition file you changed is correct.
If you have changed the settings of the storage system: make sure
that the settings you changed are correct, and if necessary, change
the configuration definition file settings.
Even if there are no problems in these files and settings, but if you
cannot run CCI, get all log files under the specified directory by
9-2
Troubleshooting
Command Control Interface User and Reference Guide
Summary of Contents for HUS VM
Page 10: ...x Command Control Interface User and Reference Guide ...
Page 18: ...xviii Preface Command Control Interface User and Reference Guide ...
Page 78: ...2 50 CCI software environment Command Control Interface User and Reference Guide ...
Page 154: ...4 8 Starting up CCI Command Control Interface User and Reference Guide ...
Page 191: ...Provisioning operations with CCI 5 37 Command Control Interface User and Reference Guide ...
Page 280: ...6 56 Data replication operations with CCI Command Control Interface User and Reference Guide ...
Page 286: ...6 62 Data replication operations with CCI Command Control Interface User and Reference Guide ...
Page 302: ...7 16 Data protection operations with CCI Command Control Interface User and Reference Guide ...
Page 324: ...8 22 Examples of using CCI commands Command Control Interface User and Reference Guide ...
Page 524: ...9 200 Troubleshooting Command Control Interface User and Reference Guide ...
Page 529: ...Command Control Interface User and Reference Guide ...