The following describes available solutions for sfcfsck(8) abnormal termination.
The following message is displayed if sfcfsck(8) fails in requesting for memory allocation for the internal table.
Can't allocate memory |
Add a swap area.
The following message is output if acquisition of the file system configuration information fails.
Can not connect to FsRM other node information get error |
See
Start the file system monitoring facility on all the nodes that provide the GFS Shared File System. See "9.2.4 Starting sfcfrmd daemon."
This message indicates that the command terminated abnormally because a mismatch was found in the partition configuration data for the GFS Shared File System partitions.
Can't open device-name: errno setup: Volume information error setup: fsck quit due to unrecoverable error! |
Use sfcadm(8) to recover the partition information.
The following example shows how to restore partition information on the "/dev/sfdsk/gfs01/dsk/volume01" device.
For a single partition, perform the following operation:
# sfcadm -r -a /dev/sfdsk/gfs01/dsk/volume01 <Enter> |
For a multi-partition configuration, use sfcinfo(8) to check the partitions and then use sfcadm(8) to perform recovery using the representative partition.
# sfcinfo /dev/sfdsk/gfs01/dsk/volume01 <Enter> /dev/sfdsk/gfs01/dsk/volume01: FSID special size Type mount 1 /dev/sfdsk/gfs01/dsk/volume01(1e756) 25418 META ----- 1 /dev/sfdsk/gfs01/dsk/volume01(1e756) 5120 LOG ----- 1 /dev/sfdsk/gfs01/dsk/volume01(1e756) 232256 DATA ----- 1 /dev/sfdsk/gfs01/dsk/volume02(1e757) 341778 DATA ----- 1 /dev/sfdsk/gfs01/dsk/volume03(1e758) 578704 DATA ----- # sfcadm -r /dev/sfdsk/gfs01/dsk/volume01 <Enter> |
See
In the result of sfcinfo(8) executed, the partition displayed the first will be the representative partition of the file system. See sfcinfo(8).
If the node which executed sfcfsck(8) is not a shared node of the file system, the following message is output.
No node volume entry for localhost,file system access forbidden! |
Execute sfcfsck(8) at the shared node of the file system.
The following message indicates that the file system is irreparable because of the GFS Shared File System data has been destroyed.
BAD SUPER BLOCK BAD VOLUME INFORMATION No Meta volume information available! No Log volume information available! Only found num data volume, total num in superblock! |
If a backup of the file system is available, recover the file system from the backup.
The following message is displayed if there are problems in the parameter or the execution environment of sfcfsck(8).
not super user duplicate option filesystem lock failed. errno(error-number) device-name is a mounted file system device-name is not for sfcfs Can't check device-name Can't open /etc/fstab setmntent failed. errno(error-number) fs_clean is not FSLOG. cannot log replay! |
Confirm whether the parameter and the execution user of the command are correct or /etc/fstab and /etc/mtab exist.
The following message is displayed if the file system was not repaired completely.
***** PLEASE RERUN FSCK *****
device-name: UNEXPECTED INCONSISTENCY; RUN sfcfsck MANUALLY.
Log Replay is failed. |
Execute a full file system check using sfcfsck(8).
The following example shows how to perform check the file system on the "/dev/sfdsk/gfs01/dsk/volume01" device.
# sfcfsck -o nolog /dev/sfdsk/gfs01/dsk/volume01 <Enter> |
When the message which shows other abnormalities is output and sfcfsck(8) terminates abnormally, please tell field engineers the output message of sfcfsck after collecting the diagnostic data with FJQSS (Information Collection Tool), fjsnap(8), or pclsnap(8).
