PRIMECLUSTER Global File Services Configuration and Administration Guide 4.3

A.1.1 Panic messages

This sub-section describes the AC panic messages of the GFS Shared File System.

PANIC: sfcfs: 0001: mountpoint: procedure_num is invalid value: procedure_num = procedure_num

Explanation

An invalid request for a process was sent from MDS.

Response

Collect the followings for troubleshooting information and then contact your customer support engineers:

• A crash dump

• A file output with fjsnap on all the nodes at the time of rebooting them

PANIC: sfcfs: 0002: mountpoint: it cannot found extent that should be found

Explanation

A failure occurred in extent information.

Response

Collect the followings for troubleshooting information and then contact your customer support engineers:

• A crash dump

• A file output with fjsnap on all the nodes at the time of rebooting them

PANIC: sfcfs: 0003: mountpoint: It failed update META data. so happened PANIC for fear that the data be destroyed

Explanation

Updating meta-data failed. It resulted in a panic for fear of destroying the meta-data.

Response

Collect the followings for troubleshooting information and then contact your customer support engineers:

• A crash dump

• A file output with fjsnap on all the nodes at the time of rebooting them

PANIC: sfcfs: 0004: mountpoint: failed to update extent

Explanation

Updating extent information failed. Updating extent information failed.

Response

Collect the followings for troubleshooting information and then contact your customer support engineers:

• A crash dump

• A file output with fjsnap on all the nodes at the time of rebooting them

PANIC: sfcfs: 0005: mountpoint: dirty buffer remaine in inode

Explanation

A panic occurred because the i-node in the writing process onto a physical device was found when blockading was attempted.

Response

Collect the followings for troubleshooting information and then contact your customer support engineers:

• A crash dump

• A file output with fjsnap on all the nodes at the time of rebooting them

PANIC: sfcfs: 0006: mountpoint: failed to unmount

Explanation

Unmounting failed.

Response

Collect the followings for troubleshooting information and then contact your customer support engineers:

• A crash dump

• A file output with fjsnap on all the nodes at the time of rebooting them

PANIC: sfcfs: 0007: Failed to XDR encode. xdrmbuf_clearbase: len = len: base = base: next = next
PANIC: sfcfs: 0008: Failed to XDR encode. xdrmbuf_putbytes: has next prev = has next prev: prev next = prev next
PANIC: sfcfs: 0009: Failed to XDR encode. xdrmbuf_putbytes
PANIC: sfcfs: 0010: Failed to XDR encode. xdrmbuf_getpos: base = base: private = private: mlen = mlen: handy = handy

Explanation

XDR encoding failed.

Response

Collect the followings for troubleshooting information and then contact your customer support engineers:

• A crash dump

• A file output with fjsnap on all the nodes at the time of rebooting them

PANIC: sfcfs: 0011: assertion failed

Explanation

An internal error is detected.

Response

Collect the followings for troubleshooting information and then contact your customer support engineers:

• A crash dump

• A file output with fjsnap on all the nodes at the time of rebooting them

PANIC: sfcfs: 0012: Assertion failed: detail

Explanation

An internal error is detected. The details of an error are displayed at detail.

Response

Collect the followings for troubleshooting information and then contact your customer support engineers:

• A crash dump

• A file output with fjsnap on all the nodes at the time of rebooting them

PANIC: sfcfs: 0013: mount_point: Incomplete blockade

Explanation

As taking time to blockade the file system (mount_point), a node panic is carried out.

Response

Collect the followings for troubleshooting information and then contact your customer support engineers:

• A crash dump

• A file output with fjsnap on all the nodes at the time of rebooting them