Allocating non-conflicting inode numbers

Patent metadata

Field	Value
Publication number	US-10713215-B2
Application number	US-201514940544-A
Country	US
Kind code	B2
Filing date	Nov 13, 2015
Priority date	Nov 13, 2015
Publication date	Jul 14, 2020
Grant date	Jul 14, 2020

Abstract

A method for allocating non-conflicting inode numbers between files generated at a first location and files generated at another location is provided. The method includes providing an inode number allocation rule table indicating availability for assignment a plurality of inode number allocation rules associated with the first location and the another location, generating a fileset at the first location by assigning an available inode number allocation rule to the fileset, registering, in the inode number allocation rule table, information associated with the fileset, and generating a file at the first location by determining the fileset within which to generate the file; and allocating an inode number for the file based on the available inode number allocation rule assigned to the fileset.

First claim

What is claimed is:

1. A method for allocating non-conflicting inode numbers between files generated at a first location and files generated at a second location, the method comprising:
providing an inode number allocation rule table comprising an inode number allocation rule column and an allocation status column, the inode number allocation rule column listing a plurality of inode number allocation rules for generating unique inode numbers for files associated with the first location, the second location, and an unassigned location, wherein the allocation status column indicates an assigned status for each inode number allocation rule of the plurality of inode number allocation rules that are assigned to one of the first location and the second location and an unassigned status for each inode number allocation rule of the plurality of inode number allocation rules that are not yet assigned to one of the first location and the second location, wherein the inode number allocation rule table includes at least one inode number allocation rule having the unassigned status, wherein the unassigned status indicates an availability of the at least one inode number allocation rule for assignment to one of the first location and the second location, and wherein the first location is on a first server and the second location is on a second server;
generating a fileset at the first location comprising:
referencing the inode number allocation rule table to identify the at least one inode number allocation rule having the unassigned status;
assigning the at least one inode number allocation rule having the unassigned status to the fileset at the first location;
changing, in the allocation status column of the inode number allocation rule table, the unassigned status of the at least one inode number allocation rule to the assigned status;
registering, in the inode number allocation rule table, information associated with the fileset comprising at least one of a fileset ID, a mount point, and an identification for the first location; and

generating a file at the first location comprising:
determining the fileset within which to generate the file; and
allocating an inode number for the file based on the assigned inode number allocation rule associated with the determined fileset.

2. The method according to claim 1 , further comprising:
generating another fileset at the second location comprising:
assigning another available inode number allocation rule to the another fileset; and
registering, in the inode number allocation rule table, information associated with the another fileset comprising at least one of another fileset ID, another mount point, and an identification for the second location; and

generating another file at the second location comprising:
determining the another fileset within which to generate the another file; and
allocating another inode number for the another file based on the assigned another available inode number allocation rule associated with the determined another fileset; and
wherein the allocated another inode number for the another file is different from the allocated inode number for the file.

3. The method according to claim 1 , wherein each inode number allocation rule from the plurality of inode number allocation rules determines a set of inode numbers that are different from sets of other inode numbers determined by other inode number allocation rules from the plurality of inode number allocation rules.

4. The method according to claim 1 , wherein the second location contains one or more files with an associated inode number from an initial set of inode numbers, and the assigned inode number allocation rule associated with the fileset allocates another set of inode numbers different from the initial set of inode numbers.

5. The method according to claim 4 , wherein the initial set of inode numbers are allocated by one or more previously assigned inode number allocation rules, and the assigned inode number allocation rule associated with the fileset allocates a first inode number different from a second inode number allocated by each of the one or more previously assigned inode number allocation rules.

6. The method according to claim 1 , wherein generating the fileset at the first location further comprises:
updating the availability of the assigned inode number allocation rule associated with the fileset.

7. The method according to claim 1 , further comprising:
restoring the generated file at the second location based on the allocated inode number for the file.

8. The method according to claim 1 , wherein the inode number allocation rule table is managed by an associated server corresponding to one of the first location and the second location.

9. The method according to claim 1 , wherein the inode number allocation rule table is managed by an external server.

10. The method according to claim 1 , further comprising:
a second inode number allocation rule table, wherein the second inode number allocation rule table is synchronized with the inode number allocation rule table.

11. The method according to claim 10 , wherein the inode number allocation rule table is managed by the first server associated with the first location and the second inode number allocation rule table is managed by the second server associated with the second location.

12. A computer program product for allocating non-conflicting inode numbers between files generated at a first location and files generated at a second location, the computer program product comprising at least one computer readable non-transitory storage medium having computer readable program instructions thereon for execution by a processor, the computer readable program instructions comprising program instructions for:
providing an inode number allocation rule table comprising an inode number allocation rule column and an allocation status column, the inode number allocation rule column listing a plurality of inode number allocation rules for generating unique inode numbers for files associated with the first location, the second location, and an unassigned location, wherein the allocation status column indicates an assigned status for each inode number allocation rule of the plurality of inode number allocation rules that are assigned to one of the first location and the second location and an unassigned status for each inode number allocation rule of the plurality of inode number allocation rules that are not yet assigned to one of the first location and the second location, wherein the inode number allocation rule table includes at least one inode number allocation rule having the unassigned status, wherein the unassigned status indicates an availability of the at least one inode number allocation rule for assignment to one of the first location and the second location, and wherein the first location is on a first server and the second location is on a second server;
generating a fileset at the first location comprising:
referencing the inode number allocation rule table to identify the at least one inode number allocation rule having the unassigned status;
assigning the at least one inode number allocation rule having the unassigned status to the fileset at the first location;
changing, in the allocation status column of the inode number allocation rule table, the unassigned status of the at least one inode number allocation rule to the assigned status;
registering, in the inode number allocation rule table, information associated with the fileset comprising at least one of a fileset ID, a mount point, and an identification for the first location; and

generating a file at the first loc

Assignees

• IBM

Inventors

• Hasegawa Tohru
• Matsui Sosuke
• Narita Izuru

Classifications

• G06F16/122 Primary

  using management policies (point-in-time backing up or restoration of persistent data G06F11/1446; file migration policies for HSM systems G06F16/185) · CPC title

• G06F16/178

  Techniques for file synchronisation in file systems · CPC title