CN113986855B - Method, system, equipment and medium for locking files by network file system - Google Patents

Abstract

The invention proposes a method, system, equipment and medium for locking files in a network file system. The method includes receiving a file locking request and generating a locking record; if the original file lock list queried according to the locking record does not have the same and same range of locking records, nor does it have conflicting locks; then add the locking record to Obtain the first file lock list from the original file lock list, and write the first file lock list into the database; then perform file locking. This method includes file unlocking, file repair and file sharing. Based on this method, a system, device and medium for locking files in a network file system are also proposed. The present invention restores the previous lock status based on the data recorded in the database, maintains the continuity of the lock status, improves the use experience of the NFS network file system, enables the NFS process to realize fault recovery for all file lock requests, and improves the stability of the NFS. performance and reliability.

Description

A method, system, device and medium for locking files in a network file system

Technical field

The invention belongs to the technical field of file storage, and in particular relates to a method, system, equipment and medium for locking files in a network file system.

Background technique

NFS (Network File System) is a network file system. It is one of the file systems supported by FreeBSD. It allows resources to be shared between computers on the network. In NFS applications, local NFS client applications can transparently read and write files located on the remote NFS server, just like accessing local files. NFS sharing service is a service process that provides file sharing in NAS cluster storage systems. The characteristics of storage require that such processes must run stably for a long time, especially for dual-control storage systems.

After the NFS-server process fails and is restarted or the storage node fails, the lock status information previously added to the file by the client through the NFS network file system will be lost, resulting in the actual lock status on the storage node and client, causing the client's NFS There is a problem with the application.

Contents of the invention

In order to solve the above technical problems, the present invention proposes a method, system, device and medium for locking files in a network file system. It realizes file locking and overcomes the defects of file locking, so that the network file system process can realize fault recovery for all file lock requests, which improves the stability and reliability of the network file system.

In order to achieve the above objects, the present invention adopts the following technical solutions:

A method for locking files in a network file system, including the following steps:

Receive file locking requests and generate locking records;

If the original file lock list queried based on the lock record does not have the same and same range of lock records, nor does it have conflicting locks; then add the lock record to the original file lock list to obtain the first file lock list, And write the first file lock list into the database; then perform file locking.

Further, the method also includes unlocking the file; the process of unlocking the file is:

Receive file unlocking request; generate unlocking record;

Delete the unlocking record from the first file lock list to obtain a second file lock list, perform file unlocking, and synchronize the second file lock list to the database.

Further, the method also includes:

Traverse the second file lock list; determine whether the file still needs to be locked; if the second file lock list is not empty, obtain a lock record from the head of the second file lock list and perform file locking.

Further, the method also includes:

After the file is locked, the network file system process is restarted, and the network file system is first put into a silent state;

In the silent state, if the file needs to be restored to the locked state, the first file lock list is read from the database, and the file structure is initialized according to the lock record;

Traverse all locked records and restore previously locked records;

Exit the quiescent state after the recovery is complete.

Further, the method also includes:

If the current node fails, the network file system shared resources of the current node are switched to the backup node;

After switching to the standby node, determine whether the file needs to be restored to the locked state. If the locked state needs to be restored, make the network file system enter a silent state, then read the file lock record corresponding to the current node from the database, and restore it as needed file structure, perform recovery, and exit the silent state after the recovery is completed.

Further, the method of querying the original file lock list for lock records that do not have the same and the same range includes:

According to the lock record, query whether the original file lock list has the same lock record. If it has the same lock record, it will return directly without locking;

According to the file lock range in the lock record, query whether there is a file lock covering the range in the original file lock list, and if so, return directly without locking.

Further, the conflicting locks include:

There is an exclusive lock with the same file lock range as in the lock record;

There is a shared lock with the same file lock range as in the lock record, and the current lock needs to be an exclusive lock.

The invention also proposes a system for locking files in a network file system. The system includes a receiving module and a locking module;

The receiving module is used to receive file locking requests and generate locking records;

The locking module is used to add the locking record to the original file lock list if the original file lock list does not have the same and same range of lock records or conflicting locks according to the lock record query. Obtain the first file lock list and write the first file lock list into the database; then perform file locking.

The invention also proposes a device, including:

Memory, used to store computer programs;

A processor configured to implement the method steps when executing the computer program.

The present invention also proposes a readable storage medium. A computer program is stored on the readable storage medium. When the computer program is executed by a processor, the method steps are implemented.

The effects provided in the summary of the invention are only the effects of the embodiments, rather than all the effects of the invention. One of the above technical solutions has the following advantages or beneficial effects:

The invention proposes a method, system, equipment and medium for locking files in a network file system. The method includes receiving a file locking request and generating a locking record; if the original file lock list queried according to the locking record does not have the same and same range of locking records, nor does it have conflicting locks; then add the locking record to Obtain the first file lock list from the original file lock list, and write the first file lock list into the database; then perform file locking. The method includes unlocking a file; the process of file unlocking is: receiving a file unlocking request; generating an unlocking record; deleting the unlocking record from the first file lock list to obtain a second file lock list, performing file unlocking, and locking the second file The list is synchronized to the database. Based on a method of locking files in a network file system, a system, device and medium for locking files in a network file system are also proposed. In the present invention, the file lock list is written into a database, and the database is a Ctdb database, that is, a distributed database, which can not only save data, but also achieve data synchronization between multiple nodes. This ensures that after the current node restarts or a failure causes the network file system sharing to switch to other nodes, the file lock information is synchronized. The file locks added before the failure are still valid after the failure or after the node switch, and will not be affected by the file lock. The inconsistent status causes file access problems in network file system client applications. All unfinished lock operations on files can be recorded persistently, so that after the NFS-server process fails and restarts or the node where the process is located fails and the shared resource is switched to other nodes, it can be restored based on the data recorded in the database ctdb. lock status, maintain the continuity of the lock status, and improve the user experience of the NFS network file system.

Description of the drawings

Figure 1 is a flow chart of a method for locking files in a network file system according to Embodiment 1 of the present invention;

Figure 2 is a flow chart of a method for unlocking files in a network file system according to Embodiment 1 of the present invention;

Figure 3 is a flow chart of a method for repairing network file system faults in Embodiment 1 of the present invention;

Figure 4 is a flow chart of a network file system fault sharing method according to Embodiment 1 of the present invention;

Figure 5 is a schematic diagram of a network file system locking files according to Embodiment 2 of the present invention.

Detailed ways

In order to clearly explain the technical features of this solution, the present invention will be described in detail below through specific implementation modes and in conjunction with the accompanying drawings. The following disclosure provides many different embodiments or examples for implementing different structures of the invention. In order to simplify the disclosure of the present invention, the components and arrangements of specific examples are described below. Furthermore, the present invention may repeat reference numbers and/or letters in different examples. This repetition is for purposes of simplicity and clarity and does not by itself indicate a relationship between the various embodiments and/or arrangements discussed. It should be noted that components illustrated in the figures are not necessarily to scale. Descriptions of well-known components and processing techniques and processes are omitted to avoid unnecessarily limiting the invention.

Example 1

Embodiment 1 of the present invention proposes a method for locking files in a network file system. The present invention provides the reception and processing of file lock requests in a network file system, and the recovery of file locks in a network file system under abnormal circumstances.

Figure 1 shows a flow chart of a method for locking files in a network file system according to Embodiment 1 of the present invention.

In step S101, receive the file lock request and generate a lock record;

NFS-server receives the lock request and generates a lock record, which includes the client identifier, file handle, starting position of the file lock, file lock range, file lock type, and file lock status. The initial file lock state is unlocked.

In step S102, if the original file lock list is queried according to the lock record and does not have the same and same range of lock records, nor does it have conflicting locks; then the lock record is added to the original file lock list to obtain the third Create a file lock list and write the first file lock list into the database; then perform file locking.

First, check whether there is the same lock record in the lock list based on the lock record. If there is the same lock record, it means that it is a duplicate lock and is returned directly;

According to the file lock range in the lock record, query whether there is a lock that can cover this range in the lock list, and if so, it will be returned directly.

According to the lock records in the lock list, compare one by one whether there are conflicting file locks. There are two situations of conflict. One is that there is already a file lock that adds an exclusive lock in the same range. The file lock currently being processed, whether it is a shared lock or an exclusive lock, conflicts with the existing lock. The second is that there is already a file lock that adds a shared lock in the same range. If the file lock currently to be processed is an exclusive lock, then the two locks will conflict. If there is a conflict, the state of the current file lock record needs to be changed to the block state, where the block state is the blocking state. If there is no conflict, you need to change the current file lock record status to the locking status and perform file locking.

Insert the current lock record into the lock list of the file structure (file_entry). Synchronously write the lock list of the file into the ctdb database

After the file locking is completed, Embodiment 1 of the present invention also proposes a file unlocking method. Figure 2 is a flow chart of a method for unlocking files in a network file system according to Embodiment 1 of the present invention.

In step S201, receive a file unlocking request; generate an unlocking record;

NFS-server receives the unlock request and finds the lock record based on the parameters passed by NFS-client.

In step S202, the unlocking record is deleted from the first file lock list to obtain a second file lock list, the file is unlocked, and the second file lock list is synchronized to the database.

Delete the lock record from the file's lock list, perform an unlock operation on the file, and synchronize the lock list to the ctdb database.

Traverse the file's lock list to determine whether the file needs to continue to be locked. If the lock list is not empty, take a lock record from the head of the lock list, modify the status of the lock record to the locking state, perform the actual locking operation on the file, and synchronize the lock to the ctdb database.

Figure 3 is a flow chart of a method for repairing network file system faults in Embodiment 1 of the present invention;

In step S301, after the file is locked, the network file system process is restarted, and the network file system is first put into a silent state;

The NFS-server process starts, the necessary initialization process of NFS-server, and the trial process enters a silent state. In the silent state, the process does not accept requests for unlocking and file modification to avoid inconsistencies.

In step S302, in the silent state, if the file needs to be restored to the locked state, the first file lock list is read from the database, and the file structure is initialized according to the lock record.

Based on the configuration of NFS-server, determine whether the lock state needs to be restored. Because not all application environments need to restore the lock state after a failure. For example, if the failure time has been long and it is meaningless to restore the lock state, the NFS-server process exits the silent state.

Read the lock list from the ctdb database. Because the process has just started at this time, there is no file_entry (file structure) for all files in the process, so the file_entry (file structure) needs to be initialized according to the needs of the lock record.

In step S303, all lock records are traversed and the records that have been locked are restored; all lock records are traversed and records with a locked status are restored, that is, the corresponding files are locked according to the content in the lock record.

In step S304, exit the silent state after the recovery is completed.

Traverse all lock records and restore the records with locked status, that is, lock the corresponding files according to the contents in the lock record. Figure 4 is a flow chart of a method for sharing a network file system in Embodiment 1 of the present invention.

In step S401, if the current node fails, the network file system shared resources of the current node are switched to the backup node;

After a node failure, the file system and NFS shared resources are switched to other nodes, such as node2. The file systems mentioned in the present invention are all single-node rather than distributed file systems, that is, a file system can only be mounted on one node at a time. The cluster on Node2 notifies the NFS-server process on this node that a node switch has occurred.

In step S402, it is determined whether the file needs to be restored to the locked state after switching to the standby node. If the locked state needs to be restored, the network file system is put into a silent state, and then the file lock record corresponding to the current node is read from the database. , and perform restoration according to the file structure that needs to be restored, and exit the silent state after the restoration is completed.

According to the configuration of NFS-server, determine whether the lock state needs to be restored;

If the lock state needs to be restored, the NFS-server process enters a partially silent state, that is, all requests received at this time need to be determined which file system they correspond to. If they correspond to the file system that has just been switched, the request will be discarded directly. ;

The NFS-server process reads the lock data corresponding to the failed node from the ctdb database, restores the file structure (file_entry) as needed, and restores the lock status based on the lock record;

After the Lock state recovery is completed, the NFS-server process exits the partially silent state.

Aiming at the defect of NFS service in locking files in the storage system, the present invention designs an improved method for NFS to lock files, so that the NFS process can realize fault recovery and sharing for all file lock requests, and improves the efficiency of NFS. stability and reliability.

Example 2

Based on the method for locking files in a network file system proposed in Embodiment 1 of the present invention, a system for locking files in a network file system is also proposed. Figure 5 is a schematic diagram of a network file system locking files according to Embodiment 2 of the present invention. The system includes a receiving module and a locking module;

The receiving module is used to receive file locking requests and generate locking records;

The locking module is used to query the original file lock list based on the locking record and there is no locking record of the same and the same range, nor does it have conflicting locks; then add the locking record to the original file lock list to obtain the first file lock list, and write the first file lock list into the database; then perform file locking.

The method of querying the original file lock list for locking records that do not have the same and the same range includes: querying the original file lock list according to the locking records to see if they all have the same locking records. If there are the same locking records, then Directly return without locking; query the original file lock list according to the file lock range in the lock record to see if there is a file lock covering the range. If so, directly return without locking.

Conflict locks include exclusive locks with the same file lock range as in the lock record; shared locks with the same file lock range as the lock record, and the current lock is an exclusive lock.

The system also includes unlocking, repairing and sharing modules;

The unlocking module is used to receive a file unlocking request; generate an unlocking record; delete the unlocking record from the first file lock list to obtain a second file lock list, perform file unlocking, and synchronize the second file lock list to the database. .

The repair module is used to restart the network file system process after the file is locked. First, the network file system enters a silent state; in the silent state, if the file needs to be restored to the locked state, the first file is read from the database. Lock list, initialize the file structure according to the lock record; traverse all the lock records, restore the records that have been locked; exit the silent state after the restoration is completed.

The sharing module is used to switch the network file system shared resources of the current node to the backup node if the current node fails; after judging whether the file needs to be restored to the locked state after switching to the backup node, if the file needs to be restored to the locked state, Then the network file system enters the silent state, and then reads the file lock record corresponding to the current node from the database, and restores it according to the file structure that needs to be restored, and exits the silent state after the recovery is completed.

Example 3

The invention also proposes a device, including:

Memory, used to store computer programs;

The processor is used to implement the method steps when executing the computer program as follows:

Figure 1 shows a flow chart of a method for locking files in a network file system according to Embodiment 1 of the present invention.

In step S101, receive the file lock request and generate a lock record;

NFS-server receives the lock request and generates a lock record, which includes the client identifier, file handle, starting position of the file lock, file lock range, file lock type, and file lock status. The initial file lock state is unlocked.

In step S102, if the original file lock list is queried according to the lock record and does not have the same and same range of lock records, nor does it have conflicting locks; then the lock record is added to the original file lock list to obtain the third Create a file lock list and write the first file lock list into the database; then perform file locking.

First, check whether there is the same lock record in the lock list based on the lock record. If there is the same lock record, it means that it is a duplicate lock and is returned directly;

According to the file lock range in the lock record, query whether there is a lock that can cover this range in the lock list, and if so, it will be returned directly.

According to the lock records in the lock list, compare one by one whether there are conflicting file locks. There are two situations of conflict. One is that there is already a file lock that adds an exclusive lock in the same range. The file lock currently being processed, whether it is a shared lock or an exclusive lock, conflicts with the existing lock. The second is that there is already a file lock that adds a shared lock in the same range. If the file lock currently to be processed is an exclusive lock, then the two locks will conflict. If there is a conflict, the state of the current file lock record needs to be changed to the block state, where the block state is the blocking state. If there is no conflict, you need to change the current file lock record status to the locking status and perform file locking.

Insert the current lock record into the lock list of the file structure (file_entry). Synchronously write the lock list of the file into the ctdb database

After the file locking is completed, Embodiment 1 of the present invention also proposes a file unlocking method. Figure 2 is a flow chart of a method for unlocking files in a network file system according to Embodiment 1 of the present invention.

In step S201, receive a file unlocking request; generate an unlocking record;

NFS-server receives the unlock request and finds the lock record based on the parameters passed by NFS-client.

In step S202, the unlocking record is deleted from the first file lock list to obtain a second file lock list, the file is unlocked, and the second file lock list is synchronized to the database.

Delete the lock record from the file's lock list, perform an unlock operation on the file, and synchronize the lock list to the ctdb database.

Traverse the file's lock list to determine whether the file needs to continue to be locked. If the lock list is not empty, take a lock record from the head of the lock list, modify the status of the lock record to the locking state, perform the actual locking operation on the file, and synchronize the lock to the ctdb database.

Figure 3 is a flow chart of a method for repairing network file system faults in Embodiment 1 of the present invention;

In step S301, after the file is locked, the network file system process is restarted, and the network file system is first put into a silent state;

The NFS-server process starts, the necessary initialization process of NFS-server, and the trial process enters a silent state. In the silent state, the process does not accept requests for unlocking and file modification to avoid inconsistencies.

In step S302, in the silent state, if the file needs to be restored to the locked state, the first file lock list is read from the database, and the file structure is initialized according to the lock record.

Based on the configuration of NFS-server, determine whether the lock state needs to be restored. Because not all application environments need to restore the lock state after a failure. For example, if the failure time has been long and it is meaningless to restore the lock state, the NFS-server process exits the silent state.

Read the lock list from the ctdb database. Because the process has just started at this time, there is no file_entry (file structure) for all files in the process, so the file_entry (file structure) needs to be initialized according to the needs of the lock record.

In step S303, all lock records are traversed and the records that have been locked are restored; all lock records are traversed and records with a locked status are restored, that is, the corresponding files are locked according to the content in the lock record.

In step S304, exit the silent state after the recovery is completed.

Traverse all lock records and restore the records with locked status, that is, lock the corresponding files according to the contents in the lock record. Figure 4 is a flow chart of a method for sharing a network file system in Embodiment 1 of the present invention.

In step S401, if the current node fails, the network file system shared resources of the current node are switched to the backup node;

After a node failure, the file system and NFS shared resources are switched to other nodes, such as node2. The file systems mentioned in the present invention are all single-node rather than distributed file systems, that is, a file system can only be mounted on one node at a time. The cluster on Node2 notifies the NFS-server process on this node that a node switch has occurred.

In step S402, it is determined whether the file needs to be restored to the locked state after switching to the standby node. If the locked state needs to be restored, the network file system is put into a silent state, and then the file lock record corresponding to the current node is read from the database. , and perform restoration according to the file structure that needs to be restored, and exit the silent state after the restoration is completed.

According to the configuration of NFS-server, determine whether the lock state needs to be restored;

If the lock state needs to be restored, the NFS-server process enters a partially silent state, that is, all requests received at this time need to be determined which file system they correspond to. If they correspond to the file system that has just been switched, the request will be discarded directly. ;

The NFS-server process reads the lock data corresponding to the failed node from the ctdb database, restores the file structure (file_entry) as needed, and restores the lock status based on the lock record;

After the Lock state recovery is completed, the NFS-server process exits the partially silent state.

Aiming at the defect of NFS service in locking files in the storage system, the present invention designs an improved method for NFS to lock files, so that the NFS process can realize fault recovery and sharing for all file lock requests, and improves the efficiency of NFS. stability and reliability.

It should be noted that the technical solution of the present invention also provides an electronic device, including: a communication interface capable of information interaction with other devices such as network equipment; a processor connected to the communication interface to realize information interaction with other devices. When running a computer program, a method for locking files in a network file system provided by one or more of the above technical solutions is executed, and the computer program is stored in the memory. Of course, in practical applications, various components in electronic equipment are coupled together through a bus system. It can be understood that the bus system is used to implement connection communication between these components. In addition to the data bus, the bus system also includes a power bus, a control bus and a status signal bus. The memory in the embodiment of the present application is used to store various types of data to support the operation of the electronic device. Examples of such data include: any computer program used to operate on an electronic device. It can be understood that the memory can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM, Read Only Memory), a programmable read-only memory (PROM, Programmable Read-Only Memory), an erasable programmable read-only memory (EPROM, Erasable Programmable Read-Only Memory). Only Memory), Electrically Erasable Programmable Read-Only Memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), Magnetic Random Access Memory (FRAM, ferromagnetic random access memory), Flash Memory (FlashMemory), Magnetic Surface Memory, Optical disk, or CD-ROM (Compact Disc Read-Only Memory); magnetic surface memory can be magnetic disk storage or tape storage. Volatile memory may be random access memory (RAM, Random Access Memory), which is used as an external cache. By way of illustration, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory Memory (DRAM, Dynamic Random Access Memory), synchronous dynamic random access memory (SDRAM, SynchronousDynamic Random Access Memory), double data rate synchronous dynamic random access memory (DDRSDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), enhanced Synchronous dynamic random access memory (ESDRAM, Enhanced Synchronous Dynamic Random Access Memory), synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), direct memory bus random access memory (DRRAM, Direct Rambus Random Access Memory). The memories described in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories. The methods disclosed in the above embodiments of the present application can be applied in a processor or implemented by the processor. The processor may be an integrated circuit chip that has signal processing capabilities. During the implementation process, each step of the above method can be completed by instructions in the form of hardware integrated logic circuits or software in the processor. The above-mentioned processor can be a general-purpose processor, DSP (Digital Signal Processing, which refers to a chip that can implement digital signal processing technology), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor can implement or execute each method, step, and logical block diagram disclosed in the embodiments of this application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, and the storage medium is located in a memory. The processor reads the program in the memory and completes the steps of the foregoing method in conjunction with its hardware. When the processor executes the program, the corresponding processes in each method of the embodiment of the present application are implemented. For the sake of simplicity, they will not be described again here.

Example 4

The present invention also proposes a readable storage medium. A computer program is stored on the readable storage medium. When the computer program is executed by a processor, the method steps are as follows:

Figure 1 shows a flow chart of a method for locking files in a network file system according to Embodiment 1 of the present invention.

In step S101, receive the file lock request and generate a lock record;

NFS-server receives the lock request and generates a lock record, which includes the client identifier, file handle, starting position of the file lock, file lock range, file lock type, and file lock status. The initial file lock state is unlocked.

In step S102, if the original file lock list is queried according to the lock record and does not have the same and same range of lock records, nor does it have conflicting locks; then the lock record is added to the original file lock list to obtain the third Create a file lock list and write the first file lock list into the database; then perform file locking.

First, check whether there is the same lock record in the lock list based on the lock record. If there is the same lock record, it means that it is a duplicate lock and is returned directly;

According to the file lock range in the lock record, query whether there is a lock that can cover this range in the lock list, and if so, it will be returned directly.

According to the lock records in the lock list, compare one by one whether there are conflicting file locks. There are two situations of conflict. One is that there is already a file lock that adds an exclusive lock in the same range. The file lock currently being processed, whether it is a shared lock or an exclusive lock, conflicts with the existing lock. The second is that there is already a file lock that adds a shared lock in the same range. If the file lock currently to be processed is an exclusive lock, then the two locks will conflict. If there is a conflict, the state of the current file lock record needs to be changed to the block state, where the block state is the blocking state. If there is no conflict, you need to change the current file lock record status to the locking status and perform file locking.

Insert the current lock record into the lock list of the file structure (file_entry). Synchronously write the lock list of the file into the ctdb database

After the file locking is completed, Embodiment 1 of the present invention also proposes a file unlocking method. Figure 2 is a flow chart of a method for unlocking files in a network file system according to Embodiment 1 of the present invention.

In step S201, receive a file unlocking request; generate an unlocking record;

NFS-server receives the unlock request and finds the lock record based on the parameters passed by NFS-client.

In step S202, the unlocking record is deleted from the first file lock list to obtain a second file lock list, the file is unlocked, and the second file lock list is synchronized to the database.

Delete the lock record from the file's lock list, perform an unlock operation on the file, and synchronize the lock list to the ctdb database.

Traverse the file's lock list to determine whether the file needs to continue to be locked. If the lock list is not empty, take a lock record from the head of the lock list, modify the status of the lock record to the locking state, perform the actual locking operation on the file, and synchronize the lock to the ctdb database.

Figure 3 is a flow chart of a method for repairing network file system faults in Embodiment 1 of the present invention;

In step S301, after the file is locked, the network file system process is restarted, and the network file system is first put into a silent state;

The NFS-server process starts, the necessary initialization process of NFS-server, and the trial process enters a silent state. In the silent state, the process does not accept requests for unlocking and file modification to avoid inconsistencies.

In step S302, in the silent state, if the file needs to be restored to the locked state, the first file lock list is read from the database, and the file structure is initialized according to the lock record.

Based on the configuration of NFS-server, determine whether the lock state needs to be restored. Because not all application environments need to restore the lock state after a failure. For example, if the failure time has been long and it is meaningless to restore the lock state, the NFS-server process exits the silent state.

Read the lock list from the ctdb database. Because the process has just started at this time, there is no file_entry (file structure) for all files in the process, so the file_entry (file structure) needs to be initialized according to the needs of the lock record.

In step S303, all lock records are traversed and the records that have been locked are restored; all lock records are traversed and records with a locked status are restored, that is, the corresponding files are locked according to the content in the lock record.

In step S304, exit the silent state after the recovery is completed.

Traverse all lock records and restore the records with locked status, that is, lock the corresponding files according to the contents in the lock record. Figure 4 is a flow chart of a method for sharing a network file system in Embodiment 1 of the present invention.

In step S401, if the current node fails, the network file system shared resources of the current node are switched to the backup node;

After a node failure, the file system and NFS shared resources are switched to other nodes, such as node2. The file systems mentioned in the present invention are all single-node rather than distributed file systems, that is, a file system can only be mounted on one node at a time. The cluster on Node2 notifies the NFS-server process on this node that a node switch has occurred.

In step S402, it is determined whether the file needs to be restored to the locked state after switching to the standby node. If the locked state needs to be restored, the network file system is put into a silent state, and then the file lock record corresponding to the current node is read from the database. , and perform restoration according to the file structure that needs to be restored, and exit the silent state after the restoration is completed.

According to the configuration of NFS-server, determine whether the lock state needs to be restored;

If the lock state needs to be restored, the NFS-server process enters a partially silent state, that is, all requests received at this time need to be determined which file system they correspond to. If they correspond to the file system that has just been switched, the request will be discarded directly. ;

The NFS-server process reads the lock data corresponding to the failed node from the ctdb database, restores the file structure (file_entry) as needed, and restores the lock status based on the lock record;

After the Lock state recovery is completed, the NFS-server process exits the partially silent state.

Aiming at the defect of NFS service in locking files in the storage system, the present invention designs an improved method for NFS to lock files, so that the NFS process can realize fault recovery and sharing for all file lock requests, and improves the efficiency of NFS. stability and reliability.

Embodiments of the present application also provide a storage medium, that is, a computer storage medium, specifically a computer-readable storage medium, such as a memory that stores a computer program. The computer program can be executed by a processor to complete the steps of the foregoing method. The computer-readable storage medium may be memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM.

Those of ordinary skill in the art can understand that all or part of the steps to implement the above method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, It includes the steps of the above method embodiment; and the aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, magnetic disks or optical disks. Alternatively, if the integrated units mentioned above in this application are implemented in the form of software function modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application can be embodied in the form of software products in essence or those that contribute to the existing technology. The computer software products are stored in a storage medium and include a number of instructions to An electronic device (which may be a personal computer, a server, a network device, etc.) is caused to execute all or part of the methods described in various embodiments of this application. The aforementioned storage media include: mobile storage devices, ROM, RAM, magnetic disks or optical disks and other media that can store program codes.

For descriptions of the relevant parts of the device and storage medium for locking files in a network file system provided by the embodiment of the present application, please refer to the details of the corresponding parts of the method of locking files by a network file system provided by Embodiment 1 of the present application. Description will not be repeated here.

It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that these entities or operations are mutually exclusive. any such actual relationship or sequence exists between them. Furthermore, the terms "comprises," "comprises," or any other variation thereof are intended to cover a non-exclusive inclusion such that elements inherent in a process, method, article, or apparatus include a list of elements. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article, or apparatus that includes the stated element. In addition, the parts of the above technical solutions provided by the embodiments of the present application that are consistent with the implementation principles of the corresponding technical solutions in the prior art have not been described in detail to avoid excessive redundancy.

Although the specific embodiments of the present invention have been described above with reference to the accompanying drawings, this does not limit the scope of the present invention. For those skilled in the art, other modifications or variations may be made based on the above description. An exhaustive list of all implementations is neither necessary nor possible. On the basis of the technical solution of the present invention, various modifications or transformations that can be made by those skilled in the art without creative efforts are still within the protection scope of the present invention.

Claims (8)

1. A method for locking files in a network file system, which is characterized by including the following steps: Receive file locking requests and generate locking records; If the original file lock list is queried according to the lock record and has neither the same or the same range of lock records nor conflicting locks; then the lock record is added to the original file lock list to obtain the first file lock list, And write the first file lock list into the database; then execute file locking; The method also includes: restarting the network file system process after the file is locked, first making the network file system enter a silent state; in the silent state, if the file needs to be restored to the locked state, reading the first file from the database Lock list, initialize the file structure according to the lock record; traverse all the lock records, restore the records that have been locked; exit the silent state after the restoration is completed; If the current node fails, switch the network file system shared resources of the current node to the backup node; after judging the switch to the backup node, judge whether the file needs to be restored to the locked state, and if it needs to be restored to the locked state, make the network file system enter Quiet state, then read the file lock record corresponding to the current node from the database, and perform recovery according to the file structure that needs to be restored, and exit the silent state after the recovery is completed. 2. A method for locking files in a network file system according to claim 1, characterized in that the method further includes unlocking the files; the process of unlocking the files is: Receive file unlocking request; generate unlocking record; Delete the unlocking record from the first file lock list to obtain a second file lock list, perform file unlocking, and synchronize the second file lock list to the database. 3. A method for locking files in a network file system according to claim 2, characterized in that the method further includes: Traverse the second file lock list; determine whether the file still needs to be locked; if the second file lock list is not empty, obtain a lock record from the head of the second file lock list and perform file locking. 4. A method for locking files in a network file system according to claim 1, wherein the method of querying the original file lock list for locking records that neither have the same nor the same range includes: According to the lock record, query whether the original file lock list has the same lock record. If it has the same lock record, it will return directly without locking; According to the file lock range in the lock record, query whether there is a file lock covering the range in the original file lock list, and if so, return directly without locking. 5. A method for locking files in a network file system according to claim 4, characterized in that the conflict lock includes: There is an exclusive lock with the same file lock range as in the lock record; There is a shared lock with the same file lock range as in the lock record, and the current lock needs to be an exclusive lock. 6. A system for locking files in a network file system, characterized in that the system includes a receiving module and a locking module; The receiving module is used to receive file locking requests and generate locking records; The locking module is used to add the locking record to the original file lock list if the original file lock list contains neither the same or the same range of lock records nor conflicting locks according to the lock record query. Obtain the first file lock list and write the first file lock list into the database; then execute file locking; After the file is locked, the network file system process is restarted, and the network file system is first put into a silent state; in the silent state, if the file needs to be restored to the locked state, the first file lock list is read from the database, and the file is locked according to the lock state. Record the initialization file structure; traverse all locked records and restore the previously locked records; exit the silent state after the restoration is completed; If the current node fails, switch the network file system shared resources of the current node to the backup node; after judging the switch to the backup node, judge whether the file needs to be restored to the locked state, and if it needs to be restored to the locked state, make the network file system enter Quiet state, then read the file lock record corresponding to the current node from the database, and perform recovery according to the file structure that needs to be restored, and exit the silent state after the recovery is completed. 7. A device for locking files in a network file system, which is characterized by including: Memory, used to store computer programs; A processor, configured to implement the method steps of any one of claims 1 to 5 when executing the computer program. 8. A readable storage medium, characterized in that a computer program is stored on the readable storage medium, and when the computer program is executed by a processor, the method steps of any one of claims 1 to 5 are implemented.