COMPACTING DISPERSED STORAGE SPACE

• US 20120110038A1
• Filed: 10/11/2011
• Published: 05/03/2012
• Est. Priority Date: 02/27/2010
• Status: Active Grant

• Current Assignee: Cleversafe Incorporated (International Business Machines Corporation)
• Original Assignee: Cleversafe Incorporated (International Business Machines Corporation)
• Inventors: Volvovski, Ilya, Baptist, Andrew, Dhuse, Greg
• Granted Patent: US 10,216,647 B2
• Time in Patent Office: Days
• US Class Current: 707/822
• CPC Class Codes: G06F 12/1408 by using cryptography for digital transmission H04L9/00
• CPC Class Codes: G06F 16/11 File system administration, e.g. details of archiving or snapshots file system backup G06F11/14
• CPC Class Codes: G06F 16/113 Details of archiving lifecycle management in storage systems G06F3/0649; backup systems G06F11/1446
• CPC Class Codes: G06F 16/1734 Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/50 of still image data
• CPC Class Codes: G06F 2212/7205 Cleaning, compaction, garbage collection, erase control
• CPC Class Codes: G06F 3/0652 Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

A method begins by a processing module receiving an encoded data slice for storage in memory that is organized as a plurality of log files and identifying a log file based on information regarding the encoded data slice to produce an identified log file, wherein the identified log file is storing at least one other encoded data slice. The method continues with the processing module comparing storage parameters of the identified log file with desired storage parameters associated with the encoded data slice. The method continues with the processing module attempting to identify a second log file based on an alternate log file storage protocol when the storage parameters of the identified log file compare unfavorably with the desired storage parameters and when the second log file is identified, storing the encoded data slice in the second log file.

Claims

1. A method comprises:

receiving an encoded data slice for storage in memory that is organized as a plurality of log files;

identifying a log file based on information regarding the encoded data slice to produce an identified log file, wherein the identified log file is storing at least one other encoded data slice;

comparing storage parameters of the identified log file with desired storage parameters associated with the encoded data slice; and

when the storage parameters of the identified log file compare unfavorably with the desired storage parameters;

attempting to identify a second log file based on an alternate log file storage protocol; and

when the second log file is identified, storing the encoded data slice in the second log file.

2. The method of claim 1 further comprises:

the comparing of the storage parameters of the identified log file with the desired storage parameters being unfavorable when the identified log file includes a number of storage gaps that compares unfavorably to a gap threshold.

3. The method of claim 1 further comprises:

the comparing of the storage parameters of the identified log file with the desired storage parameters being unfavorable when a storage balance between the identified log file and the second log file compares unfavorably to a storage balance threshold.

4. The method of claim 1 further comprises:

the comparing of the storage parameters of the identified log file with the desired storage parameters being unfavorable when a storage capacity of the identified log file compares unfavorably to a storage threshold.

5. The method of claim 1 further comprises:

the comparing of the storage parameters of the identified log file with the desired storage parameters being favorable when;

the log file is identified as a most recently compacted log file;

the log file is identified as having a favorable amount of available storage space;

the log file is identified in a slice location table lookup;

the log file is predetermined;

or

the log file is identified based on a slice name associated with the encoded data slice.

6. The method of claim 1, wherein the information of encoded data slice comprises at least one of:

a data identifier (ID) of a file associated with the encoded data slice;

a user ID associated with the encoded data slice; and

an indication of the log file contained in a message accompanying the encoded data slice.

7. The method of claim 1 further comprises:

when the second log file is not identified;

creating another log file; and

storing the encoded data slice in the other log file.

8. The method of claim 1 further comprises:

when the storage parameters of the identified log file compare favorably with the desired storage parameters;

identifying a log file offset for an available storage location of the identified log file;

storing the encoded data slice in the identified log file based on log file offset; and

updating a slice location table to include storage of the encoded data slice in the identified log file.

9. A computer comprises:

an interface;

a memory; and

a processing module operable to;

receive, via the interface, an encoded data slice for storage in the memory that is organized as a plurality of log files;

identify a log file based on information regarding the encoded data slice to produce an identified log file, wherein the identified log file is storing at least one other encoded data slice;

compare storage parameters of the identified log file with desired storage parameters associated with the encoded data slice; and

when the storage parameters of the identified log file compare unfavorably with the desired storage parameters;

attempt to identify a second log file based on an alternate log file storage protocol; and

when the second log file is identified, store the encoded data slice in the second log file.

10. The computer of claim 9, wherein the processing module further functions to:

compare the storage parameters of the identified log file with the desired storage parameters as unfavorable when the identified log file includes a number of storage gaps that compares unfavorably to a gap threshold.

11. The computer of claim 9, wherein the processing module further functions to:

compare the storage parameters of the identified log file with the desired storage parameters as unfavorable when a storage balance between the identified log file and the second log file compares unfavorably to a storage balance threshold.

12. The computer of claim 9, wherein the processing module further functions to:

compare the storage parameters of the identified log file with the desired storage parameters as unfavorable when a storage capacity of the identified log file compares unfavorably to a storage threshold.

13. The computer of claim 9, wherein the processing module further functions to:

compare the storage parameters of the identified log file with the desired storage parameters as favorable when;

the log file is identified as a most recently compacted log file;

the log file is identified as having a favorable amount of available storage space;

the log file is identified in a slice location table lookup;

the log file is predetermined;

or

the log file is identified based on a slice name associated with the encoded data slice.

14. The computer of claim 9, wherein the information of encoded data slice comprises at least one of:

a data identifier (ID) of a file associated with the encoded data slice;

a user ID associated with the encoded data slice; and

an indication of the log file contained in a message accompanying the encoded data slice.

15. The computer of claim 9, wherein the processing module further functions to:

when the second log file is not identified;

create another log file; and

store the encoded data slice in the other log file.

16. The computer of claim 9, wherein the processing module further functions to:

when the storage parameters of the identified log file compare favorably with the desired storage parameters;

identify a log file offset for an available storage location of the identified log file;

store the encoded data slice in the identified log file based on log file offset; and

update a slice location table to include storage of the encoded data slice in the identified log file.