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

Part 2 Global File Services Local File System> Chapter 4 Management of the GFS Local File System> 4.5 Checking the File System for Consistency (fsck)

4.5.1 Action method fsck terminates abnormally

Action method fsck_sfxfs(1M) terminates abnormally is explained below.

4.5.1.1 The memory demand is abnormal

The memory demand for fsck_sfxfs(1M) internal table is fails, the following messages are output.

Can't allocate memory for <xxxx>
xxxx: fsck internal table name, dup table, bta dup table, others.

Add the swap area.

4.5.1.2 Obtaining configuration information of GFS Local File System is fails

Obtaining configuration information of GFS Local File System is fails, the following message is output.

<device-name> is sfxfs_getfstab error!

Confirm the status of /etc/sfxfstab file, and is recovered.

4.5.1.3 The partition configuration information of GFS Local File System is abnormal

Each partition configuration information of GFS Local File System is disagreement, the following messages are output.

Can't open <device-name>: <errno>
Can't get the data of partition <device-name>
setup: Volume information error
setup: fsck quit due to unrecoverable error!

Recover the partition configuration information; use sfxadm(1M) command.

The file system is a single partition configuration, the following operations are done.

# sfxadm -r -a <device-name>

The file system is multi partition configurations, after the partition is confirmed by output of sfxinfo(1M), recover from representative partition, use sfxadm(1M) command.

# sfxinfo <device-name>
# sfxadm -r <restoration origin device-name>,<device-name>,...

4.5.1.4 The node cannot be added

The node cannot be added, the following message are output.

No node volume entry for localhost, file system access forbidden!

Add the node, use sfxnode(1M) command.

4.5.1.5 File system damage which cannot be recovered

GFS Local File System data damage that cannot be recovered, the following messages are output.

No Meta volume information available!
No Log volume information available!
Only found <num> data volume(s), total <num> in superblock!
The data volume <device-name> is not found!
setup_data: fs_dsize < sum(dvol->sdata)!

It is not possible to recover. Restore from the backup if you buck up the file system.


Contents Index PreviousNext

All Rights Reserved, Copyright(C) FUJITSU LIMITED 2004