FILE CLONING ACROSS DIFFERENT FILESETS

• US 20140156602A1
• Filed: 02/06/2014
• Published: 06/05/2014
• Est. Priority Date: 09/10/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Adkins, Janet E., Chang, Joon, Craft, David J., Kumar, Manoj N., Palsule, Ninad S.
• Granted Patent: US 9,020,899 B2
• Time in Patent Office: Days
• US Class Current: 707/649
• CPC Class Codes: G06F 16/11 File system administration, e.g. details of archiving or snapshots file system backup G06F11/14
• CPC Class Codes: G06F 16/128 Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion use of snapshots for error detection or correction G06F11/14, G06F11/16
• CPC Class Codes: G06F 16/40 of multimedia data, e.g. slideshows comprising image and additional audio data retrieval of still image data G06F16/50; retrieval of audio data G06F16/60; retrieval of video data G06F16/70

Abstract

A method includes determining, by a processor, that a write request indicates a clone file that was cloned from a file in a first fileset. The clone file is of a second fileset and a clustered file system comprises the first fileset and the second fileset. A data block of the clone file affected by the write request is determined. The method includes determining that the data block at a current location cannot be modified. In response to a determination that the data block at the current location cannot be modified, the method includes implementing the write request with respect to the data block at a different location and indicating that the data block at the different location can be modified for subsequent write requests that indicate the clone file.

Claims

1. A method comprising:

determining, by a processor, that a write request indicates a clone file that was cloned from a file in a first fileset, wherein the clone file is of a second fileset and a clustered file system comprises the first fileset and the second fileset;

determining a data block of the clone file affected by the write request;

determining that the data block at a current location cannot be modified; and

in response to a determination that the data block at the current location cannot be modified,

implementing the write request with respect to the data block at a different location; and

indicating that the data block at the different location can be modified for subsequent write requests that indicate the clone file.

2. The method of claim 1 further comprising generating the metadata for the clone file based, at least in part, on metadata of the file in the first fileset in response to a request to clone the file from the first fileset into the second fileset.

3. The method of claim 2, wherein the metadata for the clone file indicates the second fileset and the initial metadata of the data block indicates the first fileset.

4. The method of claim 1 further comprising:

causing a snapshot of at least the file in the first fileset to be created in response to a request to clone the file from the first fileset into the second fileset; and

associating the snapshot with the clone file.

5. The method of claim 4 further comprising preventing removal or deletion of the snapshot while the clone file is associated with the snapshot.

6. The method of claim 4 further comprising indicating in the metadata of the clone file that the clone file is a clone.

7. The method of claim 1, wherein said determining that the clone file was cloned from a file in a first fileset comprises reading a clone indication in the metadata of the clone file, wherein the clone indications comprises at least one of a clone flag and a clone creation generation.

8. The method of claim 1, wherein said determining that the data block at the current location cannot be modified comprises at least one of:

determining that the data block is not associated with the second fileset;

determining that the data block belongs to a generation different than a generation of the second fileset; and

determining that the data block does not belong to a generation later than a generation of creation of the clone file.

9. The method of claim 1, wherein said implementing the write request with respect to the data block at the different location comprises implementing the write request in accordance with redirect-on-write.

10. The method of claim 9, wherein said implementing the write request in accordance with redirect-on-write comprises indicating to a requestor of the write request that modification of the data block will be done in accordance with redirect-on-write.

11. The method of claim 1, wherein said indicating that the data block at the different location can be modified for subsequent write requests that indicate the clone file comprises updating metadata of the data block to indicate the second fileset.

12. The method of claim 11, wherein said indicating that the data block at the different location can be modified for subsequent write requests that indicate the clone file also comprises updating the metadata of the data block to indicate a current generation of the clone file.