Abstract: Provided are a system and program maintaining information on a namespace comprised of filesets shared by clients over a network. Zone information is maintained on at least one zone, wherein each zone associates at least one client system, at least one fileset, and at least one storage pool. For one zone, the associated at least one fileset and at least one storage pool are accessible to the at least one client system. Clients are provided information on filesets included in a namespace, wherein each of a plurality of clients receive information on the at least one fileset associated with the client in the at least one zone including the client.

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: A method, system, and article of manufacture, wherein a plurality of references to a plurality of files corresponding to a plurality of devices are stored in a data structure implemented in a computational device, wherein the computational device is coupled to the plurality of devices via a network. Access is enabled to the data structure to a distributed application, wherein the distributed application uses a stored reference in the data structure to determine a file corresponding to a device, and wherein the distributed application performs data transfer operations with the device via the determined file.

Abstract: A method and system for conducting an integrity check of system and user metadata when the metadata is mounted. A filesystem reviewer is embedded within software of a server node. A mutual exclusion lock is obtained on the selected metadata. An automated verification of the locked metadata is conducted while the filesystem is mounted. In addition, an automated salvage of the locked metadata may be conducted while the filesystem is mounted. The verification and/or salvage of the locked metadata can be applied to system, user, and/or a portion of the user metadata.

Abstract: A method and system for conducting an integrity check of system and user metadata when the metadata is mounted. A filesystem reviewer is embedded within software of a server node. A mutual exclusion lock is obtained on the selected metadata. An automated verification of the locked metadata is conducted while the filesystem is mounted. In addition, an automated salvage of the locked metadata may be conducted while the filesystem is mounted. The verification and/or salvage of the locked metadata can be applied to system, user, and/or a portion of the user metadata.

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: A technique for implementing policy-aware backup and restore capability in a tiered storage system. If a data set's contents are backed up from the tiered storage system to a backup storage system, metadata for the data set may also be backed up. Prior to the data set being restored from the backup storage system to the tiered storage system, the backed up metadata is restored and processed to determine a tier among the tiered storage pools to which the data set will be restored.

Abstract: A method, apparatus and program storage device for providing real-time file system charge-back accounting with real time historical minimum and maximum usage per user or group during a report cycle. In a first storage area of file system memory, space allocation data for a current accounting period is monitored and persistently maintained. A minimum, maximum and average space allocation is calculated for the management object during the current accounting period. The calculated minimum, maximum and average space allocation for the management object may be moved to a second storage area of the file system memory while beginning to monitor and persistently maintain space allocation data of the management object in the first storage area of the file system memory during a subsequent accounting period.

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, apparatus and program storage device for providing a centralized policy based preallocation in a distributed file system. Policy rules are used to provide for the specification of a preallocation and an extend size for files in a computer system. An administrator specifies the pre-allocation and extend sizes for a set of files as defined in the set of policy rules. Policy rules used in this manner can take into account the unique situation in which a file is being created or extended.

Abstract: There is provided, in a computer processing system, an apparatus for managing object data. The apparatus includes a changed objects manager for creating and managing a changed objects list that at least identifies the objects that have changed based on time of change. The changed objects list is associated with a plurality of time buckets. Each of the plurality of time buckets is associated with a respective date and time period and with object change records for objects having a timestamp falling within the respective date and time period. Each of the object change records is associated with a unique object identifier and the timestamp for a corresponding one of the objects. The timestamp specifies a date and a time corresponding to a latest one of a creation time or a most recent update time for the corresponding one of the objects.

Abstract: A method, apparatus and program storage device for providing failover for continuous or near-continuous availability in an N-way logical shared-nothing cluster system is disclosed. Cluster application data space partitions are assigned to each node in the cluster and each node's or server software's internal architecture is partitioned in accordance with the application data partitions assigned to the node. Cluster-integrity protection is performed. A failover and recovery protocol is performed based upon the assigned partitions and the partitioned and bound internal architecture. Containment of the impact of failure is provided such that most of the application data space partitions are not impacted. Affected partition sets are failed over fast and in constant time and so actual load on the surviving nodes does not affect failover duration. When shared storage is not provided, synchronous log replication may be used to facilitate failover and log-based recovery.

Abstract: Provided are a method, system, and program maintaining information on a namespace comprised of filesets shared by clients over a network. Zone information is maintained on at least one zone, wherein each zone associates at least one client system, at least one fileset, and at least one storage pool. For one zone, the associated at least one fileset and at least one storage pool are accessible to the at least one client system. Clients are provided information on filesets included in a namespace, wherein each of a plurality of clients receive information on the at least one fileset associated with the client in the at least one zone including the client.

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.

Abstract: A process for quiescing a master (master) and a plurality of subordinate computer systems (subordinates) in a cluster. An original or a pending state may be entered that is a quiesce or an online state. The master instructs the subordinates the quiesce or online state be made the pending state. The subordinates prepare to change accordingly, determine whether successful, and vote to commit or abort. Based on whether all voted to commit, the master instructs the subordinates to either commit or abort. If to commit and the pending state is the quiesce state, an operation is performed in the subordinates. If to commit and the pending state is the online state, the subordinates prepare to resume the original state. The subordinates change from the original to the pending state. Otherwise, if to abort, the subordinates prepare to remain in the original state and reset the pending to the original state.

Abstract: A method and system for allocating blocks of disk in persistent storage to requesting threads. A primary data structure is provided for organizing and categorizing blocks of disk space. In addition, a secondary data structure is provided for maintaining a list of all active file system processes and blocks of disk space used by those processes. Blocks of disk space are assigned to pages. At such time as a thread may request allocation of disk space, both data structures are reviewed to determine if the requested disk space is available and to limit access of available disk space to a single page of memory to a single thread at any one time.

Abstract: Provided are a method, system, and article of manufacture, wherein a plurality of references to a plurality of files corresponding to a plurality of devices are stored in a data structure implemented in a computational device, wherein the computational device is coupled to the plurality of devices via a network. Access is enabled to the data structure to a distributed application, wherein the distributed application uses a stored reference in the data structure to determine a file corresponding to a device, and wherein the distributed application performs data transfer operations with the device via the determined file.

Abstract: A method and system for managing availability of a dependent thread to service a nested request is provided. A plurality of reply threads are maintained in a single thread pool. In addition, a counter is provided to track availability of a reply thread from the thread pool. A service thread that requires at least one reply thread to complete execution of a request must check the counter to determine availability of the reply thread prior to execution of the request. The process of determining availability of a reply thread prior to execution of a service thread request avoids initiating execution of a request that cannot be completed in a timely manner, or at all.

Abstract: A device comprising a substrate having a surface for contacting blood wherein the surface has a continuum of thrombus-resistant polymeric material coated on and extending into the substrate to anchor the coating thereon. The device may be prepared by a method comprising: (a) contacting the substrate with a solution of monomer or oligomer in a solvent to wet the surface and impregnate the substrate below the surface to a substantial depth; (b) removing the solvent to form a continuum of the monomer or oligomer on the surface and within the substrate to a substantial depth; and (c) polymerizing the monomer or oligomer to form a substantial continuum of polymer coating on the surface and extending to a substantial depth in the substrate, thereby firmly anchoring the polymer coating on the surface.