Distributed file system

A file send and receive method utilized in a distributed file system,

• wherein said distributed file system includes a storage device for holding files, multiple clients for carrying out file operations on said storage device, a server using tokens to control rights to file reading and writing operations by the clients, and a network coupling said clients, said storage device and said server, said method comprising:
• making a request to said server for a token for rights to perform said file operations, wherein a first client makes the request to said server;
• sending, by said server, said token revoke request to a second client that holds write operation rights to said file, so as to request a return of the token for said write operation rights,
• wherein said token revoke request includes information identifying the first client that requested the token for said file, and information indicating a level of the token requested by said first client, said level being either read or write;
• and
• sending, by said second client that received said token revoke request, the file for said token held in said memory section, to the first client that requested the token for said file,
• wherein said first client that received the token revoke request sends data in a range among files linked by said token to the server for said second client that requested said token, and performs synchronous processing on said storage device by writing data in a range among files not linked by said token on said storage device, and
• wherein said first client that received the token revoke request, decides whether to send the file being held to the server for the second client making the request for said token, or to write the file in said storage device and perform synchronous processing of said store device, based on an input/output capacity of said network and said storage device, and a data size of the file sent to the server for the second client that requested the token.

A first client device utilized in a distributed file system, wherein said distributed file system includes a storage device for holding files, multiple client devices for carrying out file operations on said storage device, a server using tokens to control rights to file reading and writing operations by the client devices, and a network coupling said clients devices, said storage device and said server, said first client device comprising:

• a memory section for holding file data loaded from said storage device;
• and a data output means for sending a file relating to a token held in said memory section to a second client device that requested the token for said file when a request for returning said token for rights to read or write on said file is received by said first client device from said server,
• wherein said request includes information identifying said second client that requested said token for said file, and information indicating a level of said token requested by said second client, said level being either read or write,
• wherein said data output means sends data in a range among said files linked by said token, to said server for said second client that requested said token, and performs synchronous processing on said storage device by writing data in a range among files not linked by said token, and
• wherein said data output means decides whether to send the file being held to the server for the second client that requested said token, or to write the file in said storage device and perform synchronous processing of said storage device, based on an input/output capacity of said network and said storage device and a data size of the file sent to the server for the second client that requested the token.

A program embedded on a computer-readable storage medium, wherein the program is executed on a server device for controlling tokens for rights to file reading and writing by a first client coupled via a storage device and network, wherein said first client requests a token for rights to file reading or writing, and wherein said program causes the server device to:

• send a request for a return of said token for rights to file reading or writing, to a second client that holds rights to read or write on a file,
• wherein said request includes information identifying said first client that requested said token for said file, and information indicating a level of said token requested by said request client, said level being either read or write,
• wherein said first client that received the token revoke request sends data in a range among files linked by said token to the server for said second client that requested said token, and performs synchronous processing on said storage device by writing data in a range among files not linked by said token on said storage device, and
• wherein said first client that received the token revoke request, decides whether to send the file being held to the server for the second client making the request for said token, or to write the file in said storage device and perform synchronous processing of said storage device, based on an input/output capacity of said network and said storage device, and a data size of the file sent to the server for the second client that requested the token.

A program embedded on a computer-readable storage medium,

• wherein the program is executed on a first client device for controlling rights to reading and writing of files stored on a storage device coupled by a network, by utilizing tokens managed by a server, wherein said first client requests a token for the rights to reading and writing, and
• wherein said program causes the first client device to:
• send a file relating to the token held in said storage section to a second client device that requested said token for said file, when a request to revoke said token for rights to write on said file is sent from said server,
• wherein said request includes information identifying said second client that requested said token for said file, and information indicating a level of said token requested by said second client, said level being either read or write,
• wherein said first client that received the token revoke request sends data in a range among files linked by said token to the server for said second client that requested said token, and performs synchronous processing on said storage device by writing data in a range among files not linked by said token on said storage device, and
• wherein said first client that received the token revoke request, decides whether to send the file being held to the server for the second client making the request for said token, or to write the file in said storage device and perform synchronous processing of said storage device, based on an input/output capacity of said network and said storage device, and a data size of the file sent to the server for the second client that requested the token.