28Common TOPS VSN log messages (0202)
0003/0075 Message: [PRU_name] received an IO error (Object_Not_Writable) on path [file/directory_path name]. The "server" error was the result of performing a write operation on an object (or file) that can not be written to.
Description: The PRU encountered an error during an IO (write) operation
on the file or object. The operation was not performed. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.
Action: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If neither reboot operations are successful, then reboot the whole system. Document the problem, record all action taken, and then contact NT.
0003/0076 Message: [PRU_name] received an IO error (Bad_Access_Mode) on path [file/directory_path name]. The "server" error was the result of an illegal access specification in pathname.
Description: The PRU encountered an error during an IO operation on the file or directory. The operation was not performed. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.
Action: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If neither reboot operations are successful, then reboot the whole system. Document the problem, record all action taken, and then contact NT.
0003/0077 Message: [PRU_name] received an IO error (Bad_Remote_Pointer) on path [file/directory_path name]. The "server" error was the result of using a bad remote pointer.
Description: The PRU encountered an error during an IO operation on the file or directory. The operation was not performed. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.
Action: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then reboot the PRU. If the problem persists, then reboot the server which handles the IO operation. If neither reboot operations are successful, then reboot the whole system. Document the problem, record all action taken, and then contact NT.
0003/0078 Message: [PRU_name] received an IO error (Transaction_Timeout) on path [file/directory_path name]. The "server" error was the result of a timeout that occurred on a close/commit of a transactional file set.
Description: The PRU encountered an error during an IO operation on the file or directory. The operation was not performed. It is the responsibility of the PRU performing the operation to recover from the error and to retry the operation. If it is unable to do so, then it can declare itself faulty.