Abstract: Apparatuses, methods, and computer program products are provided for receiving a remote procedure call (RPC) processing request having a priority value from a client device and processing tasks from multiple clients according to the priority values. In certain embodiments, the apparatuses, methods, and computer program products receive a remote request, compare the priority value of the received RPC processing request with priority values of pending RPC processing requests, and assign the received RPC processing request to a queue of a plurality of queues in response to the comparing.

Abstract: A computer-implemented method according to one embodiment includes determining locations of debugging statements within a computer code, and determining identifying information for each of the discovered debugging statements within the computer code. The identifying information is stored without the debugging statements. The method further includes accessing the identifying information for using in debugging the error condition in response to determining that an error condition has occurred in an execution path. A computer program product for resolving error conditions using limited stored identifying information of a computer code according to another embodiment includes a computer readable storage medium having program instructions embodied therewith. The program instructions are readable and/or executable by a computer to cause the computer to perform the foregoing method.

Abstract: A computer-implemented method according to one embodiment includes determining locations of debugging statements within a computer code, and determining identifying information for each of the discovered debugging statements within the computer code. The identifying information is stored without the debugging statements. The method further includes accessing the identifying information for using in debugging the error condition in response to determining that an error condition has occurred in an execution path. A computer program product for resolving error conditions using limited stored identifying information of a computer code according to another embodiment includes a computer readable storage medium having program instructions embodied therewith. The program instructions are readable and/or executable by a computer to cause the computer to perform the foregoing method.

Abstract: A mechanism is provided in a data processing system comprising at least one processor and a memory comprising instructions which, when executed by the at least one processor, causes the at least one processor to implement a network protocol based file system client for read-only exports. The file system client receives a mount request to mount an export at a file system server. The file system client stores an access type of the mounted export. Responsive to the file system client receiving from a user a modification request to perform a modification on an object in the mounted export, the file system client sends an attribute check request to the file system server. Responsive to the file system client receiving a first read-only file system error from the file system server, the file system client sets a read-only file system error flag.

Abstract: Apparatuses, methods, and computer program products are provided for receiving a remote procedure call (RPC) processing request having a priority value from a client device and processing tasks from multiple clients according to the priority values. In certain embodiments, the apparatuses, methods, and computer program products receive a remote request, compare the priority value of the received RPC processing request with priority values of pending RPC processing requests, and assign the received RPC processing request to a queue of a plurality of queues in response to the comparing.

Abstract: A mechanism is provided in a data processing system comprising at least one processor and a memory comprising instructions which, when executed by the at least one processor, causes the at least one processor to implement a network protocol based file system client for read-only exports. The file system client receives a mount request to mount an export at a file system server. The file system client stores an access type of the mounted export. Responsive to the file system client receiving from a user a modification request to perform a modification on an object in the mounted export, the file system client sends an attribute check request to the file system server. Responsive to the file system client receiving a first read-only file system error from the file system server, the file system client sets a read-only file system error flag.

Abstract: Techniques are provided for processing an Input/Output (I/O) request in which an identification message is received from a client computer. It is determined whether the client computer is a rogue client based on whether a current operations record exists for the client computer.

Abstract: Techniques are provided for processing an Input/Output (I/O) request. At least one data block is allocated for use in completing the I/O request. A current operations record is stored for the I/O request. It is determined whether the I/O request has been completed within a specified period of time. In response to determining that the I/O request has not been completed within the specified period of time, the allocated at least one data block is fenced.

Abstract: Provided are techniques for determining whether content of an object has changed. Under control of a backup system, opaque object attributes and a data identifier are received, wherein the data identifier is generated based on one or more relevant object attributes of the opaque object attributes that indicate whether at least one of the content of the object and one or more of the relevant object attributes has changed. The received data identifier is compared with a previously stored data identifier. In response to determining that the received data identifier and the previously stored data identifier do not match, it is determined that the content of the object has changed.

Abstract: File system objects of unknown type are backed up and restored. A list of file system objects is received from a file system. The file system objects are to be backed up. For each file system object that has a file type that is unknown, the following is performed. First, the file system is queried to obtain information regarding the file system object that is sufficient for the file system to later recreate the file system object if necessary. Second, the file system object and the information regarding the file system object are stored. Examples of file system object types of the file system that may be unknown to an application running on a Microsoft Windows® operating system include symbolic links, named pipes, and special device files.

Abstract: A method and system for supporting a concurrent recordation of a change in a data file by a server while allowing an application to continue writing changes to a data file. In response to a change in a data file, a near-instantaneous version of the file is created. Metadata reflecting the change to the data file are synchronized with a version of the file in cache and recorded in persistent storage. During the process of recording metadata changes to the file, subsequent changes to the data file may continue, and metadata reflecting the changes may be recorded in a subsequent near-instantaneous version of the file which may also be synchronized with a version of the metadata in persistent storage.

Abstract: Techniques are provided for processing an Input/Output (I/O) request. At least one data block is allocated for use in completing the I/O request. A current operations record is stored for the I/O request. It is determined whether the I/0 request has been completed within a specified period of time. In response to determining that the I/O request has not been completed within the specified period of time, the allocated at least one data block is fenced. Also provided are techniques for processing an Input/Output (I/O) request in which an identification message is received from a client computer. It is determined whether the client computer is a rogue client based on whether a current operations record exists for the client computer.