International Business Machines Corporation

Richard B Stelmach

Karl Allen Nielsen

Matthew J Kalos

David Montgomery

David Frank Mannenbach

Pui Fun Lau

Matthew G Borlick

Clint Alan Hardy

Richard Anthony Ripberger

Robert Akira Kubo

James A O'Connor

James Lee Hafner

Chao Li

David Ray Kahler

Krishnakumar Rao Surugucchi

Yu-Cheng Hsu

Suguang Li

Michael P Vageline

Jacob Lee Sheppard

Michael John Jones

A determination is made that data stored in an extent of a first storage resource is to be moved to an extent of a second storage resource. Operations that are still awaiting to start execution in the first storage resource after the data stored in the extent of the first storage resource has been moved to the extent of the second storage resource, are configured for execution in the second storage resource.

Processing of a set of pending operations for a switchover from a first storage resource to a second storage resource

For managing RAID parity stripe contention using a processor device in a computing environment, delaying, by a host being separate to the RAID, one of a plurality of operations overlapping a parity sector in a parity stripe with a currently running operation and serializing each one of the multiplicity of operations overlapping the parity sector. The host further serializes each one of the plurality of operations overlapping the parity sector. The delaying is performed when the host determines whether a new write written through a hardware performance path comprising the one of the plurality of operations will overlap the parity stripe of a previous write comprising the currently running operation at the RAID controller.

Managing RAID parity stripe contention

For managing RAID parity stripe contention using a processor device in a computing environment, delaying one of a multiplicity of operations overlapping a parity sector in a parity stripe with a currently running operation and serializing each one of the multiplicity of operations overlapping the parity sector.

Managing raid parity stripe contention

Provided are techniques for migrating a first extent, determining a spatial distance between the first extent and a second extent, determining a ratio of a profiling score of the second extent to the spatial distance, and, in response to determining that the ratio exceeds a threshold, migrating the second extent.

Spatial extent migration for tiered storage architecture

Provided are a method, system, and article of manufacture for error checking addressable blocks in storage. Addressable blocks of data are stored in a storage in stripes, wherein each stripe includes a plurality of data blocks for one of the addressable blocks and at least one checksum block including checksum data for the addressable block. A write request is received to modify data in one of the addressable blocks. The write and updating the checksum are performed in the stripe having the modified addressable block. An indication is made to perform an error checking operation on the stripe for the modified addressable block in response to the write request, wherein the error checking operation reads the data blocks and the checksum in the stripe to determine if the checksum data is accurate. An error handling operation is initiated in response to determining that the checksum data is not accurate.

Error checking addressable blocks in storage

Method, system, and computer program product embodiments for concurrent copy of system configuration global metadata in a data storage system are provided. In one exemplary embodiment, a global data rank is quiesced, followed by an unquiesce of the global data rank except for a global metadata area. The global metadata area is updated in memory, and then unquiesced. A current range of the global metadata area to be copied is quiesced. The current range of the global metadata area is copied from a source area to a target area. The current range is unquiesced. The steps of quiescing an additional current range, copying the range from a source area to a target area, and unquiescing the current range continue until the entire global metadata area has been copied.

Concurrent copy of system configuration global metadata

Provided are a method, system, and article of manufacture for error checking addressable blocks in storage. Addressable blocks of data are stored in a storage in stripes, wherein each stripe includes a plurality of data blocks for one of the addressable blocks and at least one checksum block including checksum data derived from the data blocks for the addressable block. A write request is received to modify data in one of the addressable blocks. The write and updating the checksum are performed in the stripe having the modified addressable block. An indication is made to perform an error checking operation on the stripe for the modified addressable block in response to the write request, wherein the error checking operation reads the data blocks and the checksum in the stripe to determine if the checksum data is accurate. An error handling operation is initiated in response to determining that the checksum data is not accurate.

Provided are a method, system, and article of manufacture for detecting data integrity. An indicator is written to invalidate a data block that is capable of being stored in a plurality of sectors of a storage device, wherein the indicator is written to the storage device in at least one sector that is not included in the plurality of sectors. A writing of entire contents of the data block to the plurality of sectors of the storage device is initiated, in response to the writing of the indicator. The indicator is updated to validate the data block, in response to a completion of the writing of the entire contents of the data block to the plurality of sectors of the storage device.

Detecting data integrity

A bad track in a disk device in a data storage system is recovered by determining which cluster in the system the bad track belongs to. If the track belongs to the cluster that discovered that the track was bad, that cluster recovers the track by locating a good copy of the track, staging the good copy of the track to cache, and destaging the good copy of the track storage unit from the cache to all copies of the track, whether good or bad, in the data storage system. If the track belongs to another cluster, the cluster that discovered that the track was bad sends a message to the other cluster to inform it of the bad track, and the other cluster recovers the bad track. In another aspect, all tracks are owned by one server or server cluster, which performs the staging and destaging.

Growing community of inventors

Tucson, AZ, United States of America

Richard B Stelmach