Management of file system snapshots

• US 20060271604A1
• Filed: 04/19/2006
• Published: 11/30/2006
• Est. Priority Date: 07/08/2003
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Pillar Data Systems, Inc. (Oracle Corporation)
• Inventors: Shoens, Kurt Alan
• Granted Patent: US 7,379,954 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/128 Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion use of snapshots for error detection or correction G06F11/14, G06F11/16
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99956 File allocation

Abstract

The present invention relates to methods and systems of snapshot management of a file system in a data storage system. To represent the snapshots, the invention maintains pointers to the root block pointer of each snapshot. When the active file system is modified, this invention avoids overwriting any blocks used by previous snapshots by allocating new blocks for the modified blocks. When the invention needs to put an established block in a new location, it must update a parent block to point to the new location. The update to the parent block may then require allocating a new block for the new parent block and so forth. Parts of the file system not modified since a snapshot remain in place. The amount of space required to represent snapshots scales with the fraction of the file system that users modify. To maintain snapshot integrity, this invention keeps track of the first and last snapshots that use each block in space map blocks spread throughout the file system data space. When users delete snapshots, this invention may use a background process to find blocks no longer used by any snapshot and makes them available for future use.

Claims

1. A method of snapshot management in a data storage system that maintains multiple snapshot versions and an active file system, comprising:

(a) maintaining a space map block entry (b, e), wherein b and e represent index table entries, b indicates a first snapshot that uses a first block, and e indicates a last snapshot that uses the first block; and

(b) maintaining a snapspace matrix that counts the occurrences of (b, e) for every space map block entry.

2. The method of claim 1, further comprising:

(c) allocating a second block;

(d) writing the data in the second block;

(e) updating any other blocks that pointed to the first block to point to the second block;

(f) updating the snapspace matrix to account for allocation of the second block; and

(g) repeating the steps (c) through (f) for updating other blocks.

3. A method of claim 1, further comprising:

(c) ordering an index table that contains an entry for each snapshot and the active file system by time of snapshot creation;

(d) reading each space map block entry to determine if the first snapshot was deleted and if so, replacing the index b with the earliest index of a later undeleted snapshot or the active file system, determining if the last snapshot was deleted and if so, replacing the index e with the latest index of an earlier undeleted snapshot to clean deleted snapshots and decrementing the snapspace matrix entry corresponding to the original values of index b and index e and incrementing the snapspace matrix entry corresponding to the new values of index b and index e.

4. The method of claim 1, further comprising:

(c) calculating the space occupied by a set of snapshots by summing the snapspace entries corresponding to space map block entries used only by the set of snapshots.

5. The method of claim 1, further comprising:

(c) presenting a list of snapshots to a user;

(d) accepting a set of proposed snapshots to delete;

(e) calculating the space occupied by the set of proposed snapshots to delete by summing the snapspace entries corresponding to space map block entries used only by the proposed set of snapshots to delete; and

(f) presented the amount of space that deleting the proposed set of snapshots will free.

6. The method of claim 5, further comprising:

(g) accepting a command from the user to delete the snapshots; and

(h) deleting the proposed set of snapshots.

7. A snapshot management system including a processor for maintaining multiple snapshot versions and an active file system, comprising:

an index table that contains an entry for each snapshot and the active file system;

a space map block entry (b, e), wherein b and e represent index table entries, b indicates a first snapshot that uses the first block, and e indicates a last snapshot that uses the first block; and

a usable space for storing the snapshot versions and the active file system.

8. The system of claim 7, wherein the processor is programmed to execute steps of:

allocating a second block;

writing the data in the second block;

updating any other blocks that pointed to the first block to point to the second block; and

repeating the above steps for updating other blocks.

9. The system of claim 7, wherein the processor is programmed to execute steps:

ordering the index table by time of snapshot creation;

reading each space map block entry to determine if the first snapshot was deleted and if so, replacing the index b with the earliest index of a later undeleted snapshot or the active file system, determining if the last snapshot was deleted and if so, replacing the index e with the latest index of an earlier undeleted snapshot to clean deleted snapshots.

10. The system of claim 9, wherein the processor is programmed to set the space map block entry to indicate the associated block is free if no undeleted snapshot exists earlier than index e or if index b is later than index e.

11. The system of claim 9, wherein the processor is programmed to set the space map block entry to indicate that the associated block is free if no undeleted snapshot exists earlier than index e or if index b is later than index e.

12. A snapshot management system that maintains multiple snapshot versions and an active file system, comprising:

means for maintaining an index table that contains an entry for each snapshot and the active file system; and

means for maintaining space map block entry (b, e), wherein b and e represent index table entries, b indicates a first snapshot that uses the first block, and e indicates a last snapshot that uses the first block.

13. The system of claim 12, further comprising:

means for allocating a second block;

means for writing the data in the second block;

means for updating any other blocks that pointed to the first block to point to the second block; and

means for repeating the above steps for updating other blocks.

14. The system of claim 12, further comprising:

means for ordering the index table by time of snapshot creation; and

means for reading each space map block entry to determine if the first snapshot was deleted and if so, replacing the index b with the earliest index of a later undeleted snapshot or the active file system, determining if the last snapshot was deleted and if so, replacing the index e with the latest index of an earlier undeleted snapshot to clean deleted snapshots.

15. The system of claim 14, further comprising means for setting the space map block entry to indicate that the associated block is free if no undeleted snapshot exists earlier than index e or if index b is later than index e.

16. The system of claim 12, further comprising:

means for maintaining in the index table an image state that indicates if an entry is obsolete or not;

means for reading a snapshot c;

means for reading a snapshot p;

means for reading each space map block entry to determine;

(a) if the first snapshot is snapshot p or earlier than snapshot p and the last snapshot is earlier than snapshot c, replacing the index e with a value indicating that the block is still in use by the active file system,

(b) if the first snapshot is later than snapshot p and earlier than snapshot c, setting the space map block entry to indicate that the associated block is free;

means for marking the image state of snapshot c as deleted; and

means for resetting the image state of all obsolete index table entries to free to clean obsolete snapshots after a revert operation to snapshot p.