Common errors

This topic lists some common errors that you might encounter when using SAN File System. While these errors are generally easy fixes, it is sometimes difficult to determine the cause.

Errors when running setupsfsclient

After running the SAN File System client setup utility, the utility fails with the following error messages:
HSTDR0029I The kernel extension was successfully loaded from file
 /usr/tank/client/bin/stfs kernel module ID (kmid) = 63cc400.
HSTDR0030I File system driver is initialized and ready to handle file-system
 type 20. /usr/tank/client/bin/stfsclient: 
HSTCL0011E A -create parameter uses a maximum of two parameter values:
 client name and server name. You specified 17.
HSTCS0008E Could not create SAN File System client
HSTDR0033E SAN File System driver shut down successfully.
HSTDR0035I The kernel extension 63cc400 was unloaded successfully.

This group of errors is displayed because of a syntax error in one of the configuration fields that you completed when you ran the setupsfsclient command.

An example of this can be seen in the following entry to the device candidate list:
pat=/dev/rvpath *
In this field, there should not be a space between rvpath and the asterisk (*). In this case, the setupsfsclient will fail and the previously mentioned errors will result.

Error: Drive not found when starting SAN File System

One startup test when starting SAN File System requires the system to discover the drives. If this test does not complete before a test that requires a specific drive to be available begins, the server will enter a 5 second pause and attempt the connection again.

The server should connect to the drive before its next attempt, but a Drive not found error might occur from the first attempt.

Parent topic: Diagnostic tools

Library | Support | Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.
IBM TotalStorage SAN File System v2.2