Patent application number | Description | Published |
20120005162 | Managing Copies of Data Structures in File Systems - A method, data processing system, and computer program product for managing data. A processor unit copies a data structure within a hierarchy of data structures to form a copy of the data structure. The data structure belongs to a level within a plurality of levels in the hierarchy of data structures. The processor unit associates an identifier with the data structure within the hierarchy of data structures. The processor unit increments a portion of the identifier for the data structure in response to copying the data structure to form the copy of the data structure and associating the identifier with the data structure within the hierarchy of data structures. The portion of the identifier that is incremented is based on the level within the plurality of levels in which the data structure is located. | 01-05-2012 |
20120066181 | FILE REMOVAL WITH NO AVAILABLE DISK BLOCKS IN REDIRECT-ON-WRITE FILE SYSTEMS - Embodiments include a method for removing a file within a redirect-on-write file system. In some embodiments, a file removal operation is detected in a file management unit, which resides in a memory unit. It is then determined that the number of free data blocks in the persistent storage is below a minimum threshold. The file removal operation is written to a log used for storing system operations. A file management unit is notified of the successful write of the file removal operation to the log used for storing system operations. The data blocks are moved from the file selected for removal to a list of free data blocks. The indirect blocks from the file selected for removal are moved to a data block removal list. | 03-15-2012 |
20120066182 | INODE MANAGEMENT IN REDIRECT-ON-WRITE FILE SYSTEM - Some embodiments of the inventive subject matter allow a redirect-on-write file system to continue processing file transactions while writing a snapshot to persistent storage. Thus, embodiments do not block file transactions while flushing snapshots to persistent storage. To avoid blocking, some embodiments the file system can maintain two snapshot generations. The first snapshot generation is the snapshot being written to persistent storage. The second snapshot generation may reside in main memory, and store data for file transactions occurring after the file system began writing the first snapshot generation. | 03-15-2012 |
20120066183 | FILE CLONING ACROSS DIFFERENT FILESETS - After a clone file is created from a file, a write request targeting the clone file can be handled. It is determined that the write request indicates the clone file that was cloned from a file in a first fileset. The clone file is of a second fileset and a clustered file system comprises the first fileset and the second fileset. A data block of the clone file affected by the write request is determined. It is then determined that the data block at a current location cannot be modified. The write request is implemented with respect to the data block at a different location. It is indicated that the data block at the different location can be modified for subsequent write requests that indicate the clone file | 03-15-2012 |
20120066190 | HANDLING FILE OPERATIONS WITH LOW PERSISTENT STORAGE SPACE - In some embodiments, a file management unit located in the operating system detects a write operation that writes the data blocks within the consistency snapshot (in main memory) to the persistent storage. The file management unit can then determine that all transactions have been completed before the write operation begins. In some instances, the file management unit then attempts to write the data blocks within the consistency snapshot to the persistent storage. The file management unit can then receive a notification that the write operation did not successfully write the data blocks from the consistency snapshot to the persistent storage. In some embodiments, the write operation is not successful because there are fewer free data blocks in the persistent storage than needed for writing the data blocks within the consistency snapshot to persistent storage. The file management can then wait a period of time. After the file management unit has waited for a period of time, it can make another attempt to write the data blocks within the consistency snapshot to the persistent storage. | 03-15-2012 |
20120066278 | DISTRIBUTED FILE HIERARCHY MANAGEMENT IN A CLUSTERED REDIRECT-ON-WRITE FILE SYSTEM - Management of a file hierarchy for a clustered file system can be distributed across nodes of the cluster. A cluster file hierarchy is accessed to determine location of a file in response to a request to write to a file. A first node maintains the cluster file hierarchy. It is determined that management of a fileset object, which represents a fileset that includes the file, has been delegated to a second node based, at least in part, on said accessing the cluster file hierarchy. A node file hierarchy maintained by the second node is accessed responsive to determining the delegation. The cluster file hierarchy represents filesets of the clustered file system and the node hierarchy represents a subset of one or more of the filesets. Location of the file is determined based, at least in part, on said accessing the node file hierarchy. | 03-15-2012 |
20120066431 | RECOVERABILITY WHILE ADDING STORAGE TO A REDIRECT-ON-WRITE STORAGE POOL - Embodiments include a method comprising detecting addition of a new nonvolatile machine-readable medium to a data storage pool of nonvolatile machine-readable media. The method includes preventing from being performed a first operation of a file system that requires a first parameter that identifies a logical indication of a location within the nonvolatile machine-readable media for the file system, until logical indications of locations within the new nonvolatile machine-readable medium for the file system have been stored in the data storage pool. The method includes allowing to be performed, prior to logical indications of locations within the new nonvolatile machine-readable medium being stored in the data storage pool, a second operation of the file system that does not require a second parameter that identifies a logical indication of a location within the nonvolatile machine-readable media, wherein the second operation causes data to be written into the new nonvolatile machine-readable medium. | 03-15-2012 |
20120131274 | Legacy Data Managment - Various systems, processes, products, and techniques may be used to manage legacy data. In one general implementation, a system, process, and/or product for managing legacy data may include the ability to determine whether a data request has been received and, if a data request has been received, determine whether the data request is associated with legacy data of an external storage management system. If the data request is not associated with legacy data of an external storage management system, the system, process, and/or product may retrieve data from a local storage array, and if the data request is associated with legacy data of an external storage management system, the system, process, and/or product may request legacy data from an external storage management system. The system, process, and/or product may also generate a response to the data request. | 05-24-2012 |
20120150800 | INDEPENDENT FILESET GENERATIONS IN A CLUSTERED REDIRECT-ON-WRITE FILESYSTEM - Maintaining a generation value for each fileset that is distinct from a corresponding fileset manager preserves the independence of nodes while also allowing distributed fileset management. A fileset manager can maintain a value that reflects consistency snapshots for that node (“node generation”) separately from a value that reflects consistency snapshots for a particular fileset (“fileset generation”). | 06-14-2012 |
20120150804 | MULTIPLE CONTEXTS IN A REDIRECT ON WRITE FILE SYSTEM - A method includes initiating committing to persistent storage of a current consistency snapshot of a plurality of data objects in a redirect-on-write file system. Each of the plurality of data objects has a first copy of at least two copies of the data having a first context of at least two contexts. The method includes receiving, during committing to storage of the current consistency snapshot, an update to a data object of the plurality of data objects. The method also includes responsive to receipt of the update to the data object, creating a second copy of data of the data object from the first copy. The second copy of the data has a second context of the at least two contexts. The method includes responsive to receipt of the update to the data object, updating, based on the update, the second copy of the data of the data object. | 06-14-2012 |
20120150926 | DISTRIBUTED FREE BLOCK MAP FOR A CLUSTERED REDIRECT-ON-WRITE FILE SYSTEM - In a cluster that distributes fileset management, fileset managers will maintain a free block map and an in-flight block map to allocate blocks to clients writing to a relevant fileset. A fileset manager managing free block allocation for cluster clients that write to a fileset managed by the fileset manager. Since a clustered file system manager manages an initial free block map for the cluster (“cluster free block map”), the clustered file system manager provisions free blocks to fileset managers from the cluster free block map. The fileset manager then allocates free blocks from the provisioned free blocks to cluster clients that write to the fileset managed by the fileset manager. | 06-14-2012 |
20120209813 | FILE CLONING ACROSS DIFFERENT FILESETS - After a clone file is created from a file, a write request targeting the clone file can be handled. It is determined that the write request indicates the clone file that was cloned from a file in a first fileset. The clone file is of a second fileset and a clustered file system comprises the first fileset and the second fileset. A data block of the clone file affected by the write request is determined. It is then determined that the data block at a current location cannot be modified. The write request is implemented with respect to the data block at a different location. It is indicated that the data block at the different location can be modified for subsequent write requests that indicate the clone file | 08-16-2012 |
20120284230 | Importing Pre-Existing Data of a Prior Storage Solution into a Storage Pool for Use with a New Storage Solution - Mechanisms are provided for importing pre-existing data into a storage system utilizing a current storage management system that is different from an original storage management system used to create the pre-existing data. One or more data storage devices are integrated into the storage system in-place without modification of the pre-existing data stored on the one or more data storage devices. Metadata for the pre-existing data is created based on a linear progression of data in the pre-existing data. Read access requests targeting the pre-existing data are executed using the created metadata. Write access requests targeting the pre-existing data are executed by redirecting the write access requests to a copy of the pre-existing data created in another storage location. | 11-08-2012 |
20120284309 | Importing Pre-Existing Data of a Prior Storage Solution into a Storage Pool for Use with a New Storage Solution - Mechanisms are provided for importing pre-existing data into a storage system utilizing a current storage management system that is different from an original storage management system used to create the pre-existing data. One or more data storage devices are integrated into the storage system in-place without modification of the pre-existing data stored on the one or more data storage devices. Metadata for the pre-existing data is created based on a linear progression of data in the pre-existing data. Read access requests targeting the pre-existing data are executed using the created metadata. Write access requests targeting the pre-existing data are executed by redirecting the write access requests to a copy of the pre-existing data created in another storage location. | 11-08-2012 |
20130039166 | HIERARCHICAL NETWORK FAILURE HANDLING IN A CLUSTERED NODE ENVIRONMENT - According to one aspect of the present disclosure, a method and technique for hierarchical network failure handling in a clustered node environment is disclosed. The method includes: detecting a network failure by a node in a cluster, the cluster having plural nodes arranged in a hierarchy, wherein the network failure is associated with a subordinate node in the hierarchy to the detecting node; communicating the network failure from the detecting node to a superior node in the hierarchy; determining whether the network failure affects nodes higher than the detecting node in the hierarchy; and responsive to determining that the network failure does not affect nodes higher than the detecting node in the hierarchy, the detecting node initiating a protocol to expel the subordinate node from the cluster. | 02-14-2013 |
20130318086 | DISTRIBUTED FILE HIERARCHY MANAGEMENT IN A CLUSTERED REDIRECT-ON-WRITE FILE SYSTEM - Management of a file hierarchy for a clustered file system can be distributed across nodes of the cluster. A cluster file hierarchy is accessed to determine location of a file in response to a request to write to a file. A first node maintains the cluster file hierarchy. It is determined that management of a fileset object, which represents a fileset that includes the file, has been delegated to a second node based, at least in part, on said accessing the cluster file hierarchy. A node file hierarchy maintained by the second node is accessed responsive to determining the delegation. The cluster file hierarchy represents filesets of the clustered file system and the node hierarchy represents a subset of one or more of the filesets. Location of the file is determined based, at least in part, on said accessing the node file hierarchy. | 11-28-2013 |
20140156602 | FILE CLONING ACROSS DIFFERENT FILESETS - A method includes determining, by a processor, that a write request indicates a clone file that was cloned from a file in a first fileset. The clone file is of a second fileset and a clustered file system comprises the first fileset and the second fileset. A data block of the clone file affected by the write request is determined. The method includes determining that the data block at a current location cannot be modified. In response to a determination that the data block at the current location cannot be modified, the method includes implementing the write request with respect to the data block at a different location and indicating that the data block at the different location can be modified for subsequent write requests that indicate the clone file. | 06-05-2014 |
Patent application number | Description | Published |
20080270422 | IN-FLIGHT FILE DESCRIPTORS CHECKPOINT - A computer implemented method, data processing system, and computer program product for enabling the restoration of in-flight file descriptors during a checkpoint operation. Responsive to a checkpoint operation being initiated on a process in a workload partition, in-flight file pointers in an in-flight file queue on a socket bound to the process are identified. A file descriptor is instantiated in the process file table of the process for each identified in-flight file pointer in the in-flight file queue. After completion of the checkpoint operation, the in-flight file queue on the socket may be reconstructed in a restore operation using the instantiated file descriptors. | 10-30-2008 |
20080294787 | CREATING A CHECKPOINT FOR MODULES ON A COMMUNICATIONS STREAM - A computer implemented method, computer program product, and system for creating a checkpoint of a stream. A stream checkpoint request to create the checkpoint of the stream is received, wherein the stream is used by a process as a communications path, and wherein the communications path is modified by a set of modules. In response to identifying the identity of each module in the set of modules, the identity of each module in the set of modules is stored in the checkpoint. In response to identifying an order of the set of modules, the order of the set of modules is stored in the checkpoint. In response to sending a stream checkpoint message to each module in the set of modules, module data is received from each module in the set of modules to form received module data. The received module data is stored in the checkpoint. | 11-27-2008 |
20080320590 | METHOD AND APPARATUS FOR CREATING SECURED FILE VIEWS IN A SOFTWARE PARTITION - A computer implemented method, apparatus, and computer program product for creating secured file views of a protected file. The process receives a request to access the file, wherein the file is stored in a common location, and wherein the request includes a set of file viewing parameters. The process identifies a callback function associated with the file and calls the callback function with the set of file viewing parameters to form a set of virtual viewing parameters. Thereafter, the process generates a secured file view of the file using the virtual viewing parameters, wherein the secured file view is viewable by a user of an authorized partition. | 12-25-2008 |
20120204148 | MANAGING AN APPLICATION SOFTWARE PARTITION - A computer implemented method, apparatus, and computer usable program code for managing a software partition in logical partitioned data processing system. A virtual root process is created for the software partition, wherein the virtual root process functions as a root process for the software partition. The set of child processes is re-parented to the virtual root process in response to termination of a process having a set of child processes. | 08-09-2012 |