File system encapsulation
View Patent ↗A method, system, and apparatus to encapsulate one or more file systems in a union of file systems without modifying or copying information in each file directory entry in each file system are presented. In one embodiment, this is accomplished in part by linking an inode list file from the file system to be encapsulated with an inode list file of the union of file systems, and merging a free extent map of the to-be-encapsulated file system with the free extent map file of the union file system.
1. A method comprising:
linking a first inode list to a union inode list, wherein
a first file system comprises the first inode list,
a union file system comprises the union inode list, the union inode list comprises inodes for the union file system, and
said linking permits access to files in the first file system by referencing the union inode list;
merging a first free extent map with a union free extent map, wherein
the first file system further comprises the first free extent map, and
the union file system faker comprises the union free extent map; and
storing the union inode list and the union free extent map in a storage object associated with the union file system.
2. The method of claim 1 wherein said linking comprises:
creating an inode reference in the union file system corresponding to a location of the first inode list in the first file system.
3. The method of claim 1 wherein said linking comprises:
copying the first inode list to the union file system.
4. The method of claim 3 wherein said copying comprises:
concatenating the first inode list onto the union inode list; and
maintaining a starting offset of the first inode list as concatenated onto the union inode list in the union file system.
5. The method of claim 1 further comprising;
merging a first set of structural files describing the first file system with a union set of structural files describing the union file system, wherein
the first set of structural files includes one or more of a fileset header file, an inode allocation unit file, an extent allocation unit summary file, and a quotas file.
6. The method of claim 1 further comprising:
storing a first directory entry in the union file system corresponding to data associated with the first file system, wherein
the first file system is associated with a first fileset, and
the first directory entry includes
a first fileset identifier corresponding to the first fileset, and
a first inode value corresponding to a location of the data stored in the first fileset.
7. The method of claim 6 further comprising:
renaming a second directory entry to create the first directory entry, wherein
the second directory entry is stored in the first fileset, and
the second directory entry includes the first inode value corresponding to the location of the data stored in the first fileset.
8. The method of claim 6 further comprising:
creating a third directory entry in the first fileset, wherein
the third directory entry includes a third fileset identifier; and
flagging the third directory entry, wherein
said flagging indicates that the third directory entry includes the third fileset identifier.
9. The method of claim 8 wherein said flagging comprises:
providing a pointer to a first reserved inode in the first fileset.
10. The method of claim 8 , wherein
the third directory entry corresponds to data referenced by a second fileset, wherein
the third fileset identifier corresponds to the second fileset.
11. The method of claim 1 further comprising:
allocating an extent from a set of free extents associated with the first file system, wherein
the set of free extents is designated in the union free extent map; and
using the allocated extent to store data for a file whose initial extents are stored in the union file system.
12. The method of claim 1 further comprising:
allocating an extent from a set of free extents associated with the union file system, wherein
the set of free extents is designated in the union free extent map;
using the allocated extent to store data for a file whose initial extents are stored in the first file system;
identifying the allocated extent with an extent identifier that comprises
a fileset identifier corresponding to the fileset in which the allocated extent is located; and
flagging the extent identifier, wherein
said flagging indicates that the extent identifier comprises the fileset identifier.
13. A computer-readable storage medium comprising:
a first set of instructions, executable on a computer system, configured to link a first inode list to a union inode list, wherein
a first file system comprises the first inode list,
a union file system comprises the union inode list, the union inode list comprises inodes for the union file system, and
said link permits access to files in the first file system by referencing the union inode list;
a second set of instructions, executable on the computer system, configured to merge a first free extent map with a union free extent map, wherein the first file system further comprises the first free extent map, and the union file system further comprises the union free extent map, and
a third set of instructions, executable on the computer system, configured to store the union inode list and the union free extent map in a storage object associated with the union file system.
14. The computer-readable storage medium of claim 13 further comprising:
a fourth set of instructions, executable on the computer system, configured to store a first directory entry in the union file system corresponding to data referenced by a first fileset, wherein
the first file system further comprises the first fileset, and
the first directory entry includes
a first fileset identifier corresponding to the first fileset, and
a first inode value corresponding to a location of the data stored in the first fileset.
15. The computer-readable storage medium of claim 14 further comprising:
a fifth set of instructions, executable on the computer system, configured to rename a second directory entry to create the first directory entry, wherein
the second directory entry is stored in the first fileset, and
the second directory entry includes the first inode value corresponding to the location of the data stored in the first fileset.
16. The computer-readable storage medium of claim 14 further comprising:
a fifth set of instructions, executable on the computer system, configured to create a third directory entry in the first fileset, wherein
the third directory entry includes a third fileset identifier; and
a sixth set of instructions, executable on the computer system, configured to flag the third directory entry, wherein
said flag indicates that the third directory entry comprises the third fileset identifier.
17. The computer-readable storage medium of claim 13 further comprising:
a fourth set of instructions, executable on the computer system, configured to allocate an extent from a set of free extents associated with the first file system, wherein
the set of free extents is designated in the union free extent map; and
a fifth set of instructions, executable on the computer system, configured to use the allocated extent to store data for a file whose initial extents are stored in the union file system.
18. An apparatus comprising:
a processor;
a memory coupled to the processor and comprising one or more storage objects;
a first file system comprising a first inode list and a first free extent map, wherein the first file system is stored on a first set of storage objects of the one or more storage objects;
a union file system comprising a union inode list and a union free extent map, wherein
the union file system is stored on a second set of storage objects of the one or more storage objects, and
the union inode list comprises inodes for the union file system;
means for linking the first inode list to the union inode list, wherein said linking permits access to files in the first file system by referencing the union inode list; and
means for merging the first free extent map with the union free extent map.
19. The apparatus of claim 18 further comprising:
the first file system further comprises a first fileset, wherein
the first fileset comprises data stored in the first fileset;
means for storing in the union file system a first directory entry corresponding to the data stored in the first fileset, wherein
the first directory entry includes
a first fileset identifier corresponding to the first fileset, and
a first inode value corresponding to a location of the data stored in the first fileset.
20. The apparatus of claim 19 further comprising:
a second file system comprising a second fileset;
means for creating a second directory entry in the first fileset, wherein
the second directory entry includes a second fileset identifier; and
means for flagging the second directory entry, wherein
said flagging indicates that the second directory entry includes the second fileset identifier.
21. A system comprising:
a first storage object comprising a first file system, wherein
the first file system comprises a first inode list and a first free extent map;
a second storage object comprising a union file system, wherein
the union file system comprises a union inode list and a union free extent map, and
the union inode list comprises inodes for the union file system; and
a processor coupled to the first and second storage objects and configured to
link the first inode list to the union inode list and
merge the first free extent map with the union free extent map, wherein
said link permits access to files in the first file system by referencing the union inode list.
22. The system of claim 21 , wherein:
the first file system further comprises a first fileset, wherein
the first fileset comprises data stored in the first fileset; and
the processor is further configured to
store a first directory entry in the union file system corresponding to the data stored in the first fileset, wherein
the first directory entry includes
a first fileset identifier corresponding to the first fileset, and
a first inode value corresponding to a location of the data stored in the fit fileset.