Implicit container per version set

• US 7,818,535 B1
• Filed: 06/30/2007
• Issued: 10/19/2010
• Est. Priority Date: 06/30/2007
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Mullick, Sachin, Bono, Jean-Pierre, Veeraswamy, Sairam, Hayden, John M.
• Primary Examiner(s): Thai; Tuan V
• Assistant Examiner(s): Doan; Duc T
• Application Number:
  US11/772,154
• Time in Patent Office: 1,207 Days
• Field of Search: None
• US Class Current: 711/173
• CPC Class Codes: G06F 12/0868 Data transfer between cache memory and other subsystems, e.g. storage devices or host systems
• CPC Class Codes: G06F 2212/261 Storage comprising a plurality of storage devices
• CPC Class Codes: G06F 3/0605 by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/0643 Management of files
• CPC Class Codes: G06F 3/0649 Lifecycle management
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/0685 Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays
• CPC Class Codes: G06F 3/0689 Disk arrays, e.g. RAID, JBOD

Abstract

When a client requests creation of a production file system or logical unit number (LUN) of storage, a sparse metavolume and a container file system built on the sparse metavolume are implicitly created for containing the production file system or LUN. By implicitly creating one container file system for each production file system or LUN, it is possible to hide the management of the container file system from the client or end user. The creation of snapshot copies in the container file system can also be hidden from the client or end user. Customer service level expectations and thin provisioning can be met automatically by storage policies implemented upon the container file system and the underlying sparse metavolume.

Claims

1. A file server comprising:

data storage; and

at least one data processor coupled to the data storage for accessing the data storage;

wherein said at least one data processor is programmed for responding to a request from at least one client for creating a production file system or logical unit number (LUN) of storage by;

(a) implicitly creating a sparse metavolume of the data storage for the production file system or LUN, and

(b) implicitly creating a container file system on the sparse metavolume, the container file system including a file having a logical extent providing logical storage for the production file system or LUN, and

(c) creating the production file system or LUN in the logical extent of the file in the container file system.

2. The file server as claimed in claim 1, wherein said at least one data processor is programmed for implicitly creating one container file system for each production file system or LUN requested by the client.

3. The file server as claimed in claim 1, in which management of the container file system is hidden from the client.

4. The file server as claimed in claim 1, wherein said at least one data processor is further programmed for creating snapshot copies of the production file system or LUN and storing the snapshot copies in the container file system.

5. The file server as claimed in claim 4, wherein said at least one data processor is programmed for changing access of the production file system from direct mapped access to mapped access when a first snapshot copy of the production file system or LUN is made.

6. The file server as claimed in claim 5, wherein said at least one data processor is programmed for responding to deletion of all snapshot copies of the production file system or LUN by changing access of the production file system or LUN from mapped access to direct mapped access.

7. The file server as claimed in claim 4, wherein said at least one data processor is programmed for responding to deletion of all snapshot copies of the production file system or LUN by performing a reorganizing process of defragmentation and space reclamation.

8. The file server as claimed in claim 1, wherein said at least one data processor is programmed for receiving a specification of a size of the production file system or LUN in the request from the client, and for creating the container file system with a logical extent containing the specified size, and for provisioning physical storage or not for the specified size at the time of creation of the production file system or LUN in accordance with a configured policy as overridden by any explicit request from the client.

9. A method of operating a file server, said method comprising the steps of:

the file server receiving a request from a client for creation of a production file system; and

the file server responding to the request from the client by;

(a) implicitly creating a sparse metavolume of storage for the production file system, and

(b) implicitly creating a container file system on the sparse metavolume, the container file system including a file having a logical extent providing logical storage for the production file system, and

(c) creating the production file system in the logical extent of the file in the container file system.

10. The method as claimed in claim 9, which further includes storing, in the container file system, a transaction log for the production file system.

11. The method as claimed in claim 9, wherein one container file system is created implicitly for each production file system requested by the client.

12. The method as claimed in claim 9, wherein management of the container file system is hidden from the client.

13. The method as claimed in claim 9, which further includes creating snapshot copies of the production file system, and storing the snapshot copies in the container file system.

14. The method as claimed in claim 9, which further includes responding to deletion of all snapshot copies of the production file system by performing a reorganizing process of defragmentation and space reclamation.

15. The method as claimed in claim 9, which further includes receiving a specification of a size of the production file system in the request from the client, and for creating the container file system with a logical extent containing the specified size, and for provisioning physical storage or not for the specified size at the time of creation of the production file system in accordance with a configured policy.

16. A method of operating a file server, said method comprising the steps of:

the file server receiving a request from a client for creation of a logical unit number (LUN) of storage; and

the file server responding to the request from the client by;

(a) implicitly creating a sparse metavolume of storage for the LUN, and

(b) implicitly creating a container file system on the sparse metavolume, the container file system including a file having a logical extent providing logical storage for the LUN, and

(c) creating the LUN in the logical extent of the file in the container file system.

17. The method as claimed in claim 16, wherein one container file system is created implicitly for each LUN requested by the client.

18. The method as claimed in claim 16, wherein management of the container file system is hidden from the client.

19. The method as claimed in claim 16, which further includes creating snapshot copies of the LUN, and storing the snapshot copies in the container file system.

20. The method as claimed in claim 16, which further includes receiving a specification of a size of the LUN in the request from the client, and for creating the container file system with a logical extent containing the specified size, and for provisioning physical storage or not for the specified size at the time of creation of the LUN in accordance with a configured policy.