PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment)
Contents Index PreviousNext

Appendix E List of Messages> E.5 Management Command messages Specific to GFS Shared File System

E.5.8 sfcgetconf command

E.5.8.1 ERROR: sfcgetconf: 0001: Permission denied

[Explanation]

Execution was attempted with other than super user permission.

[Action]

Perform execution with super user permission.

E.5.8.2 ERROR: sfcgetconf: 0002: Cannot allocate memory

[Explanation]

Memory could not be allocated. Memory of system is insufficient.

[Action]

Please check the state of a system, and wait for the termination of another process, or increase the swap space or real memory. After it and re-execute the command.

E.5.8.3 ERROR: sfcgetconf: 0003: Invalid `-i' parameter: "iparam"

[Explanation]

The parameter specified for the "i" option is invalid.

[Action]

Re-execute the command with a valid (numerical) parameter in the "i" option.

E.5.8.4 ERROR: sfcgetconf: 0004: Invalid parameter

[Explanation]

The format of the command parameter is invalid.

[Action]

Re-execute the command with a valid parameter according to the format.

E.5.8.5 ERROR: sfcgetconf: 0005: backupfile is already exist

[Explanation]

The specified file as a backup (backupfile) has already existed.

[Action]

Re-execute the command with a file that does not exist.

E.5.8.6 ERROR: sfcgetconf: 0006: Cannot open backupfile: open(2) returned errcode=errno

[Explanation]

The open(2) processing for the backup file (backupfile) failed.

[Action]

Re-execute the command with the correct name of the backup file after checking the location where the backup file will be created.

E.5.8.7 ERROR: sfcgetconf: 0007: Cannot fdopen backupfile: fdopen(3C) returned errcode= errno

[Explanation]

The fdopen(3C) processing for the backup file (backupfile) failed.

[Action]

Re-execute the command with the correct name of the backup file after checking the location where the backup file will be created.

E.5.8.8 ERROR: sfcgetconf: 0008: Cannot access to cluster foundation: frm_cl_open() returned errcode=errno

[Explanation]

Communication with the cluster control could not be established.

[Action]

Check whether the cluster control is operating normally.

E.5.8.9 ERROR: sfcgetconf: 0009: Cannot get domain wide lock: config

[Explanation]

Execution of this command failed as another command is currently being executed.

[Action]

Re-execute this command after the execution of the other command.

E.5.8.10 ERROR: sfcgetconf: 0010: Cannot open path_to_sfcfrm.conf: fopen(3C) returned errcode=errno

[Explanation]

The fopen(3C) processing for sfcfrm.conf failed while attempting to acquire a backup of the sfcfrm.conf file according to the "-a" option.

[Action]

Check whether sfcfrm.conf exists at the path location displayed in the message. If the file is missing, then sfcsetup(1M) processing may not have been performed.

E.5.8.11 ERROR: sfcgetconf: 0011: file system configuration information parse error: frm_tabent() returned errcode=errno

[Explanation]

There is invalid data in sfcstab of the management partition.

[Action]

Use the backup of the management partition that was acquired previously to restore the management partition.

E.5.8.12 NOTICE: sfcgetconf: 0012: fsid=fsid is not found

[Explanation]

The file system configuration information that corresponds to fsid, which was specified as the target of the search with the '-i' option, could not be found.

Backup processing of the file system configuration information, that corresponds to the specified fsid, was ignored by the command.

[Action]

By eliminating the target of the fsid specification from the command argument specification, message output can be disabled.

E.5.8.13 NOTICE: sfcgetconf: 0013: dev=raw_device_file is not found

[Explanation]

The file system configuration information that corresponds to raw_device_file, which was specified as the target of the search with the '-d' option, could not be found.

Backup processing of the file system configuration information that corresponds to the specified raw_device_file was ignored by the command.

[Action]

By eliminating the target of the raw_device_file specification from the command argument specification, message output can be disabled.


Contents Index PreviousNext

All Rights Reserved, Copyright(C) FUJITSU LIMITED 2004