Maintaining an aggregate including active files in a storage pool in a random access medium

• US 7,634,516 B2
• Filed: 08/17/2005
• Issued: 12/15/2009
• Est. Priority Date: 08/17/2005
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Cannon, David Maxwell, Martin, Howard Newton
• Primary Examiner(s): Pham; Khanh B
• Assistant Examiner(s): LODHI, ANDALIB FT
• Application Number:
  US11/206,496
• Publication Number:
  US 20070043787A1
• Time in Patent Office: 1,581 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/1873 Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

Provided are a method, system, and program for maintaining an aggregate including active files in a storage pool in a random access medium. An active-only storage pool is configured in a random access device. The active-only storage pool is intended to include only active files and not inactive versions of files. A plurality of files in the active-only storage pool are associated with a precursor aggregate in the active-only storage pool. One file associated with the precursor aggregate in the active only storage pool is deactivated to produce an inactive version of the deactivated file. The precursor aggregate is associated with the inactive version of the file in response to the deactivation. A determination is made of the inactive version of at least one file in the precursor aggregate. The determined inactive version of the at least one file is deleted from the active only storage pool.

Claims

1. A method, comprising:

providing an active-only storage pool in a random access device, wherein the active-only storage pool is intended to include only active files and not inactive versions of files;

associating a plurality of files in the active-only storage pool with a precursor aggregate in the active-only storage pool, wherein the precursor aggregate comprises a logical entity providing an association of files;

deactivating one file associated with the precursor aggregate in the active only storage pool to produce an inactive version of the deactivated file, wherein the precursor aggregate is associated with the inactive version of the file in response to the deactivation;

determining the inactive version of at least one file in the precursor aggregate;

copying the files associated with the precursor aggregate to an aggregate managed file in an additional storage pool, wherein the aggregate managed file maintains the inactive version of the at least one file deleted from the active only storage pool, wherein files are maintained in a sequential ordering in the aggregate managed file and wherein the files in the aggregate managed file are written sequentially;

determining whether an inactive file in the precursor aggregate in the active-only storage pool is inactive and has been copied to the aggregate managed file in the additional storage pool;

deleting the determined inactive version of the file from the active only storage pool and the precursor aggregate association in response to determining that the inactive file was copied to the aggregate managed file in which files are maintained in the sequential ordering and

maintaining aggregate information for the aggregate managed file and the precursor aggregate, wherein the information for each of the aggregate managed file and the precursor aggregate indicates the aggregate managed file or precursor aggregate identifier, a number of files in the aggregate managed file or associated with the precursor aggregate, and a field indicating a size of the aggregate managed file or an indication of a precursor aggregate.

2. The method of claim 1, wherein the file is deactivated as a result of an update to the file, wherein updating the file produces an active version of the file in addition to the inactive version of the file, further comprising:

removing an indication of the association of the deleted inactive version of the at least one file with the precursor aggregate, wherein the precursor aggregate is associated with only the active version of files in response to removing the indication.

3. The method of claim 1, wherein the additional storage pool is implemented in a sequential access device.

4. The method of claim 1, wherein the precursor aggregate has a first identifier and the aggregate managed file has a second identifier, further comprising:

providing a data structure having information on defined aggregates including an aggregate identifier and storage pool including the aggregate for each indicated aggregate; and

indicating in the information for the aggregate identified by one aggregate identifier whether the aggregate is a precursor aggregate comprising an association of files or an aggregate managed file in which files are written.

5. The method of claim 4, wherein indicating in the data structure information that the aggregate is the precursor aggregate comprises indicating that the precursor aggregate has an aggregate size of zero and wherein indicating in the information that the aggregate is the aggregate managed file comprises indicating that the aggregate managed file has an aggregate size that is a cumulative size of the files written in the aggregate managed file.

6. The method of claim 5, wherein the information for each aggregate in the data structure includes a logical size and an actual size, wherein indicating that the precursor aggregate has the aggregate size of zero comprises indicating that the actual size of the precursor aggregate is zero and wherein indicating that the aggregate managed file has the aggregate size that is the cumulative size comprises indicating that the actual size of the aggregate managed file is the cumulative size, further comprising:

indicating in the information for the precursor aggregate and the aggregate managed file that the logical size is the cumulative size of the files associated with the precursor aggregate and written to the aggregate managed file, respectively.

7. The method of claim 4, wherein the file is deactivated as a result of an update to the file, wherein updating the file produces an active version of the file in addition to the inactive version of the file, farther comprising:

adding information to the data structure for the updated file having a third identifier and indicating that the updated file is in the active-only storage pool.

8. The method of claim 4, wherein the data structure comprises a first data structure, further comprising:

providing a second data structure having information on each file grouped in one aggregate including the aggregate identifier of the aggregate including the file, wherein the aggregate identifier for the files associated with the precursor aggregate comprises the first identifier and wherein the aggregate identifier for the files written to the aggregate managed file comprises the second identifier.

9. The method of claim 8, farther comprising:

deleting the information in the second data structure for the inactive version of the at least one file having the first identifier that was deleted from the active storage pool, wherein the second data structure includes information on the inactive version of the at least one file having the second identifier maintained in the aggregate managed file.

10. The method of claim 8, wherein the information for the files in the second data structure indicates an offset and file size of the file, wherein files associated with one precursor aggregate have an offset of zero and wherein files included in one aggregate managed file have an offset at which the file is stored in the aggregate managed file.

11. The method of claim 1, further comprising:

maintaining aggregate file information having an entry for each file stored in the aggregate managed file or associated with the precursor aggregate, wherein each entry indicates a file identifier, an identifier of the aggregate managed file or the precursor aggregate, and an ordering of the file in the aggregate managed file, wherein the sequential ordering of files in the aggregate managed file is indicated by the order indicated in the entries for the files of the aggregate managed file in the aggregate file information.

12. The method of claim 11, wherein the ordering of the file in the aggregate file information indicates a precursor aggregate for a file associated with the precursor aggregate.

13. The method of claim 11, wherein the order indicated in the entries in the aggregate file information comprises an offset indicating an offset of the file in the aggregate managed file, wherein the files in the aggregate managed file are written according to an order of their offsets indicated in the file entries in the aggregate file information.

14. The method of claim 11, further comprising:

adding entries to the aggregate file information for each file associated with the precursor aggregate copied to the aggregate managed file, wherein each added entry identifies the copied file, the aggregate managed file, identifier, and an order in which the file was written to the aggregate managed file.

15. The method of claim 11, wherein the sequential ordering of the files in the aggregate managed file is indicated in aggregate file information.

16. A system in communication with a random access device, comprising:

a processor;

a computer readable medium including a program executed by the processor to perform operations, the operations comprising;

providing an active-only storage pool in a random access device, wherein the active-only storage pool is intended to include only active files and not inactive versions of files;

associating a plurality of files in the active-only storage pool with a precursor aggregate in the active-only storage pool, wherein the precursor aggregate comprises a logical entity providing an association of files;

deactivating one file associated with the precursor aggregate in the active only storage pool to produce an inactive version of the deactivated file, wherein the precursor aggregate is associated with the inactive version of the file in response to the deactivation;

determining the inactive version of at least one file in the precursor aggregate;

copying the files associated with the precursor aggregate to an aggregate managed file in an additional storage pool, wherein the aggregate managed file maintains the inactive version of the at least one file deleted from the active only storage pool, wherein files are maintained in a sequential ordering in the aggregate managed file, and wherein the files in the aggregate managed file are written sequentially;

determining whether an inactive file in the precursor aggregate in the active-only storage pool is inactive and has been copied to the aggregate managed file in the additional storage pool; and

deleting the determined inactive version of the file from the active only storage pool and the precursor aggregate association in response to determining that the inactive file was copied to the aggregate managed file in which files are maintained in the sequential ordering.

17. The system of claim 16, wherein the file is deactivated as a result of an update to the file, wherein updating the file produces an active version of the file in addition to the inactive version of the file, wherein the operations further comprise:

removing an indication of the association of the deleted inactive version of the at least one file with the precursor aggregate, wherein the precursor aggregate is associated with only the active version of files in response to removing the indication.

18. The system of claim 16, wherein the precursor aggregate has a first identifier and the aggregate managed file has a second identifier, wherein the operations further comprise:

providing a data structure having information on defined aggregates including an aggregate identifier and storage pool including the aggregate for each indicated aggregate; and

indicating in the information for the aggregate identified by one aggregate identifier whether the aggregate is a precursor aggregate comprising an association of files or an aggregate managed file in which files are written.

19. The system of claim 18, wherein indicating in the data structure information that the aggregate is the precursor aggregate comprises indicating that the precursor aggregate has an aggregate size of zero and wherein indicating in the information that the aggregate is the aggregate managed file comprises indicating that the aggregate managed file has an aggregate size that is a cumulative size of the files written in the aggregate managed file.

20. The system of claim 19, wherein the information for each aggregate in the data structure includes a logical size and an actual size, wherein indicating that the precursor aggregate has the aggregate size of zero comprises indicating that the actual size of the precursor aggregate is zero and wherein indicating that the aggregate managed file has the aggregate size that is the cumulative size comprises indicating that the actual size of the aggregate managed file is the cumulative size, wherein the operations further comprise:

indicating in the information for the precursor aggregate and the aggregate managed file that the logical size is the cumulative size of the files associated with the precursor aggregate and written to the aggregate managed file, respectively.

21. The system of claim 18, wherein the file is deactivated as a result of an update to the file, wherein updating the file produces an active version of the file in addition to the inactive version of the file, wherein the operations further comprise:

adding information to the data structure for the updated file having a third identifier and indicating that the updated file is in the active-only storage pool.

22. The system of claim 18, wherein the data structure comprises a first data structure, wherein the operations further comprise:

providing a second data structure having information on each file grouped in one aggregate including the aggregate identifier of the aggregate including the file, wherein the aggregate identifier for the files associated with the precursor aggregate comprises the first identifier and wherein the aggregate identifier for the files written to the aggregate managed file comprises the second identifier.

23. The system of claim 22, wherein the operations further comprise:

deleting the information in the second data structure for the inactive version of the at least one file having the first identifier that was deleted from the active storage pool, wherein the second data structure includes information on the inactive version of the at least one file having the second identifier maintained in the aggregate managed file.

24. The system of claim 16, wherein the operations further comprise:

maintaining aggregate file information having an entry for each file stored in the aggregate managed file or associated with the precursor aggregate, wherein each entry indicates a file identifier, an identifier of the aggregate managed file or the precursor aggregate, and an ordering of the file in the aggregate managed file, wherein the sequential ordering of files in the aggregate managed file is indicated by the order indicated in the entries for the files of the aggregate managed file in the aggregate file information.

25. The system of claim 24, wherein the ordering of the file in the aggregate file information indicates a precursor aggregate for a file associated with the precursor aggregate.

26. The system of claim 24, wherein the order indicated in the entries in the aggregate file information comprises an offset indicating an offset of the file in the aggregate managed file, wherein the files in the aggregate managed file are written according to an order of their offsets indicated in the file entries in the aggregate file information.

27. The system of claim 24, wherein the operations further comprise:

adding entries to the aggregate file information for each file associated with the precursor aggregate copied to the aggregate managed file, wherein each added entry identifies the copied file, the aggregate managed file, identifier, and an order in which the file was written to the aggregate managed file.

28. The system of claim 24, wherein the sequential ordering of the files in the aggregate managed file is indicated in aggregate file information.

29. An article of manufacture comprising a computer readable storage medium having code executed to communicate with a random access device and to perform operations, the operations comprising:

providing an active-only storage pool in a random access device, wherein the active-only storage pool is intended to include only active files and not inactive versions of files;

associating a plurality of files in the active-only storage pool with a precursor aggregate in the active-only storage pool, wherein the precursor aggregate comprises a logical entity providing an association of files;

deactivating one file associated with the precursor aggregate in the active only storage pool to produce an inactive version of the deactivated file, wherein the precursor aggregate is associated with the inactive version of the file in response to the deactivation;

determining the inactive version of at least one file in the precursor aggregate;

copying the files associated with the precursor aggregate to an aggregate managed file in an additional storage pool, wherein the aggregate managed file maintains the inactive version of the at least one file deleted from the active only storage pool, wherein files are maintained in a sequential ordering in the aggregate managed file, and wherein the files in the aggregate managed file are written sequentially;

determining whether an inactive file in the precursor aggregate in the active-only storage pool is inactive and has been copied to the aggregate managed file in the additional storage pool; and

deleting the determined inactive version of the file from the active only storage pool and the precursor aggregate association in response to determining that the inactive file was copied to the aggregate managed file in which files are maintained in the sequential ordering.

30. The article of manufacture of claim 29, wherein the file is deactivated as a result of an update to the file, wherein updating the file produces an active version of the file in addition to the inactive version of the file, wherein the operations further comprise:

removing an indication of the association of the deleted inactive version of the at least one file with the precursor aggregate, wherein the precursor aggregate is associated with only the active version of files in response to removing the indication.

31. The article of manufacture of claim 29, wherein the precursor aggregate has a first identifier and the aggregate managed file has a second identifier, wherein the operations further comprise:

providing a data structure having information on defined aggregates including an aggregate identifier and storage pool including the aggregate for each indicated aggregate; and

indicating in the information for the aggregate identified by one aggregate identifier whether the aggregate is a precursor aggregate comprising an association of files or an aggregate managed file in which files are written.

32. The article of manufacture of claim 31, wherein indicating in the data structure information that the aggregate is the precursor aggregate comprises indicating that the precursor aggregate has an aggregate size of zero and wherein indicating in the information that the aggregate is the aggregate managed file comprises indicating that the aggregate managed file has an aggregate size that is a cumulative size of the files written in the aggregate managed file.

33. The article of manufacture of claim 32, wherein the information for each aggregate in the data structure includes a logical size and an actual size, wherein indicating that the precursor aggregate has the aggregate size of zero comprises indicating that the actual size of the precursor aggregate is zero and wherein indicating that the aggregate managed file has the aggregate size that is the cumulative size comprises indicating that the actual size of the aggregate managed file is the cumulative size, wherein the operations farther comprise:

indicating in the information for the precursor aggregate and the aggregate managed file that the logical size is the cumulative size of the files associated with the precursor aggregate and written to the aggregate managed file, respectively.

34. The article of manufacture of claim 31, wherein the file is deactivated as a result of an update to the file, wherein updating the file produces an active version of the file in addition to the inactive version of the file, wherein the operations further comprise:

adding information to the data structure for the updated file having a third identifier and indicating that the updated file is in the active-only storage pool.

35. The article of manufacture of claim 31, wherein the data structure comprises a first data structure, wherein the operations further comprise:

providing a second data structure having information on each file grouped in one aggregate including the aggregate identifier of the aggregate including the file, wherein the aggregate identifier for the files associated with the precursor aggregate comprises the first identifier and wherein the aggregate identifier for the files written to the aggregate managed file comprises the second identifier.

36. The article of manufacture of claim 35, wherein the operations further comprise:

deleting the information in the second data structure for the inactive version of the at least one file having the first identifier that was deleted from the active storage pool, wherein the second data structure includes information on the inactive version of the at least one file having the second identifier maintained in the aggregate managed file.

37. The article of manufacture of claim 29, wherein the operations further comprise:

maintaining aggregate file information having an entry for each file stored in the aggregate managed file or associated with the precursor aggregate, wherein each entry indicates a file identifier, an identifier of the aggregate managed file or the precursor aggregate, and an ordering of the file in the aggregate managed file, wherein the sequential ordering of files in the aggregate managed file is indicated by the order indicated in the entries for the files of the aggregate managed file in the aggregate file information.

38. The article of manufacture of claim 37, wherein the ordering of the file in the aggregate file information indicates a precursor aggregate for a file associated with the precursor aggregate.

39. The article of manufacture of claim 37, wherein the order indicated in the entries in the aggregate file information comprises an offset indicating an offset of the file in the aggregate managed file, wherein the files in the aggregate managed file are written according to an order of their offsets indicated in the file entries in the aggregate file information.

40. The article of manufacture of claim 37, wherein the operations further comprise:

adding entries to the aggregate file information for each file associated with the precursor aggregate copied to the aggregate managed file, wherein each added entry identifies the copied file, the aggregate managed file, identifier, and an order in which the file was written to the aggregate managed file.

41. The article of manufacture of claim 37, wherein the sequential ordering of the files in the aggregate managed file is indicated in aggregate file information.