Method, system, and program for managing meta data in a...

Electrical computers and digital processing systems: memory – Storage accessing and control – Hierarchical memories

Reexamination Certificate

Rate now

  [ 0.00 ] – not rated yet Voters 0   Comments 0

Details

C711S112000, C711S154000, C711S113000, C714S015000, C714S016000

Reexamination Certificate

active

06438661

ABSTRACT:

FIELD OF THE INVENTION
The present invention relates to a method for managing meta data in cache and using meta data to access customer data.
BACKGROUND OF THE INVENTION
Computing systems often include one or more host computers (“hosts”) for processing data and running application programs, direct access storage devices (DASDs) for storing data, and a storage controller for controlling the transfer of data between the hosts and the DASD. In addition to storing actual data, also known as user or customer data, the control unit often maintains meta data which provides information on tracks or blocks of data in the DASD or in a cache of the storage controller. The storage controller processes the meta data during certain operations on the actual data represented by the meta data to improve the speed and efficiency of those requested operations.
There are numerous types of meta data, such as summary information, partial-copy information, historical information, copy services information, and log structured array information. Summary information summarizes the customer data, including information on the format of a block or track of customer data, such as a count-key-data (CKD) track. In this way, information on the actual customer data that would otherwise have to be gleaned from the customer data in a time consuming process is readily available. Partial copy information contains a copy of a portion of the actual customer data to improve destage performance. Historical information records historical usage of the customer data. Historical data may be used to predict future use of the user or customer data. Copy services information contains bit maps that indicate tracks of the customer data that were modified and not yet copied to a secondary site. The log structured array (LSA) information maintains an LSA directory and related data to manage the LSA.
Typically, during initialization of the DASD, meta data is copied from the DASD to the storage controller. As the size of a meta data track and the types of meta data maintained increases, an ever increasing amount of cache storage and processing capacity is dedicated to meta data, to the exclusion of other types of data. In addition, because cache storage is volatile (data stored in cache will be lost in the event of a power loss), some conventional computing systems save meta data that has been modified in cache into separate, battery-backed-up, non-volatile storage units (NVS) for recovery purposes. Such implementations add additional costs and overhead by consuming processor and memory resources to maintain and update the meta data in NVS.
To conserve NVS capacity, some computing systems will not back-up meta data in NVS. The problem with not providing an NVS backup is that microcode errors, power loss, and other error conditions may cause some or all of the meta data stored in cache to become invalid or lost. In such case, the storage controller must rebuild the meta data from the actual data in the DASD. This process of recovering lost meta data can be time-consuming, as meta data often represents thousands of customer tracks. In conventional computing systems when modified meta data is not backed-up into NVS, lost meta data is rebuilt in a piecemeal process every time its associated customer data is staged into cache for other purposes. The need to rebuild the meta data delays the recovery of meta data and also degrades data processing operations.
There thus is a need in the art for an improved method and system for managing meta data for data recovery operations.
SUMMARY OF THE INVENTION
Preferred embodiments provide an improved method, system, and article of manufacture for processing modified meta data for data recovery operations. The meta data provides information on user data maintained in a storage device. The system determines whether meta data tracks maintained in a cache were modified and indicates in a non-volatile memory that the determined meta data tracks were modified. Data recovery operations may be initiated as a result of a system failure, such as a warmstart or coldstart recovery. During such data recovery operations, the system processes the non-volatile memory and the indications of modified meta data tracks therein to rebuild lost meta data tracks in the cache.
In further embodiments, the system indicates in the non-volatile memory that the meta data track was modified by indicating the modified meta data track on a list of modified meta data tracks. The system then rebuilds lost meta data tracks by processing the list of modified meta data tracks to generate a rebuild list indicating meta data tracks to rebuild. The system processes the rebuild list to determine meta data tracks to rebuild and rebuilds the meta data tracks indicated on the rebuild list. The rebuilt meta data tracks are then stored in the cache.
With preferred embodiments, meta data that was previously modified but not yet backed up on the storage device, e.g., DASD, may be rebuilt by using a list maintained in the non-volatile storage unit, e.g., battery backed-up RAM, that indicates whether modified meta data was in cache when the system failed. During recovery operations, the system may readily determine from the list those meta data tracks that were modified in cache when the system failed. If, during recovery, the system cannot recover the modified meta data tracks as indicated on the list from the cache, then the system would generate a rebuild list of meta data tracks to rebuild in the cache. The meta data on the rebuild list is rebuilt from the customer data. In this way, the system need only maintain a list indicating modified meta data tracks in the non-volatile storage unit in order to restore those modified meta data tracks that were in cache when the system failed.


REFERENCES:
patent: 4888681 (1989-12-01), Barnes et al.
patent: 4987533 (1991-01-01), Clark et al.
patent: 5237682 (1993-08-01), Bendert et al.
patent: 5403639 (1995-04-01), Belsan et al.
patent: 5448719 (1995-09-01), Schultz et al.
patent: 5452444 (1995-09-01), Solomon et al.
patent: 5488731 (1996-01-01), Mendelsohn
patent: 5524203 (1996-06-01), Abe
patent: 5533190 (1996-07-01), Binford et al.
patent: 5572660 (1996-11-01), Jones
patent: 5590318 (1996-12-01), Zbikowski et al.
patent: 5594836 (1997-01-01), Ryu et al.
patent: 5636359 (1997-06-01), Beardsley et al.
patent: 5644766 (1997-07-01), Coy et al.
patent: 5675781 (1997-10-01), Duncan et al.
patent: 5724501 (1998-03-01), Dewey et al.
patent: 5748874 (1998-05-01), Hicksted et al.
patent: 5774643 (1998-06-01), Lubbers et al.
patent: 5787243 (1998-07-01), Stiffler
patent: 5835955 (1998-11-01), Dornier et al.
patent: 6021408 (2000-02-01), Ledain et al.
patent: 6044444 (2000-03-01), Ofek
patent: 6112277 (2000-08-01), Bui et al.
patent: 6260129 (2001-07-01), Crockett et al.
patent: 7073085 (1995-03-01), None
patent: 9321579 (1993-10-01), None
Matthews et al., “Improving The Performance Of Log-Structured File Systems With Adaptive Methods”, Proceedings of the ACM Symposium on Operating Systems Principles, pp.: 238-251, Oct. 1997.*
R. Hagmann, “Reimplementing The Cedar File System Using Logging And Group Commit”, Proceedings of the ACM Symposium on Operating Systems Principles, pp.: 155-162, 1987.*
M. Baker et al., “Non-Volatile Memory for Fast, Reliable File Systems”, International Conference on Architectural Support for Programming Languages and Operating Systems, pp. 10-22, Oct. 1992.*
P. Chen et al., “The Rio File Cache: Surviving operating System Crashes”, International Conference on Architectural Support for programming Languages and Operating Systems, pp. 74-83, Oct. 1-4, 1996.*
Gregory R. Ganger et al. Soft Updates: A Solution to the Metadata Update Problem in the File Systems, ACM Transaction on Computer Systems, pp. 127-153, May 2000.*
IBM Technical Disclosure Bulletin; Destage Algorithm Transitions with Redundant Arrays of Independent Disks; vol. 38, No. 10, Oct. 1995.
Research Disclosure; Non-Retentive Data Identifier (NRDID); Feb. 1989, No. 298.
U.S. patent application Ser. No. 09/261,683 filed Mar. 3,

LandOfFree

Say what you really think

Search LandOfFree.com for the USA inventors and patents. Rate them and share your experience with other people.

Rating

Method, system, and program for managing meta data in a... does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Method, system, and program for managing meta data in a..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method, system, and program for managing meta data in a... will most certainly appreciate the feedback.

Rate now

     

Profile ID: LFUS-PAI-O-2891676

  Search
All data on this website is collected from public sources. Our data reflects the most accurate information available at the time of publication.