Snapshots of file systems in data storage systems

[0001] This is a continuation of U.S. application Ser. No. 11/147,739, filed on Jun. 7, 2005, now U.S. Pat. No. 7,257,606 which is a continuation of U.S. application Ser. No. 10/616,128, filed on Jul. 8, 2003, now U.S. Pat. No. 6,959,313 B2, which are both incorporated by reference herein.

[0002] The present invention relates to snapshots of file systems in data storage systems.

[0003] This application also incorporates by reference herein as follows:

[0004] U.S. application Ser. No. 10/354,797, Methods and Systems of Host Caching, filed on Jan. 29, 2003, now U.S. Pat. No. 6,965,979 B2;

[0005] U.S. application Ser. No. 10/440,347, Methods and Systems of Cache Memory Management and Snapshot Operations, filed on May 16, 2003, now U.S. Pat. No. 7,124,243 B2; and

[0006] U.S. application Ser. No. 10/600,417, Systems and Methods of Data Migration in Snapshot Operations, filed on Jun. 19, 2003, now U.S. Pat. No. 7,136,974 B2.

[0007] Files exist to store information on storage devices (e.g., magnetic disks) and allow the information to be retrieved later. A file system is a collection of files and directories plus operations on them. To keep track of files, file systems have directories. A directory entry provides the information needed to find the blocks associated with a given file. Many file systems today are organized in a general hierarchy (i.e., a tree of directories) because it gives users the ability to organize their files by creating subdirectories. Each file may be specified by giving the absolute path name from the root directory to the file. Every file system contains file attributes such as each file owner and creation time and must be stored somewhere such as in a directory entry.

[0008] A snapshot of a file system will capture the content (i.e., files and directories) at an instant in time. A snapshot results in two data images: (1) the active data that an application can read and write as soon as the snapshot is created and (2) the snapshot data. Snapshots can be taken periodically, hourly, daily, or weekly or on user demand. They are useful for a variety of applications including recovery of earlier versions of a file following an unintended deletion or modification, backup, data mining, or testing of software.

[0009] The need for high data availability often requires frequent snapshots that consume resources such as memory, internal memory bandwidth, storage device capacity and the storage device bandwidth. Some important issues for snapshots of file systems is how to manage the allocation of space in the storage devices, how to keep track of the blocks of a given file, and how to make snapshots of file systems work efficiently and reliably.

[0010] The invention provides methods and systems for management of snapshots of a file system.

[0011] In a first aspect of the invention, a snapshot management system performs a method for managing multiple snapshots and an active file system by (a) maintaining an index table that contains an entry for each snapshot and the active file system; and (b) maintaining space map block entry (b, e) where 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.

[0012] In a second aspect of the invention, a snapshot management system includes a processor for maintaining multiple snapshot versions and an active file system, comprising: (a) an index table that contains an entry for each snapshot and the active file system; (b) a space map block including 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 (c) a usable space for storing the snapshot versions and the active file system.

[0032] The following description includes the best mode of carrying out the invention. The detailed description is made for the purpose of illustrating the general principles of the invention and should not be taken in a limiting sense. The scope of the invention is determined by reference to the claims. Each part is assigned its own part number throughout the specification and drawings.

[0033] FIG. 1 illustrates a data storage system 10, including a plurality of hosts coupled to data storage subsystem(s). Each host is a computer that can connect to client(s), to data storage subsystem(s), and each other. Each host provides software/hardware interfaces such as network interface cards and software drivers to implement Ethernet, Fibre Channel, ATM, and SCSI, and InfiniBand. Hennessy and Patterson, Computer Architecture: A Quantitative Approach (2003), and Patterson and Hennessy, Computer organization and Design: The Hardware/Software Interface (1998) describe computer hardware and software, storage systems, caching, and networks and are incorporated by reference.

[0034] In an embodiment, the first host includes a motherboard with a CPU-memory bus 14 that communicates with dual processors 12 and 41. The processor used is not essential to the invention and could be any suitable processor such as the Intel Pentium 4 processor. A processor could be any suitable general purpose processor running software, an ASIC dedicated to perform the operations described herein or a field programmable gate array (FPGA). Also, one could implement the invention using a single processor in each host or more than two processors to meet more stringent performance requirements. The arrangement of the processors is not essential to the invention.

[0035] The first host cache memory 20 includes a cache manager 13, a cache directory 15, and cache lines 16. The cache memory 20 is nonvolatile memory or volatile memory or a combination of both. Nonvolatile memory protects data in the event of a power interruption or a host failure. Data is defined as including user data, instructions, and metadata. Nonvolatile memory may be implemented with a battery that supplies power to the DRAM to make it nonvolatile memory when a conventional external power interrupt circuit detects a power interruption or with inherently nonvolatile semiconductor memory.

[0036] Each host includes a bus adapter 22 between the CPU-memory bus 14 and an interface bus 24. Each host runs an operating system such as Linux, UNIX, a Windows OS, or another suitable operating system. Tanenbaum, Modern Operating Systems (2001) describes operating systems in detail and is hereby incorporated by reference. The first host is representative of the other hosts, but this feature is not essential to the invention.

[0037] The first host can communicate with the second host through an interconnect 40, shown as connected to an adapter 25 to the interface bus 24. The PCI bus is one suitable interface bus and the interconnect 40 may be any suitable known bus, SAN, LAN, or WAN technology. In an embodiment, the interconnect 40 is a dedicated Fibre Channel (FC) point-to-point link that connects to FC-PCI bus adapter 25 to provide fast point-to-point communication between the hosts.

[0038] In an alternative embodiment, the interconnect network 30 such as a FC fabric provides extra bandwidth for host-to-host communications. In this embodiment, links 28, 38 connect to the interconnect network 30 and the hosts use link 28 and link 38 when available. FC standard software can set priority levels to ensure high priority peer-to-peer requests, but there will still be some arbitration overhead and latency in claiming ownership of the links. For example, if links 28 and 38 are busy transferring data when a write request arrives, that operation must complete before either link is free for arbitration.

[0039] If the interconnect 40 ever fails, communication between hosts can be handled using the interconnect network 30. The interconnect network 30 can be implemented by interconnects used in data storage systems such as Fibre Channel, SCSI, InfiniBand, or Ethernet, and the type of interconnect is not essential to the invention. In either embodiment, redundant communication between hosts ensures the data storage system has high availability. See Clark, IP SANs: A Guide to iSCSI, IFCP, and FCIP Protocols for Storage Area Networks (2002) and Clark, Designing Storage Area Networks (1999) are incorporated herein by reference.

[0040] In an embodiment, the data storage subsystems shown in FIG. 1 can be those described in the co-pending U.S. patent application Ser. No. 10/264,603, entitled, Systems and Methods of Multiple Access Paths to Single Ported Storage Devices, filed on Oct. 3, 2002, and incorporated herein by reference. It is understood, however, that other storage device(s) or data storage subsystems could be used instead of the data storage subsystem described in that U.S. patent application.

[0041] As shown in FIG. 1, the first host connects, or couples, to the first data storage subsystem through the bus adapter 22, the interface bus 24, the adapter 26, the link 28, the interconnection network 30, and the link 32. To connect to the second data storage subsystem, the first host uses the same I/O path except the data passes through link 34, while the second host uses the same type of I/O path plus link 32 to communicate with the first data storage subsystem, or link 34 to communicate with the second data storage subsystem, or link 36 to the data storage subsystem N.

[0042] FIG. 2 illustrates that each host of the data storage system can store and retrieve files from a data storage subsystem 35 using an interconnect 28, an interconnect 33, and an interconnect network 30. In an embodiment, each storage device in the data storage subsystem is assigned a logical unit number (LUN) that is an identifier for the storage device. A virtual logical unit number (VLUN) is as an abstraction of the storage device(s) or the virtualization of the data storage subsystems such as a linear array of blocks as it appears to the data storage system users. In various embodiments, the implementation of a VLUN may be striped (i.e., spread) over multiple RAID groups for added performance, spread over sections of a RAID group for flexibility, or copied on multiple RAID groups for reliability. As shown, the storage devices of the data storage subsystem are virtualized as a file system employing contiguous fixed sized blocks 0-n where the size of each block is some value preferably 1-KB to 64-KB.

[0043] FIG. 3 illustrates a data storage subsystem for maintaining (e.g., allocating, reading, writing, and deallocating) some blocks for index tables, some for space maps, and others for usable space for data storage. The block(s) allocated to an index table depends on the size of each block and the number of concurrent snapshots supported. For example, three 8-KB blocks may be sufficient space to support an index table of 254 snapshots. As shown, the file system has a pair of index tables 195 and 196 and thus uses six 8-KB blocks so the host can alternate writes to the index tables to ensure recovery in case of a data storage system failure. Thus, if the system fails during a write to one index table, the host can retrieve the unmodified copy of the other index table. While we describe this method of writing to alternate index table copies, other methods, such as write journaling, can be used to protect against system failure during index table writes. The remainder of the storage is allocated to space map blocks with usable space for data storage.

[0044] Each index table includes an index value of the active file system 17 permitting fast location of the active file system. The index table includes a known algorithm to verify the data integrity such as a checksum 18, a cyclic redundancy check, or a digital signature. The index table provides an index to the snapshots and the active file system. Each entry in the index table represents a snapshot or the active file system. As illustrated, the index range is 1-255, but this range is not essential to the invention. In various embodiments, each snapshot and the active file system has one or more associated attributes such as a version number 19, timestamp 23 to identify the snapshot or active file system, an image state 21, a root block pointer 27, and an image name 29 as described below.

[0045] When the data storage system takes a snapshot of the file system it assigns the snapshot a unique version number such as a 32-bit unsigned integer that increases monotonically for each subsequent snapshot. The version number is not reused even as snapshots are deleted or made obsolete to the file system.

[0046] The image state can be one of the following states:

• • [0047] Active—representing the active file system
  • [0048] In-use snapshot—representing a snapshot that users can access
  • [0049] Free—representing available for writing by a snapshot or active file system
  • [0050] Deleted snapshot—representing a user has deleted the associated snapshot but a cleaner process or thread has not yet removed the space map block entry for this snapshot
  • [0051] Obsolete snapshot—representing a user has reverted to an earlier snapshot and the cleaner process or thread has not yet removed the space map block entry for this snapshot

[0052] In an embodiment, when the data storage system takes a snapshot of the file system, the host provides a timestamp (e.g., time and date) when the snapshot or active data image was created. The root block pointer provides the address of the root block in the hierarchical structure of the snapshot and the image name is a character string used to easily identify the snapshot to users.

[0053] Referring to FIG. 4, the remainder of the data storage subsystem is allocated to space map blocks and usable space for data. Each space map block keeps track of the blocks in its usable space for data storage. For example, a space map block can keep track of 2,047 blocks of usable space. Each space map block entry contains a pair of indexes (“a space map block entry”), for example, 8-bits in length that represent any of 254 snapshots or the active file system. Each space map block entry is an index into the index table shown in FIG. 3. Each space map block entry has a beginning value b that indicates the first snapshot (i.e., snapshot b) and an ending value e that indicates the last snapshot (i.e., snapshot e) to use the associated block. Thus, each space map block entry (b, e) in the space map block is used to track the usage of an associated block in the usable space:

[0054]

Beginning
Index, b	Ending Index, e	Meaning
0	0	The block is free to use by a snapshot
		or the active file system
8-bit Integer	0	The block is in use by one or more
		snapshots and has not been changed
		since the first snapshot was taken.
		The block is also in use by the active
		file system
a	0	The block is in use by the active file
		system only and there are no
		snapshots associated with the block
8-bit Integer	Another 8-bit	The block is in use by a snapshot and
	Integer	is used by all subsequent snapshots
		through a last snapshot. The data has
		changed since the last snapshot was
		created and is, therefore, no longer in
		use by the active file system

[0055] In an alternative embodiment, each space map block entry contains a pair of version numbers (e.g., 32-bit) that represent snapshots or the active file system. Thus, each version pair (b, e) in the space map block would be used to track the usage of an associated block in the usable space.

[0056] FIG. 5 illustrates how a space map block entry is used to track a block in the usable space. In an earlier stage of operation, the space map may contain many entries with beginning and ending values equal to zero indicating that many blocks in the data storage subsystem are free-to-use for snapshots or the active file system. At the same time, other blocks will be in-use that is allocated to snapshots or the active file system. FIG. 5 shows one such block used by snapshots assigned version number 10344 through version number 10388 inclusive. The space map block entry (16, 13) indicates the snapshots that use this block. The host associates the space map block entry with the version number of the snapshot by reading the index table. The space map block also contains space map block entry (212, 0) to show that the active file system, for example, assigned version number 65993 is using an associated block.

[0057] FIG. 6 illustrates the relationship between the index table 200 and the snapshot attributes and the active file system attributes. The table below illustrates the group of attributes 203, 204, 205, 206, 207, and 208 that are shown in FIG. 6:

[0058]

				Root
Index Table	Version	Image		block	Image
Entry	Number	State	Timestamp	Pointer	Name
Snapshot 1	10344	In-use	4 AM, May 8,	1002	Fred
			2003
Snapshot 3	10388	In-use	10 AM, May 9,	1004	Smokey
			2003
Active File	65993	Active	6 PM, May 14,	1006	Hilda
System		File	2003
		System
Snapshot 5	12608	Deleted	2 PM, Apr. 2,	1008	Rufus
			2003
Snapshot 253	55478	Obsolete	3 AM, May 9,	1010	Vern
			2003
Snapshot 254	0	Free	0	0	0

[0059] FIG. 7 illustrates a flow diagram of a method for creating a file system. This method can occur during the process of initialization. In an embodiment, the initialization process has proceeded to the point where the next steps relate specifically to file system creation. Although the method is described serially below, the steps can be performed in parallel, for example, asynchronously or in a pipelined manner. There is no requirement the method be performed in the order shown except where indicated. Further, the steps are implemented by computer such as one or more host(s) described earlier. For brevity, we describe the methods as executed by a host.

[0060] Referring to step 105 of FIG. 7, the host sets all of the space map block entries equal to (0, 0). This indicates that the blocks corresponding to the entries are free-to-use. At step 106, the host selects an 8-bit index “a” that represents the active file system. At step 108, the host assigns a starting version number to index a. At step 110, the host loads index “a” into the index of the active file system 201 in the directory 200 (FIG. 6). At step 112, the host selects the first available space map block and at step 114 loads the beginning index 8-bit index “a” and an 8-bit ending index 0 into the first entry in the selected space map block. At step 116, the host sets the starting version number in the associated attributes for the active file system in index table entry “a”. The host further sets the image state to active at step 118, the timestamp to the current date and time at step 120, and a starting root block pointer at step 122, calls an algorithm to verify the data integrity (e.g., checksum) of the snapshot attributes, and stores the results in index table entry “a” at step 124. At step 126, the host may write the index table to nonvolatile storage. In one embodiment, at step 128, the host continues with any other activities such as initialization. In another embodiment, the other activities can precede the creation of the file system.

[0061] FIG. 8 illustrates a flow diagram of a method of block management. At step 42, the host receives a request to update the file system data. At step 44, the host reads the space map block entry of the associated received data to determine if that block is used by the active file system only. If yes, as indicated by the space map block entry=(a, 0), the host determines at step 45 whether or not the data is a modification of existing data or an addition to existing data. If the received data is a modification of existing data, the host overwrites the block at step 46 and returns to normal operation at step 58. If the received data is an addition to the existing data, the host determines at step 48 if the space available in the current block is enough to hold all of the received data. If yes, the host adds the received data to the current block at step 50 and returns to normal operation at step 58. If not, the host allocates a free-to-use block at step 52 to hold the additional data and changes the associated space map block entry from (0, 0)→(a, 0). At step 54, the host adds the received data to the newly allocated block. At step 56, the host updates the file system block pointers to point to the new data. At step 58, the block management routine returns to normal system operation.

[0062] At step 44, if the space map block entry of the block associated with the received data indicates an in-use snapshot uses the block, that is, the space map block entry (b, 0), the host allocates a free-to-use block for the received data at step 60. At step 62, the host adds the received data to the new allocated block. At step 63, the host changes the space map block entry of the new allocated block from (0, 0)→(a, 0) indicating the new block is used by the active file system only. At step 64, the host updates the file system block pointers to point to the new data. At step 66, the host determines if there are other in-use snapshots pointing to the same old block. If the index b is associated with the latest snapshot version number, there is no other in-use snapshots pointing to the same old block. Therefore, at step 67, the host updates the old space map block entry from (b, 0)→(b, b) indicating snapshot b is the only snapshot pointing to the associated old block and that the old data has been modified since snapshot b was created. If the index b is not associated with the latest snapshot version number, there is another in-use snapshot pointing to the same old block. Therefore, at step 68, the host updates the old space map block entry from (b, 0)→(b, e) to indicate that snapshot b is the beginning snapshot and snapshot e is the ending snapshot (i.e., current in-use snapshot with the latest snapshot version number) pointing to the associated old block. In this case, there may be other snapshots with version numbers less than snapshot e and greater than snapshot b pointing to the same old block. In either case, the block management routine returns to normal system operation at step 58.

[0063] FIG. 9 illustrates a flow diagram of a method of creating a snapshot. After receiving a request for a new snapshot of the file system, the host holds off from updating the active file system at step 140. At step 142, the host searches through the index table for the first snapshot with an image state equal to free. At step 144, if the host searches the entire index table and does not find a free image state, the routine reports no free snapshots and the host resumes normal file system operation at step 164 and if appropriate, the operator can delete some snapshots. If, at step 144, a free image state is found, the host changes the active file system's image state to in-use at step 148. At step 150, the host enters a timestamp of the new in-use snapshot. When this snapshot is created, the version number and the root block pointer remain as they were when the block was allocated to the active file system. At step 151, the host assigns a user-friendly image name for the in-use snapshot. This completes creation of the new snapshot. Next, the host establishes an active file system for normal use. At step 152, the host changes snapshot attributes containing the image state free to the active file system. At step 154, the host assigns the next version number to the new active file system. At step 156, the host enters the current root block pointer (same as the new snapshot) in the attributes of the active file system. At step 158, the host saves a user-friendly image name of the active file system. The snapshot table is written to nonvolatile storage at step 162. The host returns to normal operation at step 164.

[0064] FIG. 10 illustrates a flow diagram for a method used to revert to an earlier version of a snapshot. FIGS. 15a and 15b illustrate diagrams of the method of reversion. At times it is desirable or necessary to revert to an earlier version of the file system. An earlier version of the file system is any previous snapshot of the active file system. Once a previous snapshot is selected, the host discards all versions of the file system after the chosen version, including the current active file system. After receiving a request to revert to the previous snapshot, for example, snapshot p shown in FIG. 15a, the host will hold off updates to the current active file system at step 210. At step 212, the host changes the image state of all snapshots after snapshot p from in-use to obsolete and changes the image state of the active file system from active to obsolete (See FIG. 15b). At step 214, the host makes a copy of snapshot p, for example, called snapshot c. Snapshot c is used to receive any updates to space map block entry (p, 0) that were held off during the process of reverting to the previous snapshot version. This permits snapshot p to be preserved in its present state after the system is brought back to an active image state, while at the same time, not losing the pending updates. At step 216, the host sets the image state of snapshot c to in-use. At step 218, the host assigns the next unused version to snapshot c. At step 220, the host sets the root block pointer of snapshot c to the same root block pointer of snapshot p. At step 222, the host creates another copy of snapshot p, for example, called copy a. The copy a will become the active file system of the desired image of snapshot p. At step 224, the host sets the image state of copy a to the active file system. At step 226, the host assigns the next version number to copy a. At step 228, the host sets the root block pointer of copy a to the same root block pointer of snapshot p. At step 230 the host records index a of the active file system into the index table 200 (FIG. 3). At step 232, the host writes the index table to nonvolatile storage. At step 234, the host returns to normal file system activity.

[0065] FIG. 11a illustrates a flow chart for a method to delete a snapshot. At step 75, after receiving a request to delete a snapshot (see also FIG. 15c) the host searches the index table for the requested snapshot. At step 76, the host sets the image state of the requested snapshot to deleted. At step 77, the host returns to normal file system operation.

[0066] FIG. 11b illustrates a high level flow chart for cleaning deleted and obsolete snapshots from the space map blocks and index table of the file system. At step 79, the host determines if any obsolete snapshots exist. If yes, the host goes to reference A in FIG. 13 to clean obsolete snapshots from the space map blocks. If not, the host goes to step 81 and determines if any deleted snapshots exist. If not, then no work needs to be done and the method is complete. At step 81, if a deleted snapshot is found, the host goes to reference H in FIG. 14 to clean deleted snapshots from the space map blocks and index table of the file system.

[0067] FIG. 13 illustrates the detailed flow chart for cleaning obsolete snapshots from space map block entries after a reversion to snapshot p. Step 300 examines each space map block entry one by one in the file system. Step 310 tests whether the beginning index of the space map block entry either matches the snapshot p to which we reverted or precedes snapshot p while the ending index refers to an obsolete snapshot later than p and earlier than c, the snapshot copy created in step 220 on FIG. 10. If the space map block entry matches these conditions, step 312 changes the space map block entry to (b, 0) to indicate that the block is now in use by the active file system.

[0068] Step 314 tests if the beginning index of the space map block entry indicates a snapshot later than the reverted-to snapshot p and the ending index indicates an obsolete snapshot earlier than the copy snapshot c. If so, step 316 sets the space map block entry to (0, 0) to indicate that the entry is free-to-use since no snapshot any longer references it.

[0069] If neither of the conditions tested by steps 310 or 314 are true, then step 318 leaves the space map block entry unchanged.

[0070] After executing step 312, 316, or 318, step 306 tests if we have processed the last space map block entry in the file system. If we have processed the last entry, processing continues at Reference J on FIG. 12a to remove the index table entry for all the obsolete snapshots. Otherwise, step 308 moves to the next space map block entry and processing continues at step 300.

[0071] After completing the processing of all obsolete snapshots in the space map blocks, processing continues at Reference J on FIG. 12a to remove the index table entries corresponding to obsolete snapshots. Processing begins at the first index table entry in step 400. Step 410 tests if the index table entry is obsolete. If so, step 420 clears the index table entry by setting the image state to free-to-use, the timestamp to 0, the root block pointer to 0, and by clearing the name reference. Step 430 tests if we have processed the last index table entry. If this is not the last index table entry, step 440 moves to the next index table entry and processing continues at step 410. After all index table entries have been processed, all obsolete snapshots have been completely removed from the file system.

[0072] Returning to FIG. 11b, if step 81 detects any deleted snapshots in the index table, processing continues at Reference H on FIG. 14. On FIG. 14, step 600 begins with the first space map block entry. Step 610 tests if the beginning index of the space map block entry references a deleted snapshot. If yes, then step 620 tests for any active file system or in-use snapshot with a version later than the beginning space map block entry index. If no snapshot or active file system is found later than the space map block entry beginning index, then step 680 sets the entry to (0, 0) to indicate the corresponding block is free to use. If a later snapshot or active file system is found, step 630 sets the beginning index of the space map block entry to the index of the found snapshot or active file system and continues processing at Reference G on the same sheet.

[0073] Step 640 similarly tests the ending index of the space map block entry to see if it references a deleted snapshot. If so, step 650 tests if there is a snapshot with version less than the current ending index and later than or equal to the version of the beginning index. If not, step 680 sets the space map block entry to (0, 0) to indicate that the block is free-to-use. Otherwise, step 660 sets the ending index to the latest in-use snapshot before the current ending index.

[0074] After completion of either step 660 or 680, step 670 tests for another space map block entry. If there are more space map block entries to process, control returns to step 610. After all space map block entries have been processed, control resumes at Reference K on FIG. 12b to remove index table entries for deleted snapshots.

[0075] FIG. 16 illustrates a diagram of a case where a second reversion to a prior snapshot s has occurred before the background cleaning process for the first reversion to snapshot p has completed. As the file system reverts to a prior snapshot, a pending list is maintained to record the indexes and associated version numbers of the affected snapshots each time the reversion process is invoked. If the file system reverts to more than one snapshot over a span of time where the background cleaning process has not completed, the pending list organizes the cleaning activity by individual reversion event to maintain data reliability of the snapshots. Multiple reversions are likely to occur in large and/or high activity test environments.