TWI537750B - Method for supporting file management for physical file systems and file server using such method - Google Patents

Description

Method for supporting file management of physical file system and file server applying the method

The present invention relates to a method for supporting file management of a plurality of physical file systems and a file server to which the method is applied, and in particular, a file transaction notification for supporting multiple physical file systems Method of file change notification management (FCN) and quota management, and a file server to which the method is applied.

A computer system can contain different included resources for use by one or more host processors. Multiple resources within a computer system and multiple host processors can be interconnected by one or more communication connections. These resources may include, for example, a data storage device. These data storage devices can be coupled to one or more servers or host processors and provide storage services to each host processor. Multiple data storage devices from one or more different vendors can be connected and can provide a common data store for one or more host processors in a computer system.

A host processor can perform various data processing tasks and operations to use the data storage device. For example, the host processor can perform basic system I/O operations to connect data requests such as data read and write operations.

The host processor system can use a data storage device to store and retrieve data, and the data storage device includes a plurality of host interface units and disks. Machine and disk interface unit. The host system accesses data to the data storage device via a plurality of channels therebetween, and the data storage device also provides the data to the host system via the channels. The host system does not directly address the disk of the data storage device, but accesses those that display multiple logical disk units to the host system. These logical disk units may or may not correspond to the actual disk drive. The architecture that allows multiple host systems to access a single data storage device allows multiple host systems to share material within the data storage device. In order to facilitate sharing of data within the data storage device, additional software may be used on these data storage devices.

The host system can receive requests from the client and block service requests according to various protocols and their different versions of the agreement (eg, multiple file access protocols). In a file access protocol, multiple clients make multiple requests to access a file system. For example, a client can make a request to read and write data to one or more files of the file system. Instead of directly accessing the underlying storage, the clients may interact with one or more hosts acting as file servers and providing file system services to perform client requests based on a particular file access protocol.

The file system can enforce one or more types of quotas to limit resource limits. For example, a file system can execute a data storage quota for each user, whereby a quota can be specified as a limit or an upper limit as a data storage capacity that a particular user can consume. In a similar manner, a file system can enforce quotas for other types of different levels. For example, a file system can enforce quota limits for a group of users, one or more directories, and similar segments, which can vary with a particular file system.

At present, the operating system of the file server is mostly a Linux or Unix operating system. The commonly used file system includes the Ext3 file system, the Ext4 file system, the XFS file system, the BTRFS file system, etc., and these file systems are referred to herein as physical file systems. (physical file system), to distinguish from the virtual file system. The following will be for the virtual file system. The function is described in detail.

Currently, under Linux or Unix operating systems, D_NOFITY and I_NOTIFY are used to monitor file changes. However, both D_NOFITY and I_NOTIFY have a limit on the number of modules. In addition, the current monitoring behavior restrictions for file changes are difficult to apply to data storage with a storage capacity of 500TB or PB.

In addition, user quotas and group quotas have not been successfully implemented in the BTRFS file system. Moreover, subdirectory quotas have not been successfully implemented in the Ext3 file system and the Ext4 file system.

Therefore, the technical problem to be solved by the present invention is to provide a method for supporting file management of multiple physical file systems and a file server using the same, and in particular, the method of the present invention supports multiple physical file systems. A method of file change notification management and quota management, and a file server to which the method is applied.

A method of a preferred embodiment of the present invention is performed by at least one processor. The method of the present invention is used to support file management of a plurality of physical file systems of an operating system of at least one processor. The method of the present invention first resides in the virtual file system resident in the kernel space of the operating system. The virtual file system is coupled to a plurality of physical file systems, and performs the following steps: when one of the plurality of physical file systems is opened, checking whether the first file operation on the file is a creation or deletion operation ( Delete), write operation or renaming operation; if the result of the above check is affirmative, file change notification event is generated according to the first file operation and the full path of the file (file change notification event) Information), and the temporary file transaction notification event information is in the user space of the operating system; and in the user layer, The temporary file transaction notification event information is checked asynchronously, and if so, the file change notification database is updated according to the file transaction notification event information.

Further, in the method of the present invention, the virtual file system checks whether the first file operation is an operation or a write operation, and if so, performs the following steps: obtaining a path regarding the file; and based on the path regarding the file And determining whether the sub-directory quota of the file matches the sub-directory quota exceed table stored in the virtual file system, and if so, replying to the first error message.

Further, in the method of the present invention, the virtual file system checks whether the first file operation is an operation or a write operation, and if so, performs the following steps: obtaining a node about the file, about the file a user ID and a group ID for the file; and determining the file based on the node about the file, the user identification code for the file, and the group identification code for the file User ID quota or group ID quota for the file matches the user/group ID quota excess table stored in the virtual file system (user/group ID quota exceed Table), if yes, reply to the second error message.

Further, in the method of the present invention, the virtual file system performs the following steps: when the file is closed, checking whether the second file operation on the file is an operation establishment operation, a deletion operation, or a write operation; Affirmatively, the quota event information is generated according to the node, the path, the user identification code, the group identification code, and the file size of the file, and the quota event information is temporarily stored in the user of the operating system. In the user layer, in the user layer, check whether the temporary quota event information exists asynchronously, and if so, store the temporary quota event information and the user/group ID code management database (user/group ID) Quota Management database) and sub-directory/sub volume quota management database for comparison; and selectively updating subdirectory quota excess table and user/group ID quota according to the above comparison result Excess table.

A file server according to a preferred embodiment of the present invention includes a file transaction notification database and at least one processor. At least one processor is configured to execute the operating system. The operating system has a core layer and a user layer, and includes a plurality of physical file systems resident at the core layer, a file change notification event buffer resident at the user layer, and a virtual file system resident at the core layer. And a file change notification monitor resident at the user level. The virtual file system is coupled to a plurality of physical file systems and file transaction notification event registers. The virtual file system includes a first monitoring module. When the file is opened for one of the plurality of physical file systems, the first monitoring module is configured to check whether the first file operation on the file is an operation, a delete operation, a write operation, or a rename operation, and if so, The first monitoring module generates the file transaction notification event information according to the first file operation and the path of the file, and transmits the file transaction notification event information to the file transaction notification event register. The file transaction notification monitor is coupled to the file transaction notification database and the file transaction notification event register. The file transaction notification monitor is configured to check whether the file transaction notification event information is temporarily stored in the file transaction notification event register, and if so, the file transaction notification monitor updates the file transaction notification database according to the file transaction notification event information.

Further, in the file server of the present invention, the virtual file system includes a subdirectory quota excess table. The first monitoring module checks whether the first file operation is an operation or a write operation, and if so, obtains a path about the file, and based on the path regarding the file, determines whether the subdirectory quota for the file matches The subdirectory quota excess table in the virtual file system, if yes, reply to the first error message.

Further, in the file server of the present invention, the virtual file system includes a user/group identification code quota excess table. The first monitoring module checks whether the first file operation is an operation or a write operation, and if so, obtains a node about the file, a user identification code for the file, and a group identification code for the file, and Determining whether the user identification code quota for the file or the group identification code quota for the file matches is stored in the virtual file system based on the node about the file, the user identification code for the file, and the group identification code for the file. The user/group ID quota excess table, if yes, reply to the second error message.

Further, the file server of the present invention further includes a user/group identification code quota management database and a subdirectory/subvolume quota management database. The operating system also includes a quota event buffer resident at the user level and a quota monitor resident at the user layer. The quota monitor is coupled to the user/group ID quota management repository, the subdirectory/subvolume quota management repository, and the quota event register. The virtual file system also includes a second monitoring module. When the file is closed, the second monitoring module is configured to check whether the second file operation on the file is an operation, a delete operation or a write operation, and if so, the second monitoring module is based on the file. The node, path, user ID, group ID, and file size generate quota event information and transmit quota event information to the quota event register. The quota monitor is used to check whether the quota event information is temporarily stored in the quota event register, and if so, the quota monitor will temporarily store the quota event information and the user/group ID code management database and the subdirectory/ The subvolume quota management database is compared, and based on the comparison result, the subdirectory quota excess table and the user/group ID quota excess table are selectively updated.

In one embodiment, the plurality of physical file systems may include an Ext3 file system, an Ext4 file system, an XFS file system, a BTRFS file system, and the like.

Method and file system according to the present invention compared to prior art The system can support multiple physical file systems to do file transaction notification management and quota management. Moreover, the file transaction notification management and the quota management are processed in an asynchronous state to reduce the reaction time between the original I/Os due to the addition of function modules such as the monitoring module.

The advantages and spirit of the present invention will be further understood from the following detailed description of the invention.

1‧‧‧Data Storage System

10a~10c‧‧‧File Server

12a~12c‧‧‧User terminal device

14‧‧‧Data storage device

140a~140n‧‧‧Storage components

16‧‧‧Network

100‧‧‧ operating system

101‧‧‧File Change Notification Database

102‧‧‧ core layer

103‧‧‧User layer

104a~104d‧‧‧Entity file system

105‧‧‧File Change Notification Event Register

106‧‧‧Virtual File System

107‧‧‧File Change Notification Monitor

108‧‧‧First monitor module

109‧‧‧Subdirectory quota excess

110‧‧‧User/Group ID Code Excess Table

111‧‧‧User/Group ID Code Quota Management Database

112‧‧‧Subdirectory/Subvolume Quota Management Database

113‧‧‧ Quota event register

114‧‧‧Quota monitor

115‧‧‧Second monitor module

3‧‧‧Method of the invention

S30~S38‧‧‧ Process steps

S40~S46‧‧‧ Process steps

S50~S56‧‧‧ Process steps

S60~S66‧‧‧ Process steps

1 is a block diagram showing the structure of a data storage system using the file server of the present invention.

2 is a schematic diagram of a software layer architecture of a file server in accordance with a preferred embodiment of the present invention.

3 is a flow chart of a method in accordance with a preferred embodiment of the present invention.

4 is a flow chart of further steps of the method of the present invention.

Figure 5 is a flow chart of further steps of the method of the present invention.

Figure 6 is a flow chart of further steps of the method of the present invention.

Referring to FIG. 1, the architecture of the data storage system 1 is schematically illustrated in FIG. The data storage system 1 employs file servers (10a-10c) in accordance with a preferred embodiment of the present invention. The data storage system 1 also includes user terminal devices (12a-12c), data storage devices 14, and a network 16. The user terminal devices (12a to 12c) may be various types of data processing devices, such as a desktop computer, a notebook computer, a mobile phone, a tablet computer, and the like.

Each of the file servers (10a-10c), the user terminal devices (12a-12c), and the data storage device 14 can communicate with each other via the network 16. In one embodiment, the network 16 may be an internet, an extranet, an intranet, or a local area. Network), wide area network, Ethernet, cable TV network, radio telecommunication network, public switched telephone network, 3G network, HSPA network, Wi-Fi network, WiMAX network, LTE network, or other currently commercial networks.

Although the file servers (10a to 10c) and the user terminal devices (12a to 12c) display a specific number in FIG. 1, the number of the file servers (10a to 10c) and the user terminal devices (12a to 12c) may be One or more, and connected and communicated with each other using the connection techniques mentioned in this patent specification. Each file server (10a~10c) can process the appropriate computer system for the client request it receives. As described in more detail below, the plurality of physical file systems and related services provided by the file servers (10a-10c) may include a joint distributed file system architecture in accordance with the techniques disclosed herein. The file server (10a~10c) can collectively serve as a front end for the overall distributed file system architecture, and the overall distributed file system architecture includes a plurality of physical file systems, whereby the file servers (10a-10c) Parallelism and scalability that can be understood by those of ordinary skill in the art to which the present invention pertains are provided.

The data storage device 14 can include one or more data storage elements (140a-140n). In one embodiment, each of the storage elements (140a-140n) may be a tape drive, a disk drive, a memory recording device, an optical storage recording device, or other equivalent storage device. The data storage device 14 can represent a single data storage array or array of data storage arrays that can be configured to form a suitable configuration, such as a storage area network (SAN). The file servers (10a-10c) can communicate with the data storage device 14 to interface with operations on data (e.g., files) stored in the data storage elements (140a-140n). Further, the user terminal devices (12a-12c) can communicate with the file server (10a~10c) to connect to the service client request, thereby accessing the data stored in the data storage device 14.

For example, the user terminal device 12a can issue a request to write one The files are transmitted from the user terminal device 12a to one of the file servers (10a to 10c) (for example, the file server 10a). In response to the request, the file server 10a can communicate with the data storage device 14 to perform processing to perform data processing on one or more of the data storage elements (140a-140n) to write the requested data to the archive. The file server (10a~10c) can provide data and access control information to the data storage device 14 via a plurality of channels, and the data storage device 14 can provide data to the file server (10a-10c) via the channels. The file server (10a~10c) may not address multiple physical storage elements of the data storage device 14, but address multiple logical elements or logical books via multiple channels, and use files via other software layers. Based on access technology.

Referring to FIG. 2, a software layer architecture of a file server (10a-10c) according to a preferred embodiment of the present invention is schematically illustrated in FIG.

As shown in FIG. 2, a file server (10a~10c) according to a preferred embodiment of the present invention includes a file transaction notification database 101 and at least one processor (not shown in FIG. 2).

At least one processor is used to execute the operating system 100. The operating system 100 has a core layer 102 and a user layer 103, and includes a plurality of physical file systems (104a-104d) resident in the core layer 102, a file transaction notification event register 105 resident in the user layer 103, and resident in the core layer. The virtual file system 106 of 102 and the file transaction notification monitor 107 resident in the user layer 103.

The virtual file system 106 is coupled to a plurality of physical file systems (104a-104d) and a file transaction notification event register 105. The virtual file system 106 includes a first monitoring module 108. When the file is opened for one of the plurality of physical file systems (104a-104d), the first monitoring module 108 is configured to check whether the first file operation of the file is an operation, a deletion operation, a write operation, or a rename. Operation, and if so, the first monitoring module 108 generates a file transaction notification event based on the first file operation and the path to the file Information, and the file transaction notification event information is transmitted to the file transaction notification event register 105. In a specific embodiment, the first monitoring module 108 can be a hooker monitoring software.

The file transaction notification monitor 107 is coupled to the file transaction The knowledge database 101 and the file transaction notification event register 105 are known. The file transaction notification monitor 107 is configured to check whether the file transaction notification event information is temporarily stored in the file transaction notification event register 105, and if so, the file transaction notification monitor 107 updates the file transaction notification according to the file transaction notification event information. Database 101. Thereby, the software layer architecture of the file server (10a~10c) of the present invention can support the physical file system (104a~104d) to perform file transaction notification management.

In one embodiment, the operating system 100 can be a Linux operating system or a Unix operating system.

In one embodiment, the plurality of physical file systems (104a-104d) may include an Ext3 file system, an Ext4 file system, an XFS file system, a BTRFS file system, and the like.

Further, also shown in FIG. 2, in the file server (104a-104d) of the present invention, the virtual file system 106 includes a subdirectory quota excess table 109. The first monitoring module 108 also checks whether the first file operation is an operation or a write operation, and if so, obtains a path about the file, and based on the path regarding the file, determines whether the subdirectory quota for the file matches. The subdirectory quota excess table 109 stored in the virtual file system 106, if yes, replies to the first error message. Thereby, the software layer architecture of the file server (10a~10c) of the present invention can support the entity file system (104a~104d) to perform quota management.

Further, also shown in FIG. 2, in the file server (104a-104d) of the present invention, the virtual file system 106 includes a user/group identification code quota excess table 110. The first monitoring module 108 and checking whether the first file operation is Establishing an operation or a write operation, and if so, obtaining a node about the file, a user identification code for the file, and a group identification code for the file, and based on the node regarding the file, a user identification code for the file And a group identification code for the file, determining whether the user identification code quota for the file or the group identification code quota for the file matches the user/group identification code quota excess table 110 stored in the virtual file system 106, If yes, reply to the second error message. Thereby, the software layer architecture of the file server (10a~10c) of the present invention can support the entity file system (104a~104d) to perform quota management.

Further, also shown in FIG. 2, the file server (104a-104d) of the present invention further includes a user/group identification code quota management database 111 and a subdirectory/sub-volume quota management database 112. The operating system 100 also includes a quota event register 113 resident in the user layer 103 and a quota monitor 114 resident in the user layer 103. The quota monitor 114 is coupled to the user/group identification code quota management repository 111, the subdirectory/subvolume quota management repository 112, and the quota event register 113. The virtual file system 106 also includes a second monitoring module 115. When the file is closed, the second monitoring module 115 is configured to check whether the second file operation regarding the file is an operation establishing operation, a deletion operation or a writing operation, and if so, the second monitoring module 115 according to the relevant The node, path, user identification code, group identification code, and file size of the file generate quota event information, and the quota event information is transmitted to the quota event register 113. The quota monitor 114 is configured to check whether the quota event information is temporarily stored in the quota event register 113, and if so, the quota monitor 114 stores the temporarily stored quota event information and the user/group identification code quota management database 111. And the subdirectory/subvolume quota management database 112 is compared, and based on the comparison result, the subdirectory quota excess table 109 and the user/group identification code quota excess table 110 are selectively updated. Thereby, the software layer architecture of the file server (10a~10c) of the present invention can support the entity file system (104a~104d) to perform quota management. In a specific embodiment, the second monitoring module 115 can be a hooker monitoring software.

Please refer to FIG. 3, which is a preferred embodiment of the present invention. The process steps of Method 3 are depicted in Figure 3. The method 3 of the present invention performs the functions of the software layer architecture shown in FIG. 2 by at least one processor. The method 3 of the present invention is used to support file management of a plurality of physical file systems (104a-104d) of the operating system 100 of at least one processor.

As shown in FIG. 3, the method 3 of the present invention first performs step S30 to resident the virtual file system 106 in the core layer 102 of the operating system 100.

The virtual file system 106 is coupled to a plurality of physical file systems (104a-104d). Next, the method 3 of the present invention performs step S32. When a file is opened for one of the plurality of physical file systems (104a-104d), it is checked whether the first file operation regarding the file is an operation of establishing, deleting, or writing. Or rename the operation.

If the result of the check in step S32 is affirmative, the method 3 of the present invention performs step S34, generating file transaction notification event information according to the first file operation and the path about the file, and temporarily storing the file transaction notification event information on the operating system 100. Within the user layer 103. After step S34, the method 3 of the present invention performs step S36 to asynchronously check whether the temporary file transaction notification event information exists in the user layer 103. If the result of the check in step S36 is affirmative, step S38 is executed to update the file transaction notification database 101 based on the file transaction notification event information.

Further, referring to FIG. 4, method 3 of the present invention and performing step S40, virtual file system 106 and checking whether the first file operation is an operation or a write operation. If the result of the check in step S40 is affirmative, the method 3 of the present invention executes step S42 to obtain a path regarding the file. After step S42, the method 3 of the present invention performs step S44 to determine, based on the path of the file, whether the subdirectory quota for the file matches the subdirectory quota excess table 109 stored in the virtual file system 106. If the result of the determination in step S44 is affirmative, the method 3 of the present invention performs step S46 to reply to the first error message.

Further, referring to FIG. 5, method 3 of the present invention and performing step S50, virtual file system 106 and checking whether the first file operation is an operation or a write operation. If the result of the check in step S50 is affirmative, the method 3 of the present invention executes step S52 to obtain a node about the file, a user identification code for the file, and a group identification code for the file. After step S52, the method 3 of the present invention performs step S54, determining a user identification code quota for the file based on the node about the file, the user identification code for the file, and the group identification code for the file. Whether the group ID code quota of the file matches the user/group ID quota excess table 110 stored in the virtual file system 106. If the step S54 is YES, the method 3 of the present invention performs the determination in the step S56 as affirmative, and replies to the second error message.

Further, referring to FIG. 6, the method 3 of the present invention and performing step S60, when the file is closed, it is checked whether the second file operation regarding the file is an operation establishment operation, a deletion operation, or a write operation. If the result of the check in step S60 is affirmative, the method 3 of the present invention performs step S62, generating quota event information according to the node, the path, the user identification code, the group identification code, and the file size of the file, and temporarily storing the quota. The event information is within the user layer 103 of the operating system 100. After step S62, the method 3 of the present invention performs step S64 to check whether the temporarily stored quota event information exists asynchronously in the user layer 103. If the result of the check in step S64 is affirmative, the method 3 of the present invention executes step S66 to store the temporary quota event information and the user/group identification code quota management database 111 and the subdirectory/subvolume quota management database 112. comparing. After step S66, the method 3 of the present invention performs step S68 to selectively update the subdirectory quota excess table 109 and the user/group identification code quota excess table 110 according to the comparison result.

It should be emphasized that the method and file server according to the present invention can support multiple physical file systems (104a-104d) to perform file transaction notification management and quota management as compared with the prior art. Moreover, regarding the file transaction notification management and quota management, the asynchronous state processing is adopted to reduce the new monitoring mode. Groups and other functional modules increase the reaction time between the original I/O.

The features and spirit of the present invention are intended to be more apparent from the detailed description of the preferred embodiments. On the contrary, the intention is to cover various modifications and equivalents that are within the scope of the invention as claimed. Therefore, the scope of the patent application of the present invention should be construed broadly in the light of the above description, so that it covers all possible changes and arrangements.

100‧‧‧ operating system

101‧‧‧File Change Notification Database

102‧‧‧ core layer

103‧‧‧User layer

104a~104d‧‧‧Entity file system

105‧‧‧File Change Notification Event Register

106‧‧‧Virtual File System

107‧‧‧File Change Notification Monitor

108‧‧‧First monitor module

109‧‧‧Subdirectory quota excess

110‧‧‧User/Group ID Code Excess Table

111‧‧‧User/Group ID Code Quota Management Database

112‧‧‧Subdirectory/Subvolume Quota Management Database

113‧‧‧ Quota event register

114‧‧‧Quota monitor

115‧‧‧Second monitor module

Claims (10)

A method performed by at least one processor to support file management of a plurality of physical file systems of one of the at least one processor operating system, the method comprising the steps of: (a) resident a virtual file system in the job Within one core layer of the system, the virtual file system is coupled to the plurality of physical file systems and performs the following steps: (b) when one of the plurality of physical file systems is opened, checking one of the files Whether the first file operation is selected from one of a group consisting of a setup operation, a delete operation, a write operation, and a rename operation; (c) if the result of the step (b) is affirmative, The first file operation and a path for the file to generate a file transaction notification event information, and temporarily storing the file transaction notification event information in a user layer of the operating system; and (d) within the user layer, Simultaneously checking whether the temporarily stored file transaction notification event information exists, and if so, updating a file transaction notification data according to the file transaction notification event information . The method of claim 1, wherein the plurality of physical file systems comprise one selected from the group consisting of an Ext3 file system, an Ext4 file system, an XFS file system, and a BTRFS file system. The method of claim 2, wherein the virtual file system further performs the following steps: (e) checking whether the first file operation is the setup operation or the write operation, and if so, performing the following steps: (f) obtaining the path with respect to the file; and (g) based on the path with respect to the file And determining whether a subdirectory quota of the file matches a subdirectory quota excess table stored in the virtual file system, and if so, replying with a first error message. The method of claim 2, wherein the virtual file system further performs the steps of: (h) checking whether the first file operation is the setup operation or the write operation, and if so, performing the following steps: (i) Obtaining a node about the file, a user identification code for the file, and a group identification code for the file; and (j) based on the node about the file, the user identification code for the file, and about the The group identification code of the file, determining whether a user identification code quota of the file or a group identification code quota of the file matches a user/group identification code quota excess table stored in the virtual file system, If yes, reply with a second error message. The method of claim 2, wherein the virtual file system further performs the following steps: (k) when the file is closed, checking whether a second file operation regarding one of the files is selected from the setup operation, the delete operation And one of the groups consisting of the writing operation; (1) if the result of the step (k) is affirmative, according to the node about the file, the path, the user identification code, the group identification code And a file size Generating a quota event information, and temporarily storing the quota event information in the user layer of the operating system; (m) in the user layer, asynchronously checking whether the temporarily stored quota event information exists, and if present And comparing the temporarily stored quota event information with a user/group identification code quota management database and a subdirectory/subvolume quota management database; and (n) selecting according to the comparison result of step (m) This subdirectory quota excess table and the user/group ID quota excess table are updated sexually. A file server includes: a file transaction notification database; and at least one processor for executing an operating system, the operating system having a core layer and a user layer and comprising: a plurality of physical file systems, resident The core layer; a file transaction notification event register is resident at the user layer; a virtual file system resident in the core layer and coupled to the plurality of entity file systems and the file transaction notification event register The virtual file system includes a first monitoring module. When the file is opened for one of the plurality of physical file systems, the first monitoring module is configured to check whether the first file operation of the file is Selecting one of a group consisting of a setup operation, a deletion operation, a write operation, and a rename operation, and if so, the first monitoring module operates according to the first file and about the file a path generates a file transaction notification event information, and transmits the file transaction notification event information to the file transaction notification event register; a file transaction notification monitor resident in the user layer and coupled to the file transaction notification database and the file transaction notification event register, the file transaction notification monitor is configured to check whether the file transaction notification event information is temporarily stored The file transaction notification event is stored in the event register, and if so, the file transaction notification monitor updates the file transaction notification database based on the file transaction notification event information. The file server of claim 6, wherein the plurality of physical file systems comprise one selected from the group consisting of an Ext3 file system, an Ext4 file system, an XFS file system, and a BTRFS file system. The file server of claim 7, wherein the virtual file system includes a subdirectory quota excess table, and the first monitoring module checks whether the first file operation is the setup operation or the write operation, and If so, obtaining the path for the file, and based on the path for the file, determining whether a subdirectory quota for the file matches a subdirectory quota excess table stored in the virtual file system, and if so, replying A first error message. The file server of claim 7, wherein the virtual file system includes a user/group identification code quota excess table, and the first monitoring module checks whether the first file operation is the establishing operation or the writing Entering an operation, and if so, obtaining a node for the file, a user identification code for the file, and a group identification code for the file, and based on the node regarding the file, the user identification for the file a code and a group identification code for the file, determining whether a user identification code quota for the file or a group identification code quota for the file matches the virtual code A user/group ID quota excess table in the proposed file system, and if so, a second error message is replied. The file server of claim 7, further comprising: a user/group identification code quota management database; and a subdirectory/subvolume quota management database; wherein the operating system further comprises: a quota event temporary storage Residing at the user layer; and a quota monitor resident at the user layer and coupled to the user/group ID code management database, the subdirectory/subvolume quota management database, and the quota event a temporary storage device, wherein the virtual file system further includes a second monitoring module, and when the file is closed, the second monitoring module is configured to check whether the second file operation of the file is selected from the Establishing, deleting, and one of the groups of the write operations, and if so, the second monitoring module according to the node, the path, the user identification code, the group The group identification code and a file size generate a quota event information, and transmit the quota event information to the quota event register; wherein the quota monitor is used to check the quota event Whether it is temporarily stored in the quota event register, and if so, the quota monitor stores the temporary quota event information with the user/group identification code quota management database and the subdirectory/subvolume quota management The database is compared, and based on the comparison result, the subdirectory quota excess table and the user/group ID quota excess table are selectively updated.