HP StorageWorks Scalable File Share User Manual
Page 235
Emergency clustat events occur during configure server command
9–11
9.18 Emergency clustat events occur during configure server command
When the
configure server
command is running on a server for the first time, emergency
clustat
events such as the following may appear in the event log:
south1 clustat[4867]: <emerg> diskLseekRawReadChecksum: bad check sum, part = 1
offset = 8704 len = 24
These messages are benign and the events can be ignored.
9.19 The show log command fails with corrupted record
Occasionally, the
show log
command fails, with a message similar to the following:
Corrupted record with log_size == 131072
seek forward: Input/output error
You can correct this problem by entering the following command on the administration server:
# evlogmgr --fix
9.20 SFS CLI command fails with error: Could not insert duplicate
record
An SFS CLI command such as the
boot server
command may occasionally fail with an error message
similar to the following:
sfs> boot server south3
Error: Command not entered into the Database:
lsdbCommandsAdd: lsdbAdd: liblsdb.so: Could not insert duplicate record
If this happens, there may be a problem with the
hpls_commands
table in the database.
Check the
hpls_commands
table as follows:
# mysql hplsdb
mysql> check table hpls_commands;
+----------------------+-------+----------+------------------------------------
+| Table | Op | Msg_type |Msg_text
+----------------------+-------+----------+------------------------------------
+
| hplsdb.hpls_commands | check | warning | Auto-increment value: 0 is smaller
than max used value: 866 |
| hplsdb.hpls_commands | check | status | OK
+----------------------+-------+----------+------------------------------------
+
If the table returns warnings similar to the warning in the example above, you can attempt to repair the table
by entering the following command:
mysql>
repair table hpls_commands;
When the repair operation has completed, enter the
check table
command again. If the table has been
successfully repaired, the output will be similar to the following:
mysql> check table hpls_commands;
+----------------------+-------+----------+----------+
| Table | Op | Msg_type | Msg_text |
+----------------------+-------+----------+----------+
| hplsdb.hpls_commands | check | status | OK |
+----------------------+-------+----------+----------+
1 row in set (0.00 sec)
If the table has been successfully repaired, you can enter the original command that failed.