← Back to Patent Explorer
US5983239A Expired / Lapsed US ⏱️ 0.0 years remaining

Storage management system with file aggregation supporting multiple aggregated file counterparts

Assignee: International Business Machines Corp
•
Filing: 1997-10-29
•
Granted: 1999-11-09
•
Expires: 2017-10-29
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

Abstract A data storage subsystem employs managed files comprising one or a contiguous aggregation of multiple constituent user files. A mapping table cross-references each managed file with the names and locations of its constituent user files. A storage table cross-references each managed file with its address. Eventually, "deleted-file space" arises as individual user files are deleted from managed files. "Reconstruction" consolidates managed files to regain this wasted space. Reconstruction preferably permits multiple embodiments of a managed file called "siblings". Reconstruction identifies contiguous regions of user files within a managed file, and copies these regions to adjacent locations in a target area. Before entering the reconstructed file in any tables, the mapping table is searched for a "paradigm" managed file containing the same user files as the reconstructed file. Finding a paradigm file, the storage table is modified by deleting reference to the pre-reconstruction filename, and adding an entry cross-referencing the paradigm file with the reconstructed file's storage address. Not finding the paradigm file, a new sibling filename is designated for the reconstructed file, an entry is added to the mapping table, cross-referencing the sibling with its constituent user files and their locations within the reconstructed file, reference to the pre-reconstruction file is deleted from the storage table, and an entry is added to the storage table, cross-referencing the sibling with its address. Finally, if the storage table has no other instances of the pre-reconstruction file, reference to the pre-reconstruction file is purged from the mapping table.

Inventors

  • 👤 David Maxwell Cannon

Bibliographic Details

Application Number —
Jurisdiction US
Data Source google_patents
Last Synchronized 2026-11-03 07:14
CPC Classifications
G; G06; G06F; G06F16/00; G06F16/10; G06F16/17; G06F16/1727; Y; Y10; Y10S; Y10S707/00; Y10S707/99951; Y10S707/99952; Y10S707/99953; Y10S707/99955

Claims Analysis

Total Claims: 54
Claim 1
Independent Claim 320 words
A method of reconstructing a managed file originally created with a contiguous aggregation of constituent user files, said deleted-file space arising from deletion of individual user files from the managed file, said managed file residing at a source storage area, the managed file and all constituent user files being represented in (1) a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, and (2) a storage table cross-referencing each managed file with an address in the subsystem containing that managed file, the method comprising: receiving a request to reconstruct a first managed file having an original filename; reconstructing the first managed file by identifying contiguous regions of user files within the first managed file and copying each identified contiguous region to adjacent locations in a target storage area; searching the mapping table for a paradigm managed file having contents identical to the reconstructed first managed file; if the paradigm managed file is found, the paradigm managed file having a paradigm filename, deleting reference in the storage table to the original filename; and in the storage table, adding a new entry cross-referencing the paradigm filename with an address in the subsystem containing the reconstructed managed file; if the paradigm managed file is not found, designating a sibling filename for the reconstructed first managed file; in the mapping table, adding a new entry cross-referencing the sibling filename with all constituent user files and corresponding locations of those user files within the reconstructed first managed file; deleting reference in the storage table to the original filename; and in the storage table, adding a new entry cross-referencing the sibling filename with an address in the subsystem containing the reconstructed managed file; and searching the storage table for the original filename, and if not found, updating the mapping table by deleting reference to the original filename and all data cross-referenced thereto.
Claim 2
Independent Claim 320 words
A method of reconstructing a managed file originally created with a contiguous aggregation of constituent user files, said deleted-file space arising from deletion of individual user files from the managed file, said managed file residing at a source storage area, the managed file and all constituent user files being represented in (1) a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, and (2) a storage table cross-referencing each managed file with an address in the subsystem containing that managed file, the method comprising: receiving a request to reconstruct a first managed file having an original filename; reconstructing the first managed file by identifying contiguous regions of user files within the first managed file and copying each identified contiguous region to adjacent locations in a target storage area; searching the mapping table for a paradigm managed file having contents identical to the reconstructed first managed file; if the paradigm managed file is found, the paradigm managed file having a paradigm filename, deleting reference in the storage table to the original filename; and in the storage table, adding a new entry cross-referencing the paradigm filename with an address in the subsystem containing the reconstructed managed file; if the paradigm managed file is not found, designating a sibling filename for the reconstructed first managed file; in the mapping table, adding a new entry cross-referencing the sibling filename with all constituent user files and corresponding locations of those user files within the reconstructed first managed file; deleting reference in the storage table to the original filename; and in the storage table, adding a new entry cross-referencing the sibling filename with an address in the subsystem containing the reconstructed managed file; and searching the storage table for the original filename, and if not found, updating the mapping table by deleting reference to the original filename and all data cross-referenced thereto.
Claim 3
Dependent Claim 17 words
The method of claim 1, the source and target storage areas having no storage space in common.
Claim 4
Dependent Claim 13 words
The method of claim 1, the source and target storage areas substantially overlapping.
Claim 5
Dependent Claim 93 words
The method of claim 1, where: the method further comprises maintaining a managed file attributes table including a representation of each managed file along with the managed file's occupied space and active space, said active space being the occupied space reduced by any deleted-file space; and the searching of the mapping table for a paradigm managed file having contents substantially identical to the reconstructed first managed file comprises: searching the mapping table for a paradigm managed file with (1) same constituent user files as the reconstructed managed file, and (2) no deleted-file space.
Claim 6
Independent Claim 145 words
A method of processing requests to access a storage subsystem that maintains managed files each originally created with a contiguous aggregation of constituent user files, each managed file and all constituent user files therein being represented in a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, the method comprising: receiving a request to restore a first managed file to the storage subsystem; utilizing the mapping table to identify a user file occupying a predetermined position in the first managed file; utilizing the mapping table to identify all managed files containing the identified user file; if one or more managed files other than the first managed file are identified, using predetermined criteria to select one of the identified managed files and restoring the first managed file from the selected managed file.
Claim 7
Independent Claim 145 words
A method of processing requests to access a storage subsystem that maintains managed files each originally created with a contiguous aggregation of constituent user files, each managed file and all constituent user files therein being represented in a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, the method comprising: receiving a request to restore a first managed file to the storage subsystem; utilizing the mapping table to identify a user file occupying a predetermined position in the first managed file; utilizing the mapping table to identify all managed files containing the identified user file; if one or more managed files other than the first managed file are identified, using predetermined criteria to select one of the identified managed files and restoring the first managed file from the selected managed file.
Claim 8
Dependent Claim 20 words
The method of claim 5, the predetermined position being a first-ordered position among user files in the first managed file.
Claim 9
Dependent Claim 21 words
The method of claim 5, the predetermined criteria selecting an identified managed file in response to manual designation by a user.
Claim 10
Dependent Claim 14 words
The method of claim 5, the predetermined criteria selecting a non-busy identified managed file.
Claim 11
Dependent Claim 28 words
The method of claim 5, the predetermined criteria selecting an identified managed file according to read access speeds of storage devices accessing the managed files in the subsystem.
Claim 12
Independent Claim 113 words
A method of processing requests to access a storage subsystem that maintains managed files each originally created with a contiguous aggregation of constituent user files, each managed file and all constituent user files therein being represented in a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, the method comprising: receiving a request to delete a first user file from the storage subsystem; utilizing the mapping table to identify all managed files containing the first user file; and if one or more managed files are identified, updating the mapping table by deleting each entry referencing the first user file.
Claim 13
Independent Claim 113 words
A method of processing requests to access a storage subsystem that maintains managed files each originally created with a contiguous aggregation of constituent user files, each managed file and all constituent user files therein being represented in a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, the method comprising: receiving a request to delete a first user file from the storage subsystem; utilizing the mapping table to identify all managed files containing the first user file; and if one or more managed files are identified, updating the mapping table by deleting each entry referencing the first user file.
Claim 14
Independent Claim 125 words
A method of processing requests to access a storage subsystem that maintains managed files each originally created with a contiguous aggregation of constituent user files, each managed file and all constituent user files therein being represented in a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, the method comprising: receiving a request to retrieve a first user file from the storage subsystem; utilizing the mapping table to identify all managed files containing the first user file; and if one or more managed files are identified, using predetermined criteria to select one of the identified managed files and providing an output of the first user file from the selected managed file.
Claim 15
Independent Claim 125 words
A method of processing requests to access a storage subsystem that maintains managed files each originally created with a contiguous aggregation of constituent user files, each managed file and all constituent user files therein being represented in a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, the method comprising: receiving a request to retrieve a first user file from the storage subsystem; utilizing the mapping table to identify all managed files containing the first user file; and if one or more managed files are identified, using predetermined criteria to select one of the identified managed files and providing an output of the first user file from the selected managed file.
Claim 16
Dependent Claim 21 words
The method of claim 11, the predetermined criteria selecting an identified managed file in response to manual designation by a user.
Claim 17
Dependent Claim 14 words
The method of claim 11, the predetermined criteria selecting a non-busy identified managed file.
Claim 18
Dependent Claim 28 words
The method of claim 11, the predetermined criteria selecting an identified managed file according to read access speeds of storage devices accessing the managed files in the subsystem.
Claim 19
Dependent Claim 338 words
A signal-bearing medium tangibly embodying a program of machine-readable instructions executable by a digital processing apparatus to perform a method for reconstructing a managed file originally created with a contiguous aggregation of constituent user files, said deleted-file space arising from deletion of individual user files from the managed file, said managed file residing at a source storage area, the managed file and all constituent user files being represented in (1) a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, and (2) a storage table cross-referencing each managed file with an address in the subsystem containing that managed file, the method comprising: receiving a request to reconstruct a first managed file having an original filename; reconstructing the first managed file by identifying contiguous regions of user files within the first managed file and copying each identified contiguous region to adjacent locations in a target storage area; searching the mapping table for a paradigm managed file having contents identical to the reconstructed first managed file; if the paradigm managed file is found, the paradigm managed file having a paradigm filename, deleting reference in the storage table to the original filename; and in the storage table, adding a new entry cross-referencing the paradigm filename with an address in the subsystem containing the reconstructed managed file; if the paradigm managed file is not found, designating a sibling filename for the reconstructed first managed file; in the mapping table, adding a new entry cross-referencing the sibling filename with all constituent user files and corresponding locations of those user files within the reconstructed first managed file; deleting reference in the storage table to the original filename; and in the storage table, adding a new entry cross-referencing the sibling filename with an address in the subsystem containing the reconstructed managed file; and searching the storage table for the original filename, and if not found, updating the mapping table by deleting reference to the original filename and all data cross-referenced thereto.
Claim 20
Dependent Claim 338 words
A signal-bearing medium tangibly embodying a program of machine-readable instructions executable by a digital processing apparatus to perform a method for reconstructing a managed file originally created with a contiguous aggregation of constituent user files, said deleted-file space arising from deletion of individual user files from the managed file, said managed file residing at a source storage area, the managed file and all constituent user files being represented in (1) a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, and (2) a storage table cross-referencing each managed file with an address in the subsystem containing that managed file, the method comprising: receiving a request to reconstruct a first managed file having an original filename; reconstructing the first managed file by identifying contiguous regions of user files within the first managed file and copying each identified contiguous region to adjacent locations in a target storage area; searching the mapping table for a paradigm managed file having contents identical to the reconstructed first managed file; if the paradigm managed file is found, the paradigm managed file having a paradigm filename, deleting reference in the storage table to the original filename; and in the storage table, adding a new entry cross-referencing the paradigm filename with an address in the subsystem containing the reconstructed managed file; if the paradigm managed file is not found, designating a sibling filename for the reconstructed first managed file; in the mapping table, adding a new entry cross-referencing the sibling filename with all constituent user files and corresponding locations of those user files within the reconstructed first managed file; deleting reference in the storage table to the original filename; and in the storage table, adding a new entry cross-referencing the sibling filename with an address in the subsystem containing the reconstructed managed file; and searching the storage table for the original filename, and if not found, updating the mapping table by deleting reference to the original filename and all data cross-referenced thereto.
Claim 21
Dependent Claim 17 words
The medium of claim 15, the source and target storage areas having no storage space in common.
Claim 22
Dependent Claim 13 words
The medium of claim 15, the source and target storage areas substantially overlapping.
Claim 23
Dependent Claim 93 words
The medium of claim 15, where: the method further comprises maintaining a managed file attributes table including a representation of each managed file along with the managed file's occupied space and active space, said active space being the occupied space reduced by any deleted-file space; and the searching of the mapping table for a paradigm managed file having contents substantially identical to the reconstructed first managed file comprises: searching the mapping table for a paradigm managed file with (1) same constituent user files as the reconstructed managed file, and (2) no deleted-file space.
Claim 24
Dependent Claim 146 words
A signal-bearing medium of processing requests to access a storage subsystem that maintains managed files each originally created with a contiguous aggregation of constituent user files, each managed file and all constituent user files therein being represented in a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, the method comprising: receiving a request to restore a first managed file to the storage subsystem; utilizing the mapping table to identify a user file occupying a predetermined position in the first managed file; utilizing the mapping table to identify all managed files containing the identified user file; if one or more managed files other than the first managed file are identified, using predetermined criteria to select one of the identified managed files and restoring the first managed file from the selected managed file.
Claim 25
Dependent Claim 146 words
A signal-bearing medium of processing requests to access a storage subsystem that maintains managed files each originally created with a contiguous aggregation of constituent user files, each managed file and all constituent user files therein being represented in a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, the method comprising: receiving a request to restore a first managed file to the storage subsystem; utilizing the mapping table to identify a user file occupying a predetermined position in the first managed file; utilizing the mapping table to identify all managed files containing the identified user file; if one or more managed files other than the first managed file are identified, using predetermined criteria to select one of the identified managed files and restoring the first managed file from the selected managed file.
Claim 26
Dependent Claim 20 words
The medium of claim 19, the predetermined position being a first-ordered position among user files in the first managed file.
Claim 27
Dependent Claim 21 words
The medium of claim 19, the predetermined criteria selecting an identified managed file in response to manual designation by a user.
Claim 28
Dependent Claim 14 words
The medium of claim 19, the predetermined criteria selecting a non-busy identified managed file.
Claim 29
Dependent Claim 28 words
The medium of claim 19, the predetermined criteria selecting an identified managed file according to read access speeds of storage devices accessing the managed files in the subsystem.
Claim 30
Dependent Claim 114 words
A signal-bearing medium of processing requests to access a storage subsystem that maintains managed files each originally created with a contiguous aggregation of constituent user files, each managed file and all constituent user files therein being represented in a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, the method comprising: receiving a request to delete a first user file from the storage subsystem; utilizing the mapping table to identify all managed files containing the first user file; and if one or more managed files are identified, updating the mapping table by deleting each entry referencing the first user file.
Claim 31
Dependent Claim 114 words
A signal-bearing medium of processing requests to access a storage subsystem that maintains managed files each originally created with a contiguous aggregation of constituent user files, each managed file and all constituent user files therein being represented in a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, the method comprising: receiving a request to delete a first user file from the storage subsystem; utilizing the mapping table to identify all managed files containing the first user file; and if one or more managed files are identified, updating the mapping table by deleting each entry referencing the first user file.
Claim 32
Dependent Claim 127 words
A signal-bearing medium of processing requests to access a storage subsystem that maintains managed files each originally created with a contiguous aggregation of constituent user files, each managed file and all constituent user files therein being represented in a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, and the method comprising: receiving a request to retrieve a first user file from the storage subsystem; utilizing the mapping table to identify all managed files containing the first user file; and if one or more managed files are identified, using predetermined criteria to select one of the identified managed files and providing an output of the first user file from the selected managed file.
Claim 33
Dependent Claim 127 words
A signal-bearing medium of processing requests to access a storage subsystem that maintains managed files each originally created with a contiguous aggregation of constituent user files, each managed file and all constituent user files therein being represented in a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file, and the method comprising: receiving a request to retrieve a first user file from the storage subsystem; utilizing the mapping table to identify all managed files containing the first user file; and if one or more managed files are identified, using predetermined criteria to select one of the identified managed files and providing an output of the first user file from the selected managed file.
Claim 34
Dependent Claim 21 words
The medium of claim 25, the predetermined criteria selecting an identified managed file in response to manual designation by a user.
Claim 35
Dependent Claim 14 words
The medium of claim 25, the predetermined criteria selecting a non-busy identified managed file.
Claim 36
Dependent Claim 28 words
The medium of claim 25, the predetermined criteria selecting an identified managed file according to read access speeds of storage devices accessing the managed files in the subsystem.
Claim 37
Dependent Claim 376 words
A data storage subsystem, comprising: a storage including a source storage area and a target storage area, said source storage area containing one or more managed files each including one or an aggregation of multiple constituent user files; a database, including (1) a mapping table cross-referencing each managed file with each constituent user file and a corresponding location of that user file within the managed file, and (2) a storage table cross-referencing each managed file with an address in the subsystem containing that managed file; and a digital data processing apparatus coupled to the storage and the database; wherein the digital data processing apparatus is programmed to perform a method for reconstructing a managed file originally created with a contiguous aggregation of constituent user files, said managed file containing deleted-file space arising from deletion of individual user files from the managed file, said managed file residing in the source storage area, the method comprising: receiving a request to reconstruct a first managed file having an original filename; reconstructing the first managed file by identifying contiguous regions of user files within the first managed file and copying each identified contiguous region to adjacent locations in a target storage area; searching the mapping table for a paradigm managed file having contents identical to the reconstructed first managed file; if the paradigm managed file is found, the paradigm managed file having a paradigm filename, deleting reference in the storage table to the original filename; and in the storage table, adding a new entry cross-referencing the paradigm filename with an address in the subsystem containing the reconstructed managed file; if the paradigm managed file is not found, designating a sibling filename for the reconstructed first managed file; in the mapping table, adding a new entry cross-referencing the sibling filename with all constituent user files and corresponding locations of those user files within the reconstructed first managed file; deleting reference in the storage table to the original filename; and in the storage table, adding a new entry cross-referencing the sibling filename with an address in the subsystem containing the reconstructed managed file; and searching the storage table for the original filename, and if not found, updating the mapping table by deleting reference to the original filename and all data cross-referenced thereto.
Claim 38
Dependent Claim 376 words
A data storage subsystem, comprising: a storage including a source storage area and a target storage area, said source storage area containing one or more managed files each including one or an aggregation of multiple constituent user files; a database, including (1) a mapping table cross-referencing each managed file with each constituent user file and a corresponding location of that user file within the managed file, and (2) a storage table cross-referencing each managed file with an address in the subsystem containing that managed file; and a digital data processing apparatus coupled to the storage and the database; wherein the digital data processing apparatus is programmed to perform a method for reconstructing a managed file originally created with a contiguous aggregation of constituent user files, said managed file containing deleted-file space arising from deletion of individual user files from the managed file, said managed file residing in the source storage area, the method comprising: receiving a request to reconstruct a first managed file having an original filename; reconstructing the first managed file by identifying contiguous regions of user files within the first managed file and copying each identified contiguous region to adjacent locations in a target storage area; searching the mapping table for a paradigm managed file having contents identical to the reconstructed first managed file; if the paradigm managed file is found, the paradigm managed file having a paradigm filename, deleting reference in the storage table to the original filename; and in the storage table, adding a new entry cross-referencing the paradigm filename with an address in the subsystem containing the reconstructed managed file; if the paradigm managed file is not found, designating a sibling filename for the reconstructed first managed file; in the mapping table, adding a new entry cross-referencing the sibling filename with all constituent user files and corresponding locations of those user files within the reconstructed first managed file; deleting reference in the storage table to the original filename; and in the storage table, adding a new entry cross-referencing the sibling filename with an address in the subsystem containing the reconstructed managed file; and searching the storage table for the original filename, and if not found, updating the mapping table by deleting reference to the original filename and all data cross-referenced thereto.
Claim 39
Dependent Claim 17 words
The subsystem of claim 29, the source and target storage areas having no storage space in common.
Claim 40
Dependent Claim 13 words
The subsystem of claim 29, the source and target storage areas substantially overlapping.
Claim 41
Dependent Claim 93 words
The subsystem of claim 29, where: the method further comprises maintaining a managed file attributes table including a representation of each managed file along with the managed file's occupied space and active space, said active space being the occupied space reduced by any deleted-file space; and the searching of the mapping table for a paradigm managed file having contents substantially identical to the reconstructed first managed file comprises: searching the mapping table for a paradigm managed file with (1) same constituent user files as the reconstructed managed file, and (2) no deleted-file space.
Claim 42
Dependent Claim 180 words
A data storage subsystem, comprising: a storage including a source storage area and a target storage area, said storage containing one or more managed files each originally created with a contiguous aggregation of constituent user files; a database, including a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file; a digital data processing apparatus coupled to the storage and the database; wherein the digital data processing apparatus is programmed to perform a method for processing requests to access data in the storage, the method comprising: receiving a request to restore a first managed file to the storage subsystem; utilizing the mapping table to identify a user file occupying a predetermined position in the first managed file; utilizing the mapping table to identify all managed files containing the identified user file; if one or more managed files other than the first managed file are identified, using predetermined criteria to select one of the identified managed files and restoring the first managed file from the selected managed file.
Claim 43
Dependent Claim 180 words
A data storage subsystem, comprising: a storage including a source storage area and a target storage area, said storage containing one or more managed files each originally created with a contiguous aggregation of constituent user files; a database, including a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file; a digital data processing apparatus coupled to the storage and the database; wherein the digital data processing apparatus is programmed to perform a method for processing requests to access data in the storage, the method comprising: receiving a request to restore a first managed file to the storage subsystem; utilizing the mapping table to identify a user file occupying a predetermined position in the first managed file; utilizing the mapping table to identify all managed files containing the identified user file; if one or more managed files other than the first managed file are identified, using predetermined criteria to select one of the identified managed files and restoring the first managed file from the selected managed file.
Claim 44
Dependent Claim 20 words
The subsystem of claim 33, the predetermined position being a first-ordered position among user files in the first managed file.
Claim 45
Dependent Claim 21 words
The subsystem of claim 33, the predetermined criteria selecting an identified managed file in response to manual designation by a user.
Claim 46
Dependent Claim 14 words
The subsystem of claim 33, the predetermined criteria selecting a non-busy identified managed file.
Claim 47
Dependent Claim 28 words
The subsystem of claim 33, the predetermined criteria selecting an identified managed file according to read access speeds of storage devices accessing the managed files in the subsystem.
Claim 48
Dependent Claim 148 words
A data storage subsystem, comprising: a storage including a source storage area and a target storage area, said storage containing one or more managed files each originally created with a contiguous aggregation of constituent user files; a database, including a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file; a digital data processing apparatus coupled to the storage and the database; wherein the digital data processing apparatus is programmed to perform a method for processing requests to access data in the storage, the method comprising: receiving a request to delete a first user file from the storage subsystem; utilizing the mapping table to identify all managed files containing the first user file; and if one or more managed files are identified, updating the mapping table by deleting each entry referencing the first user file.
Claim 49
Dependent Claim 148 words
A data storage subsystem, comprising: a storage including a source storage area and a target storage area, said storage containing one or more managed files each originally created with a contiguous aggregation of constituent user files; a database, including a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file; a digital data processing apparatus coupled to the storage and the database; wherein the digital data processing apparatus is programmed to perform a method for processing requests to access data in the storage, the method comprising: receiving a request to delete a first user file from the storage subsystem; utilizing the mapping table to identify all managed files containing the first user file; and if one or more managed files are identified, updating the mapping table by deleting each entry referencing the first user file.
Claim 50
Dependent Claim 160 words
A data storage subsystem, comprising: a storage including a source storage area and a target storage area, said storage containing one or more managed files each originally created with a contiguous aggregation of constituent user files; a database, including a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file; a digital data processing apparatus coupled to the storage and the database; wherein the digital data processing apparatus is programmed to perform a method for processing requests to access data in the storage, the method comprising: receiving a request to retrieve a first user file from the storage subsystem; utilizing the mapping table to identify all managed files containing the first user file; and if one or more managed files are identified, using predetermined criteria to select one of the identified managed files and providing an output of the first user file from the selected managed file.
Claim 51
Dependent Claim 160 words
A data storage subsystem, comprising: a storage including a source storage area and a target storage area, said storage containing one or more managed files each originally created with a contiguous aggregation of constituent user files; a database, including a mapping table cross-referencing each managed file with its constituent user files and a corresponding location of each user file within the managed file; a digital data processing apparatus coupled to the storage and the database; wherein the digital data processing apparatus is programmed to perform a method for processing requests to access data in the storage, the method comprising: receiving a request to retrieve a first user file from the storage subsystem; utilizing the mapping table to identify all managed files containing the first user file; and if one or more managed files are identified, using predetermined criteria to select one of the identified managed files and providing an output of the first user file from the selected managed file.
Claim 52
Dependent Claim 21 words
The subsystem of claim 39, the predetermined criteria selecting an identified managed file in response to manual designation by a user.
Claim 53
Dependent Claim 14 words
The subsystem of claim 39, the predetermined criteria selecting a non-busy identified managed file.
Claim 54
Dependent Claim 28 words
The subsystem of claim 39, the predetermined criteria selecting an identified managed file according to read access speeds of storage devices accessing the managed files in the subsystem.

USPTO Annuity & Maintenance Windows

Annuity Stage Window Opens Payment Deadline Surcharge Period Until Estimated Fee Status
3.5 Years (Year 4) 2002-11-08 2003-05-10 2003-11-09 $2000.00 Window Closed / Lapsed
7.5 Years (Year 8) 2006-11-08 2007-05-10 2007-11-09 $3760.00 Window Closed / Lapsed
11.5 Years (Year 12) 2010-11-08 2011-05-10 2011-11-09 $7700.00 Window Closed / Lapsed

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag