Top
PRIMECLUSTER Global File Services Configuration and Administration Guide 4.5
FUJITSU Software

12.2.1 Action to be taken when fsck terminates abnormally

The following describes available solutions for fsck_sfcfs(1M) abnormal termination.

12.2.1.1 Memory allocation request error

The following message is displayed if fsck_sfcfs(1M) fails in requesting for memory allocation for the internal table.

Can't allocate memory

Add a swap area.

12.2.1.2 File system configuration information acquisition failure

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 share the GFS Shared File System. See "9.2.4 Starting sfcfrmd daemon"

12.2.1.3 File system partition configuration data error

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(1M) to recover the partition information.

The following example shows how to restore partition information on the "/dev/sfdsk/gfs01/rdsk/volume01" device.

For a single partition, perform the following operation:

# sfcadm -r -a /dev/sfdsk/gfs01/rdsk/volume01 <Enter>

For a multi-partition configuration, use sfcinfo(1M) to check the partitions and then use sfcadm(1M) 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(11500000021)     25418  META  -----
   1 /dev/sfdsk/gfs01/dsk/volume01(11500000021)      5120  LOG   -----
   1 /dev/sfdsk/gfs01/dsk/volume01(11500000021)    232256  DATA  -----
   1 /dev/sfdsk/gfs01/dsk/volume02(11500000022)   7341778  DATA  -----
   1 /dev/sfdsk/gfs01/dsk/volume03(11500000023)   6578704  DATA  -----

# sfcadm -r /dev/sfdsk/gfs01/rdsk/volume01 <Enter>

See

In the result of sfcinfo(1M) executed, the partition displayed the first will be the representative partition of the file system. See sfcinfo(1M).

12.2.1.4 Node that executed fsck_sfcfs(1M) is not a shared node of the file system

If the node which executed fsck_sfcfs(1M) 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 fsck_sfcfs(1M) at the shared node of the file system.

12.2.1.5 Irreparable file system destruction

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.

12.2.1.6 Operation error

The following message is displayed if there are problems in the parameter or the execution environment of fsck_sfcfs(1M).

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/vfstab

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/vfstab and /etc/mnttab exist.

12.2.1.7 Repairing of file system is non-completion

The following message is displayed if the file system was not repaired completely.

*****  RERUN FSCK *****

<device-name>: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.

Log Replay is failed.

Execute a full file system check using fsck_sfcfs(1M).

The following example shows how to perform check the file system on the "/dev/sfdsk/gfs01/rdsk/volume01" device.

# fsck -F sfcfs -o nolog /dev/sfdsk/gfs01/rdsk/volume01 <Enter>

12.2.1.8 Executed in non-global zone

The following message is output when the fsck_sfcfs(1M) command is executed in a non-global zone.

cannot be executed in non-global zone

The command cannot be used in non-global zones.

For Solaris 10, only global zones can be used to operate GFS.

12.2.1.9 Collection of zone information fails

The following message is output when collection of zone setup information fails.

cannot get current zone information

When the message is output, check the system then wait until the other process is done, or expand the swap area or memory. Execute the command again.

12.2.1.10 Other messages

When the message which shows other abnormalities is output and fsck_sfcfs(1M) terminates abnormally, tell field engineers the output message of fsck_sfcfs(1M) after collecting the diagnostic data with FJQSS (Information Collection Tool) or fjsnap(1M).