Snapshot facility allowing preservation of chronological views on block drives

• US 7,055,010 B2
• Filed: 11/03/2003
• Issued: 05/30/2006
• Est. Priority Date: 11/06/2002
• Status: Expired due to Fees

• Current Assignee: Synology Incorporated
• Original Assignee: Synology Incorporated
• Inventors: Liao, Cheen, Lin, Alvis
• Primary Examiner(s): Bataille, Pierre Michel
• Assistant Examiner(s): PEERS, CHASE W
• Application Number:
  US10/701,129
• Publication Number:
  US 20040093474A1
• Time in Patent Office: 939 Days
• Field of Search: 707/10, 707/200, 707/202, 711/162, 711/152, 711/164, 714/1, 714/5
• US Class Current: 711/162
• CPC Class Codes: G06F 16/1727 Details of free space management performed by the file system saving storage space on storage systems G06F3/0608; management of blocks in storage devices G06F3/064
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A method for efficiently maintaining snapshot instances. To maintain the state of snapshot instances, the snapshot copies the data needed to be protected into free space on the same volume. In order to identify whether a block is free, a snapshot record is created for each block on a volume to record write operations on the block. With these snapshot records, the allocation status of blocks on a volume can quickly be identified. Free space allocation is then accomplished by allocating free space via the file-system provided interface and identifying it with snapshot records. With this mechanism, snapshot software can allocate free space to store snapshot metadata and “copy-to-write” data dynamically.

Claims

1. A product for interfacing with a plurality of file-systems and block devices, said product creating and handling multiple snapshot instances in a computer storage system, the product implementing the process of:

identifying one or more blocks being used;

creating a snapshot record for each of said blocks on a base volume at a first time, wherein creating a snapshot record at the first time further comprises;

(1) suspending all of the write operations issued from file systems;

(2) identifying the blocks called by file systems;

(3) creating a snapshot record for each of the identified blocks;

(4) resuming the write operations issued from the file systems to the said blocks on said base volume;

(5) counting the number of write operations being taken to the said block; and

(6) creating a binding of a copy-on-write block associated with the said block as well as the associated snapshot instances;

performing snapshot management functions to said blocks on said base volume;

handling snapshot records of said blocks on said base volume at a second time; and

allowing writing of data on said blocks to free space on said base volume.

2. The product of claim 1, wherein creating a new snapshot instance comprises:

allocating an unused bit in a counting bitmap to identify the created snapshot instance; and

updating all of the allocated bits in the counting bitmap.

3. The product of claim 1, wherein handling a snapshot record comprises:

suspending the write operation to blocks on base volume;

updating a counting bitmap;

checking the snapshot record to determine whether a copy-on-write operation is needed;

allocating free space on the base volume; and

performing the copy-on-write operation to the allocated block in free space when a copy-on-write is needed;

otherwise, resuming the write operation to blocks on base volume.

4. The product of claim 3, wherein allocating free space on the base volume comprises:

selecting an unused block on the base volume;

identifying the selected block in the snapshot record;

updating block allocation bitmap and snapshot block allocation bitmap of file system.

5. The product of claim 4, wherein allocating free space for storing snapshot records comprises:

dynamic allocating one or more free blocks when size of snapshot record grows and freeing allocating blocks when size of snapshot record shrinks.

6. The product of claim 4, wherein freeing blocks on the base volume further comprises:

marking the freed blocks as unused ones in both the block allocation bitmap and the snapshot block allocation bitmap of file system.

7. The product of claim 1, wherein handling a snapshot instance created on the base volume during a delete operation comprises:

suspending all write operations issued from file system to the base volume;

identifying a counting bit corresponding to the said snapshot instance;

removing unused record of write operation to its associated block;

finding all copy-on-write blocks associated with said snapshot instance;

freeing said copy-on-write blocks when they have no other snapshot instance to associate with;

otherwise, resuming all pending write operations issued from file system to base volume.

8. The product of claim 1, wherein handling a snapshot instance being created on the base volume during a storing operation further comprises:

restraining all write operations issued from file system to said base volume;

identifying all copy-on-write blocks associated with said snapshot instance;

exchanging data on copy-on-write blocks with data on the blocks associated with the snapshot instance;

updating the state of snapshot record;

updating the block allocation bitmap and snapshot block allocation bitmap of file system;

restarting the write operations of the file system to the base volume.

9. The product of claim 8, wherein updating the block allocation bitmap and snapshot block allocation bitmap of a file system comprises:

freeing all blocks being marked as used in the snapshot block allocation bitmap;

marking blocks which are currently used by the product as used in both bitmaps.