Chapter 38 File-System Messages

The messages in this chapter are generated by the file-system subsystem. The subsystem ID displayed by these messages includes ZFIL as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

101

process has used 75% of its PFS. Program: program

`process`	is the name of the process that encountered the error when it attempted to allocate more space than the PFS is capable of holding.
`program`	is the name of the program that encountered the error.

Cause The indicated process has allocated more than three-quarters of the space available in its process file segment (PFS).

Effect None. However, if the process continues to consume PFS space until the available space is exhausted, operations of the program will fail as described under event 102.

Recovery This is a warning message that the process might experience PFS exhaustion at a future time. Unless it is certain that the available PFS space will not be exhausted, possible actions should be investigated and initiated. See event message 102 for recovery information. For more information about monitoring PFS consumption, see items 76 and 77 of the PROCESS_GETINFOLIST_ procedure in the Guardian Procedure Calls Reference Manual.

102

process has exhausted its PFS. Program: program

`process`	is the name of the process that encountered the error when it attempted to allocate more space than the PFS is capable of holding.
`program`	is the name of the program that encountered the error.

Cause The indicated process attempted to allocate more space than the process file segment (PFS) is capable of holding. Each process allotted a PFS that can hold 8 megabytes, regardless of user’s PFS size settings.

Effect A system call within the process fails. Further operations might also fail, although no subsequent event messages will be generated.

Recovery Reduce the PFS space used by the process. In some cases, this might be done by reducing the amount of work assigned to the process so that the process attempts fewer simultaneous file-system operations. How to reduce assigned work is application dependent. In many cases, the program will have to be modified to change the way it does operations that consume PFS space. The following are possible places where work assignments can be reduced:

The number of concurrent user I/O’s done by the program.
The size of the user I/O’s.
The number files opened.
The nowait depth on open files.
The use of sequential block buffering on open files.
Turning off PFS I/O buffering using SETMODE function 72. For more information about the SETMODE procedure, see the Guardian Procedure Calls Reference Manual.

103

process File close request to target-process has timed out. Program: program Timeout value: timeout seconds

`process`	is the name of the process that encountered the timeout error when file close request is sent to the `target-process`
`target-process`	is the name of the process that did not respond to the close request.
`program`	is the name of the program that encountered the timeout error. If the event is generated while the process is terminating then program is `$``systemloadvol`.`subvol`.`NOPROGRM`
`timeout`	is the timeout value, in seconds.

Cause The target process target-process did not reply to a file close request from the affected process process. There might be network issues in the system or with other systems connected through the Expand network.

Effect The target process target-process might not clean up certain data structures, which can later result in communication problems for the target process.

Recovery Fix the network connectivity problems. If necessary, restart the target process.

104

Allocation error for FLEXPOOL resource. Unable to allocate Measure FILE entity counter records. Program: program

program

is the name of the program that encountered the error.

Cause The process is unable to allocate Measure FILE entity counter records for some open files because the FLEXPOOL resource has been exhausted.

Effect Measure is not able to report FILE entity statistics on some file opens in this process.

Recovery Move the program or other FLEXPOOL intensive applications to other processors.




	NOTE: FLEXPOOL is a shared resource. The availability of FLEXPOOL might be affected by other system processes using the same processor.

105

process During a process open, a request to the monitor process on node: node-number, cpu: cpu-number has timed out. Program: program-name

`process`	is the name of the process that encountered the timeout error.
`node-number`	node number of the monitor process.
`cpu-number`	CPU number of the monitor process.
`program-name`	is the name of the program that encountered the timeout error. If the event is generated while the process is terminating, the program is `$``coldloadvol`.`subvol`.`NOPROGRM`.

Cause The local or remote monitor process did not respond to a request from the affected process for a stipulated time of one minute or six minutes.

Effect The Guardian application program interfaces (APIs) FILE_OPEN_() and OPEN() fail with error 162.

Recovery Contact your service provider.

106

process TS/MP process target-process has become unresponsive.

`process`	is the name of the process that encountered the problem.
`target-process`	is the name of the TS/MP process.

Cause The TS/MP process does not respond to a request from the TS/MP requestor.

Effect The TS/MP requestor waiting for reply from the TS/MP process hangs. If more number of requestors hang, it leads to a condition where the new process creation fails.

Recovery If the new process creation fails, take processor dump and reload the processor. Contact your service provider.