NFS server, NFS server control program and NFS server control method

Abstract

An NFS server, an NFS server control program and an NFS control method can reduce the extended lock reacquisition period. The NFS server comprises a prior-to-restart lock acquiring client information recording section for recording the identifiers of the NFS clients that have acquired locks before a restart of the NFS server and the number of the first files that is the number of files for which locks have been acquired, a lock acquiring client information recording section for recording the identifiers of the NFS clients that have reacquired locks after the restart of the NFS server and the number of the second files that is the number of files for which lock have been reacquired and an NSM that ends the reception of any lock reacquisition request from any of the NFS clients when the number of the second files of all the NFS clients acquired by the prior-to-restart lock acquiring client information recording section becomes equal to the number of the first files.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic block diagram of an NFS to which the present invention is applicable, illustrating the configuration and the operation of a lock acquisition process thereof;

FIG. 2 is a schematic block diagram of the NFS of FIG. 1, illustrating the configuration and the operation of a lock reacquisition process thereof;

FIG. 3 is a schematic block diagram of a known NFS, illustrating the configuration and the operation of a lock acquisition process thereof; and

FIG. 4 is a schematic block diagram of the known NFS of FIG. 3, illustrating the configuration and the operation of a lock reacquisition process thereof.

Claims

1. An NFS server for control the locks of an NFS, the NFS server comprising: a first lock information acquiring section that acquires the identifiers of the NFS clients that acquired locks before a restart of the NFS server and a first number of files that is the number of files for which the NFS clients have acquired the locks;a second lock information acquiring section that acquires the identifiers of the NFS clients that reacquired the locks after a restart of the NFS server and a second number of files that is the number of files for which the NFS clients have reacquired the locks; anda lock reacquisition ending section that ends the reception of lock reacquisition requests from NFS clients when the second number of files of all the NFS clients acquired by the first lock information acquiring section has become equal to the first number of files according to the first number of files acquired by the first lock information acquiring section for each NFS client and the second number of files acquired by the second lock information acquiring section for each NFS client.

2. The NFS server according to claim 1, wherein, when a predefined extended lock reacquisition period has elapsed after a restart of the NFS server, the lock reacquisition ending section ends the reception of a lock reacquisition request from any of the NFS clients.

3. The NFS server according to claim 1, wherein, if there is an NFS client that has not transmitted any lock reacquisition request at all among the NFS clients recorded in the first lock information recording section at the time when a predefined client operation confirmation period has elapsed after a restart of the NFS server, the lock reacquisition ending section ends the reception of lock reacquisition requests from the NFS client.

4. The NFS server according to claim 3, wherein, when the lock reacquisition ending section ends the reception of a lock reacquisition request from a specific NFS client, it changes the number of the first files of the NFS client to nil (0).

5. The NFS server according to claim 1, wherein, if there is an NFS client that has not transmitted any lock reacquisition request at all among the NFS clients recorded in the first lock information recording section by the time when a predefined client operation confirmation period has elapsed after the restart of the NFS server, the lock reacquisition ending section ends the reception of any lock reacquisition request from any of all the NFS clients.

6. The NFS server according to claim 3, wherein the client operation confirmation period is shorter than the extended lock reacquisition period.

7. The NFS server according to claim 1, wherein the second lock information acquiring section additionally records the clock times of the lock reacquisition requests from NFS clients and other information.

8. The NFS server according to claim 1, further comprising: a nonvolatile recording section for recording the identifiers of the NFS clients that have acquired locks before a restart of the NFS server and the number of the first files of such NFS clients.

9. An NFS server control program for causing the computer of an NFS server to control the locks of an NFS, the program comprising: a first lock information acquiring step that acquires the identifiers of the NFS clients that acquired locks before a restart of the NFS server and a first number of files that is the number of files for which the NFS clients have acquired the locks;a second lock information acquiring step that acquires the identifiers of the NFS clients that reacquired the locks after a restart of the NFS server and a second number of files that is the number of files for which the NFS clients have reacquired the locks; anda lock reacquisition ending step that ends the reception of lock reacquisition requests from NFS clients when the second number of files of all the NFS clients acquired in the first lock information acquiring step has become equal to the first number of files according to the first number of files acquired in the first lock information acquiring step for each NFS client and the second number of files acquired in the second lock information acquiring step for each NFS client.

10. The program according to claim 9, wherein, when a predefined extended lock reacquisition period has elapsed after a restart of the NFS server, the lock reacquisition ending step ends the reception of a lock reacquisition request from any of the NFS clients.

11. The program according to claim 9, wherein if there is an NFS client that has not transmitted any lock reacquisition request at all among the NFS clients recorded in the first lock information recording step at the time when a predefined client operation confirmation period has elapsed after a restart of the NFS server, the lock reacquisition ending step ends the reception of lock reacquisition requests from the NFS client.

12. The program according to claim 11, wherein, when the lock reacquisition ending step ends the reception of a lock reacquisition request from a specific NFS client, it changes the number of the first files of the NFS client to nil (0).

13. The program according to claim 9, wherein, if there is an NFS client that has not transmitted any lock reacquisition request at all among the NFS clients recorded in the first lock information recording step by the time when a predefined client operation confirmation period has elapsed after the restart of the NFS server, the lock reacquisition ending step ends the reception of any lock reacquisition request from any of all the NFS clients.

14. The program according to claim 11, wherein the client operation confirmation period is shorter than the extended lock reacquisition period.

15. The program according to claim 9, wherein the second lock information acquiring step additionally records the clock times of the reacquisition requests from NFS clients and other information.

16. The program according to claim 9, wherein the identifiers of the NFS clients that have acquired locks before a restart of the NFS server and the number of the first files of such NFS clients are recorded in a nonvolatile recording apparatus of the NFS server before the restart of the NFS server.

17. An NFS server control method for controlling the locks of an NFS, the method comprising: a first lock information acquiring step that acquires the identifiers of the NFS clients that acquired locks before a restart of the NFS server and a first number of files that is the number of files for which the NFS clients have acquired the locks;a second lock information acquiring step that acquires the identifiers of the NFS clients that reacquired the locks after a restart of the NFS server and a second number of files that is the number of files for which the NFS clients have reacquired the locks; anda lock reacquisition ending step that ends the reception of lock reacquisition requests from NFS clients when the second number of files of all the NFS clients acquired in the first lock information acquiring step has become equal to the first number of files according to the first number of files acquired in the first lock information acquiring step for each NFS client and the second number of files acquired in the second lock information acquiring step for each NFS client.

18. The method according to claim 17, wherein, when a predefined extended lock reacquisition period has elapsed after a restart of the NFS server, the lock reacquisition ending step ends the reception of a lock reacquisition request from any of the NFS clients.

19. The method according to claim 17, wherein if there is an NFS client that has not transmitted any lock reacquisition request at all among the NFS clients recorded in the first lock information recording step at the time when a predefined client operation confirmation period has elapsed after a restart of the NFS server, the lock reacquisition ending step ends the reception of lock reacquisition requests from the NFS client.

20. The method according to claim 19, wherein, when the lock reacquisition ending step ends the reception of a lock reacquisition request from a specific NFS client, it changes the number of the first files of the NFS client to nil (0).