International Business Machines Corporation

Leo Shyh-Wei Luan

Frank Bernhard Schmuck

Binny Sher Gill

Wayne A Sawdon

M Corneliu Constantinescu

James Lee Hafner

Sangeetha Seshadri

Veera W Deenadhayalan

Owen Theodore Anderson

David William Archer

Geoffrey Albert Riegel

Manuel Vasconcellos Pereira, Iii

Violet Rodriguez

Veera A Deenadhayalan

Embodiments are disclosed for a method. The method includes generating a backing layer having a file volume, in a layering file format and representing a portion of a volume snapshot that is backed up on a slower storage, and enabling an associated virtual machine. The method also includes generating an active layer comprising a second file volume, in the layering file format, representing a second portion of the volume snapshot, and enabling the associated virtual machine. The method further includes starting a process to pull a plurality of blocks from the backing layer to the active layer.

Cloning storage volumes from backup

The embodiments described herein relate to managing compressed data to optimize file compression. A compression is performed on a first set of data to create a first set of compressed data partitions in a compression group. A partition table is constructed, and partition entries for the first data block are added to the table in conjunction with the first set. A current size of the compression group is assessed. In response to a compression ratio being greater than a target compression ratio and internal fragmentation of the compression group being smaller than a threshold, the compression group is dynamically completed. The dynamic completion decides a size for the compression group. The partition table is added to the compression group by assigning space within the first compression group for the table. The compression group is written to persistent storage.

Compressed data layout with variable group size

The embodiments described herein relate to managing compressed data to optimize file compression. A first compression is performed on a first set of data to create first compressed data. The first compressed data is stored in one or more blocks of a first compression group. A size of free space of a last block of the first compression group is discovered and calculated. A second compression is performed on a second set of data to create second compressed data. At least a portion of the second compressed data is supplied to the first compression group for padding into the last block in response to determining that the size of the free space is sufficient. An unpadded portion of the second compressed data is stored in one or more blocks of a second compression group.

Compressed data rearrangement to optimize file compression

The embodiments described herein relate to managing compressed data to optimize file compression for efficient random access to the data. A first partition of a first data block of a compression group is compressed. The first compressed partition is stored in a first compression entity. An in-memory table is maintained, which includes updating the in-memory table with data associated with an address of the stored compressed first partition. At such time as it is determined that the first compression entity is full, the in-memory table is compressed and written to the first compression entity. Accordingly, the in-memory table, which stores partition compression data, is store with the compression entity.

Compressed data layout for optimizing data transactions

A write error detection mechanism for a computer data disk drive or storage controller writes and then verifies data to detect disk write errors. It allows the heads to be moved to other tracks to do other jobs in the time it takes the disk to rotate from the point the data was written and to return there again so it can be read to verify the write. The data written is temporarily stored in feature table memory outside the disk, so it can be used as in the comparison later when the written data can be read for the verify. In the interim, other write-and-verify and read operations can be pipelined, or multitasked using the same head, even on different tracks.

Efficient method to detect disk write errors

A method and system for cache-based dropped write protection in data storage systems are provided. An implementation involves detecting undetected write errors in a storage system, by writing data to a storage medium from a data cache; maintaining a copy of the data in the data cache until said data on the storage medium is validated or said data needs to be evicted from the data cache; and prior to eviction of said data from the data cache, maintaining metadata for said data in a metadata cache until the data written to the storage medium has been validated against the metadata.

Method and system for cache-based dropped write protection in data storage systems

Addressed is a system and method for remote data caching and replication by local copy maintenance of remote data within a SAN file system. Distributed Storage Tank (DST), an extension to a SAN file system, provides for transparent SAN client access of local copies by importing, exporting, and storing data using network file access protocols as well as by providing assurance of metadata and file content validity. A Remote Access Agent (RAA) handles protocol implementation and conversion necessary for communication with remote data sources. Controlled by a consistency policy, consistency is maintained by RAA fetching and updating local copies if modifications have occurred to a file since it was first stored as a local copy in local storage. Additionally, RAA returns metadata pertaining to the requested data. A SAN client obtains metadata corresponding to the requested data and utilizes it to directly access locally stored copies of remote data.

Remote access agent for caching in a SAN file system

Network latencies are reduced by detecting a metadata access call for filesystem metadata contained in a filesystem node of remotely located filesystem. The metadata corresponding to the metadata access call is fetched when the metadata corresponding to the metadata access call is not contained in a local filesystem cache that has a hierarchical structure corresponding to a hierarchical structure of the remotely located filesystem. Metadata related to the metadata corresponding to the metadata access call from the remotely located filesystem is prefetched when the related metadata is not contained in the local filesystem cache. The metadata related to the metadata corresponding to the access call can be contained in a child node or a parent node of the node containing the metadata corresponding to the access call, or the descendants of such nodes.

Growing community of inventors

Saratoga, CA, United States of America

Leo Shyh-Wei Luan