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

E.1.1 Panic messages

This subsection explains the AC (kernel) panic message of the GFS Shared File System.

E.1.1.1 PANIC: sfcfs:0015: mount_point: bad v_count == 0

E.1.1.2 PANIC: sfcfs:0016: mount_point: bad v_count == 0

[Explanation]

An error in i-node management (v_count) of a file system (mount_point) was detected.

[Action]

Obtain a crash dumping, and contact local Customer Support.

E.1.1.3 PANIC: sfcfs:0057: page_create == NULL

[Explanation]

An error in i-node management (page assignment) of a file system was detected.

[Action]

Obtain a crash dumping, and contact local Customer Support.

E.1.1.4 PANIC: sfcfs:0058: bn == SFCFS_HOLE

E.1.1.5 PANIC: sfcfs:0059: bn == SFCFS_HOLE

[Explanation]

An error in i-node management (area management) of a file system was detected.

[Action]

Obtain a crash dumping, and contact local Customer Support.

E.1.1.6 PANIC: sfcfs:0062: bn == SFCFS_HOLE and rw == S_WRITE

[Explanation]

An error in i-node management (area management) of a file system was detected.

[Action]

Obtain a crash dumping, and contact local Customer Support.

E.1.1.7 PANIC: sfcfs:0063: inode not in hash queue

[Explanation]

An error in i-node management (hash management) of a file system was detected.

[Action]

Obtain a crash dumping, and contact local Customer Support.

E.1.1.8 PANIC: sfcfs:0064: mount_point: writes still outstanding, so panic to protect fs from writing by this node (wrcnt=cnt)

[Explanation]

The system was paniced because I/O by the indicated file system (mount_point) has not finished for a regular period of time.

[Action]

Obtain a crash dumping, and contact local Customer Support.

E.1.1.9 PANIC: sfcfs:0170: mount_point: could not reply to MDS (proc=pnum, ino=inum)

E.1.1.10 PANIC: sfcfs:0170: mount_point: could not reply to MDS (proc=pnum)

[Explanation]

An error was detected in the reply of AC procedure to MDS.

[Action]

Obtain a crash dumping and fjsnap, and contact local Customer Support.