Avoiding inode number conflict during metadata restoration

Patent metadata

Field	Value
Publication number	US-9965361-B2
Application number	US-201514926218-A
Country	US
Kind code	B2
Filing date	Oct 29, 2015
Priority date	Oct 29, 2015
Publication date	May 8, 2018
Grant date	May 8, 2018

Abstract

A method for avoiding inode number conflict during metadata restoration at a restoration location is provided. The method includes receiving metadata for a first file including an inode containing an initial internal inode number and a directory entry containing an external inode number, determining an allocation status of the initial internal inode number at the restoration location, identifying an available internal inode number to be allocated to the first file, updating the initial internal inode number in the inode for the first file with the available internal inode number, registering the available internal inode number and the external inode number in an inode mapping table indicating correspondence between the available internal inode number and the external inode number, and restoring the inode based on the available internal inode number.

First claim

What is claimed is:

1. A method for avoiding inode number conflict during metadata restoration at a restoration location, the method comprising:
receiving metadata associated with a first file generated at another location, wherein the metadata comprises an inode containing an initial internal inode number and a directory entry containing an external inode number;
determining an allocation status of the initial internal inode number at the restoration location;
identifying, based on the allocation status of the initial internal inode number being allocated to another file at the restoration location, an available internal inode number to be allocated to the first file;
updating the initial internal inode number in the inode associated with the first file with the available internal inode number;
registering the available internal inode number and the external inode number in an inode mapping table, wherein the inode mapping table indicates correspondence between the available internal inode number and the external inode number; and
restoring the inode based on the available internal inode number.

2. The method according to claim 1 , further comprising:
restoring the directory entry.

3. The method according to claim 1 , wherein the metadata associated with the first file further comprises a file-tape mapping table indicating correspondence between the external inode number and a location on a backup medium containing data associated with the first file.

4. The method according to claim 3 , further comprising:
receiving the backup medium.

5. The method according to claim 1 , wherein the directory entry indicates correspondence between the external inode number and a filename associated with the first file.

6. The method according to claim 1 , wherein the directory entry is provided in a directory entry table.

7. The method according to claim 1 , further comprising:
providing an internal inode allocation table indicating an allocation status of a plurality of internal inode numbers at the restoration location; and
wherein determining the allocation status of the initial internal inode number at the restoration location is based on the internal inode allocation table.

8. The method according to claim 7 , wherein the internal inode allocation table is a bitmap data structure.

9. The method according to claim 1 , wherein the first file is part of a first fileset and the another file is not part of the first fileset.

10. The method according to claim 9 , wherein the another file is part of another fileset.

11. The method according to claim 9 , wherein the inode mapping table is associated with the first fileset.

12. The method according to claim 1 , wherein the restoration location contains metadata associated with the another file comprising another inode and another directory entry, wherein the another inode contains an allocated internal inode number and the another directory entry contains another external inode number.

13. The method according to claim 1 , wherein the method repeats for each inode to be restored at the restoration location.

14. A computer program product for avoiding inode number conflict during metadata restoration at a restoration 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:
receiving metadata associated with a first file generated at another location, wherein the metadata comprises an inode containing an initial internal inode number and a directory entry containing an external inode number;
providing an inode allocation table indicating an allocation status of a plurality of internal inode numbers at the restoration location;
determining, based on the inode allocation table, an allocation status of the initial internal inode number;
identifying, based on the allocation status of the initial internal inode number being allocated to another file at the restoration location, an available internal inode number to be allocated to the first file;
updating the initial internal inode number in the inode associated with the first file with the available internal inode number;
registering the available internal inode number and the external inode number in an inode mapping table, wherein the inode mapping table indicates correspondence between the available internal inode number and the external inode number; and
restoring the inode based on the available internal inode number.

15. The computer program product according to claim 14 , further comprising:
restoring the directory entry.

16. The computer program product according to claim 14 , wherein the first file is part of a first fileset and the another file is not part of the first fileset.

17. The computer program product according to claim 16 , wherein the inode mapping table is associated with the first fileset.

18. A computer system for avoiding inode number conflict during metadata restoration at a restoration location, the computer system comprising:
at least one processing unit;
at least one computer readable memory;
at least one computer readable tangible, non-transitory storage medium; and program instructions stored on the at least one computer readable tangible, non-transitory storage medium for execution by the at least one processing unit via the at least one computer readable memory, wherein the program instructions comprise program instructions for:
receiving metadata associated with a first file generated at another location, wherein the metadata comprises an inode containing an initial internal inode number and a directory entry containing an external inode number;
providing an inode allocation table indicating an allocation status of a plurality of internal inode numbers at the restoration location;
determining, based on the inode allocation table, an allocation status of the initial internal inode number;
identifying, based on the allocation status of the initial internal inode number being allocated to another file at the restoration location, an available internal inode number to be allocated to the first file;
updating the initial internal inode number in the inode associated with the first file with the available internal inode number;
registering the available internal inode number and the external inode number in an inode mapping table, wherein the inode mapping table indicates correspondence between the available internal inode number and the external inode number; and
restoring the inode based on the available internal inode number.

19. The computer system according to claim 18 , further comprising:
restoring the directory entry.

20. The computer system according to claim 18 , wherein the first file is part of a first fileset and the another file is not part of the first fileset.

Assignees

• IBM

Inventors

• Iwasaki Norie
• Matsui Sosuke
• Miyamura Tsuyoshi
• Yamamoto Noriko

Classifications

• G06F16/2365

  Ensuring data consistency and integrity · CPC title

• G06F16/183

  Provision of network file services by network file servers, e.g. by using NFS, CIFS (network file access protocols H04L67/1097) · CPC title

• G06F11/1448

  Management of the data involved in backup or backup restore · CPC title

• G06F16/958 Primary

  Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking · CPC title

• G06F2201/84

  Using snapshots, i.e. a logical point-in-time copy of the data · CPC title