# Patent

## Title
File system snapshots over fully provisioned volume file in direct mode

## Abstract

A data storage system employs a multi-level stack including a lower-deck file system and an upper-deck file system providing a file system interface to a file system consumer. The lower-deck file system presents a volume file to provide storage to the upper-deck file system. Storage is reserved to the upper-deck file system, and the volume file is fully provisioned so an out-of-space condition is not presented to the upper-deck file system. In an initial direct operating mode a block address in the lower-deck file system is obtained by a calculation from a corresponding block address in the volume file. Snapshots of a primary volume file are created and stored in respective snapshot volume files. The lower-deck file system transitions into a mapped mode using generally arbitrary mappings of block addresses of the primary volume file and snapshot volume files to obtain corresponding block addresses in the lower-deck file system.

## Background
BACKGROUND
File-based data storage systems are known in the art. These systems include programming and hardware structures to provide file-based access to file systems. File-based data storage systems are sometimes referred to as Network Attached Storage or NAS systems. Such systems may support NFS (Network File System), CIFS (Common Internet File System), SMB (Server Message Block), and/or other file-based protocols. With file-based protocols, host computers (hosts) perform read and write operations to files by specifying particular file systems, paths, and file names. Internally to the data storage system, file system directories map the files specified by host commands to particular sets of blocks on internal volumes, which themselves are derived from disk drives or electronic flash drives. The data storage system accesses the mapped locations and performs the requested reads or writes. An example of a file-based data storage system is the Celerra® system from EMC Corporation of Hopkinton, Mass.
SUMMARY
Methods and apparatus are disclosed for a file-based data storage system that employs a certain set of functional components to provide flexibility and enhanced performance in providing file services to file system consumers such as hosts employing file-based protocols.
In one aspect, a data storage system is disclosed that includes physical nonvolatile storage devices such as disk drives, Flash memory arrays, etc., and a processing subsystem executing software forming a multi-level stack of functional components including a lower-deck file system and an upper-deck file system. The upper-deck file system provides a file system interface to the file system consumer. The lower-deck file system presents a volume file from which storage is provided to the upper-deck file system, and units of storage of the storage devices are reserved to the upper-deck file system, the volume file being fully provisioned based on the reserved units of storage so that an out-of-space condition is not presented to the upper-deck file system. The reserved units of storage are dynamically added to the volume file to increase its allocated size in response to demand from the upper-deck file system. A direct operating mode is initially used in which a block address of a data block in the lower-deck file system is obtained by a predetermined calculation from a corresponding block address of a data block in the volume file.
The volume file may be a primary volume file, and one or more snapshots of the primary volume file are created and stored in respective snapshot volume files of the lower-deck file system, where each snapshot is a respective point-in-time copy of the primary volume file. The lower-deck file system transitions into a mapped mode of operation upon creation of the snapshots, where the mapped mode includes use of generally arbitrary mappings of respective block addresses of data blocks of the primary volume file and snapshot volume files to obtain corresponding block addresses of the data blocks in the lower-deck file system.
The storage system provides flexibility in terms of functionality and performance. Direct mode operation provides performance by use calculations in place of lower-performance IB tree traversals required in mapped mode. However, the ability to transition into mapped mode provides desired support for snapping and related functions. When snaps are deleted and the functionality is no longer being utilized, the higher-performance direct mode operation can resume.



BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
The foregoing and other features and advantages will be apparent from the following description of particular embodiments of the invention, as illustrated in the accompanying drawings, in which like reference characters refer to the same parts throughout the different views. In the accompanying drawings,
FIG. 1 is a block diagram showing a data storage apparatus in an example environment wherein improved techniques hereof may be practiced;
FIG. 2 is a block diagram showing particular example features of a storage processor of FIG. 1, including features of a front end and a back end of an IO stack;
FIG. 3 is a block diagram showing example features of the front end of FIG. 2 in additional detail, including lower-deck file systems built upon storage units (e.g., slices) from a storage pool;
FIG. 4 is a block diagram showing file systems and volumes of the IO stack;
FIG. 5 is a schematic diagram of operation of a file system with a volume;
FIG. 6 is a schematic diagram of use of a volume file for storing data of a file system;
FIGS. 7(a), 7(b), 7(c), 7(d) and 7(e) are schematic diagrams depicting operation of a lower-deck file system pertaining to snapshot files (“snaps”);
FIG. 8 is a flow diagram of operation of a lower-deck file system.



DETAILED DESCRIPTION OF THE INVENTION
Embodiments of the invention will now be described. It is understood that such embodiments are provided by way of example to illustrate various features and principles of the invention, and that the invention hereof is broader than the specific example embodiments disclosed.
FIG. 1 shows an example environment 100 in which embodiments of the improved technique hereof can be practiced. Here, multiple host computing devices (“hosts”), shown as devices 110(1) through 110(N), access a data storage apparatus 116 over a network 114. The data storage apparatus 116 includes a storage processor, or “SP,” 120 and storage 180. The storage 180 is provided, for example, in the form of hard disk drives (HDD) and/or electronic flash drives (EFD). Although not shown in FIG. 1, the data storage apparatus 116 may include multiple SPs like the SP 120. For instance, multiple SPs may be provided as circuit board assemblies, or “blades,” which plug into a chassis that encloses and cools the SPs. The chassis has a backplane for interconnecting the SPs, and additional connections may be made among SPs using cables. It is understood, however, that no particular hardware configuration is required, as any number of SPs (including a single one) can be provided and the SP 120 can be any type of computing device capable of processing host IOs.
The network 114 can be any type of network or combination of networks, such as a storage area network (SAN), local area network (LAN), wide area network (WAN), the Internet, and/or some other type of network, for example. In an example, the hosts 110(1-N) connect to the SP 120 using various technologies. For example, the host 110(1) can connect to the SP 120 using Fibre Channel (e.g., through a SAN). The hosts 110(2-N) can connect to the SP 120 using TCP/IP, to support, for example, iSCSI, NFS, SMB 3.0, and CIFS. Any number of hosts 110(1-N) may be provided, using any of the above protocols, some subset thereof, or other protocols besides those shown. As is known, Fibre Channel and iSCSI are block-based protocols, whereas NFS, SMB 3.0, and CIFS are file-based protocols. The SP 120 is configured to receive IO requests 112(1-N) according to both block-based and file-based protocols and to respond to such IO requests 112(1-N) by reading or writing the storage 180.
The SP 120 is seen to include one or more communication interfaces 122, a set of processors 124, and memory 130. The communication interfaces 122 include, for example, adapters, such as SCSI target adapters and network interface adapters, for converting electronic and/or optical signals received from the network 114 to electronic form for use by the SP 120. The set of processors 124 includes one or more processing chips and/or assemblies. In a particular example, the set of processors 124 includes numerous multi-core CPUs. The memory 130 includes both volatile memory (e.g., RAM), and non-volatile memory, such as one or more ROMs, disk drives, solid state drives (SSDs), and the like. The set of processors 124 and the memory 130 together form control circuitry, which is constructed and arranged to carry out various methods and functions as described herein. Also, the memory 130 includes a variety of software constructs realized in the form of executable instructions. When the executable instructions are run by the set of processors 124, the set of processors 124 are caused to carry out the operations of the software constructs. Although certain software constructs are specifically shown and described, it is understood that the memory 130 typically includes many other software constructs, which are not shown, such as various applications, processes, and daemons.
As shown, the memory 130 includes an operating system 134, such as Unix, Linux, or WindowsTM, for example. The operating system 134 includes a kernel 136. The memory 130 further includes a container 132. In an example, the container 132 is a software process that provides an isolated userspace execution context within the operating system 134. In various examples, the memory 130 may include multiple containers like the container 132, with each container providing its own isolated userspace instance. Although containers provide isolated environments that do not directly interact (and thus promote fault containment), different containers can run on the same kernel 136 and can communicate with one another using inter-process communication (IPC) mediated by the kernel 136. Containers are well-known features of Unix, Linux, and other operating systems.
In the example of FIG. 1, only a single container 132 is shown. Running within the container 132 is an IO stack 140, a mirror cache 150, and a replicator 160. The IO stack 140 provides an execution path for host IOs (e.g., 112(1-N)) and includes a front end 142 and a back end 144. The mirror cache 150 stores data for incoming writes and mirrors the data to cache on another SP. The replicator 160 makes local and/or remote copies of data for incoming writes. As the IO stack 140, mirror cache 150, and replicator 160 all run within the same container 132, the IO stack 140, mirror cache 150, and replicator 160 can communicate with one another using APIs (application program interfaces), i.e., without the need to use IPC.
The memory 130 also stores a configuration database 170. The configuration database 170 stores system configuration information. In other implementations, the configuration database 170 is stored elsewhere in the data storage apparatus 116, such as on a disk drive separate from the SP 120 but accessible to the SP 120, e.g., over a backplane or network.
In operation, the hosts 110(1-N) issue IO requests 112(1-N) to the data storage apparatus 116. The IO requests 112(1-N) may include both block-based requests and file-based requests. The SP 120 receives the IO requests 112(1-N) at the communication interfaces 122 and passes the IO requests to the IO stack 140 for further processing. At the front end 142, processing may include caching data provided with any write IO requests to the mirror cache 150, which may in turn cache the data to another SP. Also within the front end 142, mapping operations map LUNs and host file systems to underlying files stored in a set of internal file systems of the front end 142. Host IO requests received for reading and writing both LUNs and file systems are thus converted to reads and writes of respective files. The IO requests then propagate to the back end 144, where commands are executed for reading and/or writing the physical storage 180, agnostically to whether the data read and/or written is directed to a LUN or to a host file system.
Although FIG. 1 shows the front end 142 and the back end 144 together in an “integrated” form, the front end 142 and back end 144 may alternatively be provided on separate SPs. For example, the IO stack 140 may be implemented in a “modular” arrangement, with the front end 142 on one SP and the back end 144 on another SP. The IO stack 140 may further be implemented in a “gateway” arrangement, with multiple SPs running respective front ends 142 and with a back end provided within a separate storage array. The back end 144 performs processing that is similar to processing natively included in many block-based storage arrays. Multiple front ends 142 can thus connect to such arrays without the need for providing separate back ends.
FIG. 2 shows the front end 142 and back end 144 of the IO stack 140 in additional detail. Here, the front end 142 is seen to include protocol end points 220, a redirector 222, an incoming cache manager 224, a user object layer 226, a mapping layer 228, one or more lower-deck (internal) file systems 230, a storage pool 232, a unified cache manager 234, and a basic volume interface 236. The back end 144 is seen to include a host side adapter 250, a RAID (Redundant Array of Independent Disks) manager 252, and hard disk drive/electronic flash drive support 254.
Within the front end 142, protocol end points 220 receive the host IO requests 210 from the communication interfaces 122 and perform protocol-specific processing, such as stripping off header information and identifying data payloads. Processing then continues to the redirector 222.
The redirector 222 receives the host IOs and, under specified conditions, redirects the host IO requests to another SP. For example, the LUN specified in any block-based host 10 request may be owned by a particular SP of the data storage apparatus 116. If the SP 120 receives a host IO request that is directed to a LUN owned by another SP, the redirector 222 sends the host IO to the SP that owns the LUN, at which point processing of the host 10 request by the SP 120 ceases. However, if the redirector 222 detects that the LUN specified in a block-based host 10 request is owned by the SP 120, the redirector allows the host IO request to continue to propagate through the front end 142. The redirector 222 performs no operation for file-based host 10 requests. For host 10 requests that are not redirected, processing continues to the incoming cache manager 224.
The incoming cache manager 224 provides low-latency responses to incoming host 10 write requests. When a write 10 request is received, the incoming cache manager 224 caches the data specified by the write request in the mirror cache 150. Operating in conjunction with the unified system cache 234, the incoming cache manager 224 directs the contents of the mirror cache 150 to be copied over a high-speed interconnect (e.g., a high-speed cable or bus) to a cache of a second SP of the data storage apparatus, where a duplicate copy of the data is stored. The data specified by the host write 10 request are thus stored in two independent locations and are deemed to be persisted. Upon confirmation that the data have been successfully written to both the mirror cache 150 and the cache of the other SP, the incoming cache manager 224 acknowledges the write back to the originating host (i.e., the host of 110(1-N) that sent the write host 10). Using this arrangement, write requests are acknowledged quickly, without the need to wait until the requests propagate to the actual storage 180 or even to the unified cache manager 234, thereby providing a low level of latency in responding to write IOs. The data stored in the mirror cache 150 may eventually be destaged to the storage 180 (e.g., to the set of slices that store the LUN or file system being written to), but such destaging may be conducted when convenient and out of band with the processing of host IOs. Processing continues to the incoming user object layer 226.
The user object layer 226 presents underlying files representing LUNs and underlying files representing host file systems in a form recognized by the hosts (i.e., as LUNs and host file systems). For example, the user object layer 226 presents data stored in underlying files for block-based data as LUNs. The user object layer 226 also presents data stored in underlying files for file-based data as host file systems. In an example, the user object layer 226 includes an upper-deck file system for each host file system stored in a file of the lower-deck file system(s) 230 (described below). Each upper-deck file system presents files and directories of a host file system to the hosts 110(1-N), even though the host file system is represented internally as a file.
The mapping layer 228 maps host objects as presented in the user object layer 226 to corresponding underlying files stored in one or more lower-deck file systems 230. For LUNs, the mapping layer 228 converts a LUN identifier and offset range to a particular file in a lower-deck file system 230 and to a particular offset range within that file. Any set of blocks of a LUN identified in a host IO request are thus mapped to a set of blocks in the underlying file that represents the LUN. Similarly, for host file systems, the mapping layer 228 converts a given file or directory represented in an upper-deck file system of the user object layer 226 to a particular file in a lower-deck file system 230 and to a particular location within the file.
The lower-deck file system layer 230 represents LUNs and host file systems in the form of files. Any number of lower-deck file systems 230 may be provided. In one arrangement, a single lower-deck file system 230 may be provided to include any number of LUNs and/or host file systems, as well as their snaps (i.e., point-in-time copies). In another arrangement, a different lower-deck file system is provided for each primary object to be stored, i.e., for each LUN and for each host file system. The lower-deck file system for any primary object may include a file storing the object itself, as well as files storing any snaps of the object. Each lower-deck file system 230 has an inode table, which provides a unique inode for each file stored in the lower-deck file system 230. The inode table of each lower-deck file system stores properties of each file in the respective lower-deck file system, such as ownership and block locations at which the file's data are stored. Lower-deck file systems are built upon storage elements managed by a storage pool 232.
The storage pool 232 organizes elements of the storage 180 in the form of slices. A “slice” is an increment of storage space, such as 256 MB in size, which is drawn from the storage 180. The pool 232 may allocate slices to lower-deck file systems 230 for use in storing their files. The pool 232 may also deallocate slices from lower-deck file systems 230 if the storage provided by the slices is no longer required. In an example, the storage pool 232 creates slices by accessing RAID groups formed from the storage 180, dividing the RAID groups into FLUs (Flare LUNs), and further dividing the FLU's into slices.
The unified cache manager 234 provides caching services for data stored in the lower-deck file systems 230. In some examples, the unified cache manager 234 directs data specified by host writes to local RAM or flash memory and thus avoids the need to access the storage 180, which is typically more remote than the local RAM or flash memory and takes more time to access. In some examples, the unified cache manager 234 also directs data returned in response to read IO requests to be stored in local RAM or flash memory for fast access in the event that subsequent host IO requests require the same data. In some examples, the local RAM or flash memory may store the only valid copy of host data, with writes to the storage 180 being deferred and, in cases where host data needs to be stored only transiently, avoided altogether.
The basic volume interface 236 is arranged to send host IOs to the back end 144 when the back end 144 is provided on another SP of the data storage apparatus 116 or when the back end 144 is provided on a separate array. In an example, the basic volume interface 236 converts host IOs propagating out of the front end 142 to a block-based protocol, such as Fibre Channel. After being processed by the basic volume interface 236, processing continues to the back end 144.
Within the back end 144, the host side adapter 250 receives the host IO and extracts the host IO content. In some implementations, such as the “integrated” arrangement shown in FIG. 1, the basic volume interface 236 and host side adapter 250 may be omitted or may be made to perform no operation.
The RAID manager 252 accesses the particular slice or slices being written or read using RAID protocols. In some examples, the RAID manager 252 also performs out-of-band operations of maintaining RAID groups, such as swapping out failing disk elements and applying erasure coding to restore required redundancy.
The hard disk drive/electronic flash drive support 254 includes drivers that perform the actual reading from or writing to the storage 180.
Although the above-described components of the IO stack 140 are presented in a particular order, this order can be varied. For example, the incoming cache manager 224 can be located above the redirector 222. Also, multiple cache managers can be provided at different locations within the IO stack 140.
FIG. 3 shows portions of the front end 142 in additional detail. Here, the user object layer 226 includes a representation of an HFS (host file system) 312, and the mapping layer 228 includes a file-to-HFS mapping 322. The file-to-HFS mapping 322 maps the HFS 312 to a file F (346). Through the file-to-HFS mapping 322, any file or directory of the HFS 312 is mapped to a corresponding set of blocks within the file 346.
The file 346 is included within a particular lower-deck file system 340. The lower-deck file system 340 includes an inode table 342. The inode table 342 provides information about files in the lower-deck file system 340 in the form of inodes. For example, the inode table 342 of the lower-deck file system 340 includes an inode 344 which provides file-specific information about the file 346. The information stored in each inode includes location information (e.g., data block locations) where the data of the respective file is stored, and may thus be accessed as metadata to identify the locations of the file 346.
Although a single file is shown for the lower-deck file system 340, it is understood that each of the lower-deck file systems 230 may include any number of files, each having its own entry in the respective inode table of its file system. Also, a lower-deck file system may store not only regular files such as the file F 346, but also snapshots (point-in-time copies, also called “snaps”) of such files. In this context the original file (e.g., file F 346) is referred to as a “primary” file. For instance, the lower-deck file system 340 stores the primary file 346 along with a different file for every snap of that file (such snaps effectively forming snaps of the HFS 312).
As shown, a set of slices 360 is allocated from the storage pool 232 for storing the file 346. In the example shown, slices S1 through S3 are used for storing the file 346, and thus the data that make up the HFS 312 are stored in the slices S1 through S3. In an example, the storage pool 232 allocates slices 350 to the set of file systems 230 in an on-demand manner, e.g., as the file 246 requires additional storage. The storage pool 232 can also deallocate slices from the set of file systems 230 when all the currently allocated slices are no longer required.
As described more below, at least some of the lower-deck file systems 230 are associated with respective volumes referred to as “sparse volumes”. Sparse volumes provide an additional layer of mapping between the lower-deck file systems 230 and the pool 232 and allow the lower-deck file systems 230 to operate as file systems normally do, by accessing underlying volumes. Sparse volumes may also be employed at a higher level, between an HFS 312 and a file of a lower-deck file system 230 that is presented as a volume. Additional details about sparse volumes and their relation to lower-deck file systems may be found in U.S. Pat. No. 7,631,155, which is hereby incorporated by reference in its entirety. The incorporated patent uses the term “container file systems” to refer to constructs similar to the lower-deck file systems disclosed herein.
FIG. 4 shows another view of the organization of the data storage system useful for describing certain functionality as presented below. In FIG. 4, the user object and mapping layers 226, 228 include an upper-deck file system 400. As shown, the upper-deck file system 400 presents data in the form of host files 404 to a separate host computer (not shown). The lower-deck file system layer 230 includes a lower-deck file system 406. The lower-deck file system 406 presents a file referred to as a “volume file” 410 to the upper-deck file system 400. The volume file 410 may be the subject of point-in-time copying by which snapshots or “snaps” are created and used for various purposes. The active production file is referred to as the “primary” volume file 410-P, while the snaps are shown as snapshot files 410-S.
As described more below, the arrangement of FIG. 4 uses “full provisioning” with a dynamic allocation feature, which refers to the manner in which slices of the pool 232 become allocated or assigned to the upper-deck file system 400 as underlying physical storage for file contents. In the present description, these include the following:
1. Underlying storage is fully reserved, meaning that the configured size of the upper-deck file system 400 is equal to the amount of storage in the pool 232 reserved for use by the upper-deck file system 400 to the exclusion of other potential users (e.g., other file systems 230).
2. Underlying storage is dynamically allocated, meaning that slices from the pool 232 are assigned for actual use by the upper-deck file system 400 as its contents grow in response to the writing of data.
3. The volume file 410 is dense, i.e., completely containing actual underlying storage. Slices that are cut from the volume file 410 for use by the upper-deck file system 400 are fully provisioned. There cannot be an out-of-space condition.
FIG. 5 illustrates certain details regarding files and file systems, applicable at both the upper layer (404, 400 in FIG. 4) and at the lower layer (410, 406) except for certain differences that are noted below. A file 404, 410 is shown as including an Inode 500 and a set of data blocks (B) 502. An indirect block (IB) 504 is also shown. All these items are included in the respective file system 400, 406, which in general will contain multiple files. Thus, the Inode 500 is part of an Inode structure 506 that includes Inodes of other files (not shown) as well as the indirect blocks 504. Additional details about the files 404, 410 and file systems 400, 406 are provided below.
Also shown in FIG. 5 is the relationship of the file 404, 410 to the respective file system. Each file system 400, 406 has a respective maximum size (as may be specified in blocks or bytes, for example) shown as Max(FS). At any given time there is an allocated size corresponding to the amount of underlying storage that is actually allocated for use.
The upper-deck file system 400 draws slices of storage from the volume file 410, while the lower-deck file system 406 draws slices directly from the pool 232. Of course, the volume file 410 is constituted by slices from the pool 232 via operation of the lower-deck file system 406. In many cases it will be desirable that slices defined at the upper level (upper-deck file system 400 and volume file 410) are of the same size, and aligned with, slices as defined in the pool 232 and used by the lower-deck file system 406. However, in general this is not required.
Returning to the files 404, 410, the Inode 500 contains direct pointers to some number of blocks 502 where file data is stored. If the file is sufficiently large, then one or more indirect blocks 504 are used. The Inode 500 contains pointers to the indirect block(s) 504, which in turn include pointers to additional data blocks 502. In typical file systems there may be at most three levels of indirection. In the description below, the term “IB tree” is used to refer to the entire set of IBs 504 and the Inode 500 for a given file.
The IB tree establishes a mapping 512 from a logical linear arrangement of blocks 502 of a file 404, 410 to corresponding block locations in the address space of the file system 400, 406. In general this mapping may be arbitrary, i.e., neither ordering nor adjacencies of blocks need to be preserved, and for such arbitrary mappings it is necessary to traverse the IB tree to locate a block in the file system 400, 406 based on an address of the block in the corresponding file 404, 410. This is the manner of operation of the upper-deck file system 400.
For the lower-deck file system 406, however, there is the possibility of operating in what is referred to as “direct mode” in which the mapping is constrained in a manner that enables block locations to be identified by calculation rather than by traversing the IB tree. In particular, as shown in FIG. 5 the block ordering is preserved, and block adjacencies are preserved within individual groups. In the simplified example of FIG. 5, this is shown for two groups, one having three blocks 502 and the other having two blocks 502. Calculation is generally much faster than IB tree traversal, and thus direct mode operation can provide improved file system performance.
In one embodiment, direct mode is a consequence of there being a single file in the file system 406. Rather than randomly allocating blocks to the file as it writes to them, a linear mapping is used that maps the first block in the file to the first data block in the file system, the second data block in the file to the second data block in the file system, and so on.
If there are no interspersed metadata structures, then the on disk location of any data block in a file can be simply the starting location of all data blocks in the file system plus the offset of the data block in the file. If the data blocks have metadata structures interspersed, the storage address can be algorithmically calculated given the file offset (the block in the file). The algorithm knows where the interspersed data structures are on disk so that it can correctly calculate the address of the data block on disk.
FIG. 6 illustrates the relationship between the upper-deck file system 400 and the volume file 410 presented by the lower-deck file system 406. Slices 510 are created from corresponding slice-size areas of the volume file 410, with a generally arbitrary mapping between their respective locations. Holes 508 are slice-size areas not currently provisioned. As the actual size of the upper-deck file system 400 increases, which is reflected in holes 508 being replaced with slices 510, the size of the volume file 410 is increased accordingly. This demand from the upper-deck file system 400 is passed down to the lower-deck file system 406, to which additional pool slices 350 are allocated to enable the lower-deck file system 406 to grow the size of the volume file 410 accordingly, and this additional space is used to add slices 510 to the upper-deck file system 400. As indicated, the volume file 410 has a maximum size shown as Max(VF). If demand by the upper-deck file system 400 surpasses this value, then subsequent file write operations from a host to the upper-deck file system 400 may be responded to with an out-of-space condition. In one embodiment, this may always occur. In another embodiment, this may be prevented by increasing Max(VF) and allocating additional storage from the pool 232 if available.
FIG. 7 illustrates operation of the lower-deck file system 406 with the snapshot files or “snaps” 410-S.
FIG. 7(a) shows the direct mode with the primary file 410-P, similar to FIG. 5 discussed above.
FIG. 7(b) shows an arrangement immediately after creation of a snap 410-S. The snap 410-S has a respective mapping 512-S, and initially its pointers point to the same blocks 502 of the primary file 410-P. Thus, these blocks 502 are now shared (indicated with shading) between the primary file 410-P and the snap 410-S. In this operating state, a read operation to any block 502 of either the primary file 410-P or the snap 410-S is satisfied by accessing the shared blocks 502.
FIG. 7(c) shows an arrangement sometime later after writes to the primary file 410-P have occurred, which induces a “write split” causing blocks 502-P of the primary file 410-P to be located separately from the blocks 502-S. The pointers for the snap 410-S point to the blocks 502 (now identified as 502-S) that were part of the primary file 410-P when the snap was taken. In this state, writes and reads to/from the primary file 410-P and snap file 410-S are satisfied from the respective sets of blocks 502-P, 502-S.
FIG. 7(d) shows an arrangement upon the snap 410-S being deleted. The mapping 512-S (snap file metadata) is all deleted, and the data blocks 502-P of the primary file 410-P remain in their current locations. The blocks 502-S are now “free”, meaning that they do not contain file data and thus could potentially be re-used by the file system 406. This operation can continue indefinitely.
FIG. 7(e) shows the situation at a later time after (a) a process of defragmenting the lower-deck file system 406 is been performed to compact the data blocks 502-P and move them to other (free) slices. The blocks are moved in a manner that enables the file system 406 to regain its direct-mode operation, as described above with reference to FIG. 5.
The simple example of FIG. 7 has only one snap 410-S of a given primary file 410-P. In general there may be multiple snaps 410-S of a given primary file. In many embodiments snaps 410-S are generally read-only (unless and until they become promoted to primary status, such as in a rollback to a previous file state). However, in other embodiments snaps 410-S may essentially become independent operating files subject to regular modification by application writes. In these cases the system may support “snaps of snaps”, i.e., creating a snap 410-S2 from a previously created snap 410-S1. The description above applies equally to such deeper-level snapshot files 410-S.
FIG. 8 is a high-level flow diagram of pertinent operation 600 of the data storage system 116. At 602, software is instantiated in the SP 120 to form a multi-level stack of functional components including a lower-deck file system 406, an upper-deck file system 400, and a first (lower) volume 408 used by the lower-deck file system 406 and formed by units of storage of physical storage devices 180. The upper-deck file system 400 provides a file system interface to a file system consumer (e.g., a host computer), and the units of storage are drawn from a pool 232 of units available for other uses by the data storage system. That is, the units (e.g. slices) are not reserved for use by the upper-deck file system 400.
At 604 are operations of the lower-deck file system 406, which include (1) presenting a volume file from which storage is provided to the upper-deck file system. Units of storage of the storage devices 180 are reserved to the upper-deck file system 400, and the volume file 410 is fully provisioned based on the reserved units of storage so that an out-of-space condition is not presented to the upper-deck file system 400. Additionally, the reserved units of storage are dynamically added to the volume file 410 to increase its allocated size in response to demand from the upper-deck file system 400. Operations further include (2) utilizing a direct operating mode is used in which a block address of a data block in the lower-deck file system is obtained by a predetermined calculation from a corresponding block address of a data block in the volume file.
Finally, operations of the lower-deck file system 406 include (3) creating and managing snap volume files 410-S for snapshots of the upper-deck file system 400. These operations include establishing and using respective mappings 512-S, sharing of blocks 502, write splitting, transitioning into mapped mode and back into direct mode upon deletion of a last snap, etc. as described above.
As shown, the operating software may be stored on and instantiated from a non-transitory computer-readable medium 606 such as a magnetic or optical disk or nonvolatile semiconductor memory such as Flash.
One feature of the presently disclosed system and methods is that all of the metadata of the upper-deck file system 400 is stored within the volume file 410. For example, the file system 400 may maintain certain logs referred to as a metadata intent log and a data intent log, as well as slice pool state information, and all this metadata is entirely contained within the volume file 410 that is subject to snap. This can greatly simplify snapshotting the upper-deck file system 400, because there is no need to coordinate taking the snap with making the upper deck metadata, file data cache or upper slice pool respective states stable.
At a time that a snap of the file system 400 is mounted, it needs to recover its state by going thru these steps:
1) recover upper deck slice pool state
2) recover metadata state
3) recover file cache state
As used throughout this document, the words “comprising,” “including,” and “having” are intended to set forth certain items, steps, elements, or aspects of something in an open-ended fashion. Although certain embodiments are disclosed herein, it is understood that these are provided by way of example only and the invention is not limited to these particular embodiments. In addition, the word “set” as used herein indicates one or more of something, unless a statement is made to the contrary.
Having described certain embodiments, numerous alternative embodiments or variations can be made. For example, the lower-deck file systems 230 have been described as storing file representations of LUNs, host file systems, block-based vVols, file-based vVols, and snaps of any of the foregoing. These are merely examples, however. Other types of objects may be stored in the lower-deck file systems 230 as file representations, such as virtual hard disks (VHDs), virtual machine disks (VMDKs), internal file systems used by the data storage apparatus 116, and internal volumes, for example.
In addition, as shown and described, different types of objects (LUNs, host file systems, etc.) are shown and described as being stored in respective lower-deck file systems. This is merely an example, however. Alternatively, any of LUNs, host file systems, block-based vVols, and file-based vVols, as well as snaps of any of the foregoing, may be included together in a single lower-deck file system or in any number of lower-deck file systems. Thus, it is not required that files representing different types of objects be stored in different lower-deck file systems.
Also, the improvements or portions thereof may be embodied as a non-transient computer-readable storage medium, such as a magnetic disk, magnetic tape, compact disk, DVD, optical disk, flash memory, Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), and the like (shown by way of example as medium 1150 in FIG. 12). Multiple computer-readable media may be used. The medium (or media) may be encoded with instructions which, when executed on one or more computers or other processors, perform methods that implement the various processes described herein. Such medium (or media) may be considered an article of manufacture or a machine, and may be transportable from one machine to another.
Further, although features are shown and described with reference to particular embodiments hereof, such features may be included in any of the disclosed embodiments and their variants. Thus, it is understood that features disclosed in connection with any embodiment can be included as variants of any other embodiment, whether such inclusion is made explicit herein or not.
Those skilled in the art will therefore understand that various changes in form and detail may be made to the embodiments disclosed herein without departing from the scope of the invention.

## Claims

1. A data storage system for use by a file system consumer according to a file system interface, comprising:
one or more physical, non-transitory, nonvolatile storage devices; and
a processing subsystem executing software to form a multi-level stack of functional components including a lower-deck file system and an upper-deck file system, the upper-deck file system providing the file system interface to the file system consumer, the lower-deck file system presenting a volume file from which storage is provided to the upper-deck file system, units of storage of the storage devices being reserved to the upper-deck file system, the volume file being fully provisioned based on the reserved units of storage so that an out-of-space condition is not presented to the upper-deck file system, the reserved units of storage being added dynamically to the volume file to increase its allocated size in response to demand from the upper-deck file system, the lower-deck file system initially operating in a direct mode in which a block address of a data block in the lower-deck file system is obtained by a predetermined calculation from a corresponding block address of a data block in the volume file,
wherein the volume file is a primary volume file, and one or more snapshots of the primary volume file are created and stored in respective snapshot volume files of the lower-deck file system, each snapshot being a respective point-in-time copy of the primary volume file, and wherein the lower-deck file system transitions into a mapped mode of operation upon creation of the snapshots, the mapped mode including use of generally arbitrary mappings of respective block addresses of data blocks of the primary volume file and snapshot volume files to obtain corresponding block addresses of the data blocks in the lower-deck file system.

2. A data storage system according to claim 1, wherein upon creation of a snapshot it is populated with existing blocks of the primary volume file, and in response to ongoing writes to the primary file, a write split is performed by which current data blocks of the primary volume file are separated from the existing blocks which continue to populate the snapshot, the current data blocks being the subject of the ongoing writes as well as reads directed to the primary volume file.

3. A data storage system according to claim 2, wherein in response to deletion of a last one of the snapshots, the data blocks of the primary volume file are configured in a linear manner and the lower-deck file system transitions back into the direct mode with respect to the primary volume file.

4. A data storage system according to claim 1, wherein the snapshot volume files are first-level snapshot volume files, and wherein one or more second-level snapshots of the one of the first-level snapshot volume files are stored in respective second-level snapshot volume files of the lower-deck file system, each second-level snapshot being a respective point-in-time copy of a respective first-level snapshot volume file, and the mapped mode includes use of generally arbitrary additional mappings of respective block addresses of data blocks of the second-level snapshot volume files to obtain corresponding block addresses of the data blocks in the lower-deck file system.

5. A data storage system according to claim 1, wherein the mapped mode includes traversal of pointers and indirect blocks of an inode structure identifying locations of data blocks in the lower-deck file system based on block addresses of the data blocks in the volume file.

6. A data storage system according to claim 1, wherein:
all metadata of the upper-deck file system is stored within the volume file and therefore automatically included as part of the snapshots without need for separately making the metadata stable at a time a snapshot is obtained; and
at a later time of mounting a snap of the upper-deck file system, state is recovered by reading and applying the following from the metadata of the snap: (1) upper deck slice pool state, (2) metadata state, and (3) file cache state.

7. A data storage system according to claim 1, wherein the units of storage are provided by a pool layer, and the multi-level stack of functional components includes a sparse volume layer of mapping between the lower-deck file system and the pool layer, the sparse volume layer including a sparse volume on which the lower-deck file system is structured and which is accessed by file operations of the lower-deck file system.

8. A data storage system according to claim 7, wherein the upper-deck file system draws slices of storage from the volume file, and the volume file is constituted by slices from the pool via operation of the lower-deck file system which draws slices from the pool.

9. A data storage system according to claim 1, wherein the upper-deck file system operates in a respective mapped mode including use of generally arbitrary mappings of respective block addresses of data blocks of files of the upper-deck file system to obtain corresponding block addresses of the data blocks of the volume file.

10. A method of operating a data storage system to provide file system functionality to a file system consumer according to a file system interface, the data storage system including one or more physical nonvolatile storage devices and a processing subsystem, comprising:
instantiating, in the processing subsystem, software to form a multi-level stack of functional components including a lower-deck file system and an upper-deck file system, the upper-deck file system providing the file system interface to the file system consumer; and
by the lower-deck file system, (i) presenting a volume file from which storage is provided to the upper-deck file system, units of storage of the storage devices being reserved to the upper-deck file system, the volume file being fully provisioned based on the reserved units of storage so that an out-of-space condition is not presented to the upper-deck file system, (ii) dynamically adding the reserved units of storage to the volume file to increase its allocated size in response to demand from the upper-deck file system, and (iii) utilizing a direct operating mode in which a block address of a data block in the lower-deck file system is obtained by a predetermined calculation from a corresponding block address of a data block in the volume file,
wherein the volume file is a primary volume file, and one or more snapshots of the primary volume file are created and stored in respective snapshot volume files of the lower-deck file system, each snapshot being a respective point-in-time copy of the primary volume file, and wherein the lower-deck file system transitions into a mapped mode of operation upon creation of the snapshots, the mapped mode including use of generally arbitrary mappings of respective block addresses of data blocks of the primary volume file and snapshot volume files to obtain corresponding block addresses of the data blocks in the lower-deck file system.

11. A method according to claim 10, wherein upon creation of a snapshot it is populated with existing blocks of the primary volume file, and in response to ongoing writes to the primary file, a write split is performed by which current data blocks of the primary volume file are separated from the existing blocks which continue to populate the snapshot, the current data blocks being the subject of the ongoing writes as well as reads directed to the primary volume file.

12. A method according to claim 11, wherein in response to deletion of a last one of the snapshots, the data blocks of the primary volume file are configured in a linear manner and the lower-deck file system transitions back into the direct mode with respect to the primary volume file.

13. A method according to claim 10, wherein the snapshot volume files are first-level snapshot volume files, and wherein one or more second-level snapshots of the one of the first-level snapshot volume files are stored in respective second-level snapshot volume files of the lower-deck file system, each second-level snapshot being a respective point-in-time copy of a respective first-level snapshot volume file, and the mapped mode includes use of generally arbitrary additional mappings of respective block addresses of data blocks of the second-level snapshot volume files to obtain corresponding block addresses of the data blocks in the lower-deck file system.

14. A method according to claim 10, wherein the mapped mode includes traversal of pointers and indirect blocks of an inode structure identifying locations of data blocks in the lower-deck file system based on block addresses of the data blocks in the volume file.

15. A method according to claim 10, wherein:
all metadata of the upper-deck file system is stored within the volume file and therefore automatically included as part of the snapshots without need for separately making the metadata stable at a time a snapshot is obtained; and
at a later time of mounting a snap of the upper-deck file system, state is recovered by reading and applying the following from the metadata of the snap: (1) upper deck slice pool state, (2) metadata state, and (3) file cache state.