CN111737109A - A kind of cluster file system testing method and device - Google Patents

Abstract

One or more embodiments of this specification provide a method and device for testing a cluster file system, including: reading a configuration file; the configuration file includes global configuration information and configuration information of an item to be tested; A test item set including at least one to-be-tested item; according to the configuration information of the to-be-tested item, select a target test item from the test item set; test the target test item to obtain a test result. This manual can realize the test of the cluster file system.

Description

A kind of cluster file system testing method and device

technical field

One or more embodiments of this specification relate to the field of computer technologies, and in particular, to a method and apparatus for testing a cluster file system.

Background technique

A cluster file system refers to a file system that runs on multiple computers and communicates with each other through network, RDMA, etc., so as to integrate and virtualize all storage space resources in the cluster and provide file access services to the outside world. The cluster file system can expand the storage function. In different application scenarios, the cluster file system needs to have compatibility and portability to adapt to different system environments and meet the corresponding storage expansion functions.

At present, the existing file system compatibility testing tools can test the system kernel file system, such as the POSIX file system testing tool, but there is no method for testing the cluster file system.

SUMMARY OF THE INVENTION

In view of this, the purpose of one or more embodiments of this specification is to provide a method and apparatus for testing a cluster file system, which can test a cluster file system.

Based on the above purpose, one or more embodiments of this specification provide a method for testing a cluster file system, including:

Read a configuration file; the configuration file includes global configuration information and configuration information of the item to be tested;

Create a test item set including at least one item to be tested according to the global configuration information;

According to the configuration information of the item to be tested, select a target test item from the set of test items;

Test the target test item to obtain a test result.

Optionally, the global configuration information includes initialization configuration information for testing the cluster file system; the configuration information of the item to be tested includes system call operation content and operation ratio of the item to be tested.

Optionally, creating a test item set including at least one item to be tested according to the global configuration information includes: adding the system call operation content of the item to be tested to the idle operation list according to the global configuration information.

Optionally, according to the configuration information of the item to be tested, select a target test item from the set of test items, including:

According to the operation ratio of the item to be tested, randomly select the target test item from the idle operation list;

According to the selected target test item, an operation group is created; the operation group includes at least one operation item of the target test item;

The operation group is added to the test waiting queue.

Optionally, the operation item includes the operation object, the operation object type, the operation premise, and whether the operation object already exists; randomly determine whether the operation premise is open or close, if the operation object is a file or a directory, when the When the operation premise is open, the operation item does not need to execute the system call operation content of opening a file or a directory, and when the operation premise is closed, the operation item needs to execute the system call content of opening a file or opening a directory.

Optionally, after reading the configuration file, the method further includes: verifying the configuration file, and if the configuration file verification passes, creating a test item set including at least one item to be tested according to the global configuration information;

Verifying the configuration file includes: judging whether the test directory for mounting the cluster file system and the verification directory for mounting the file system for verification are included; otherwise, the verification fails; Whether the sum of the operation proportions of the type operations is 100%, and if the sum of the operation proportions of at least one operation is not 100%, the verification fails; it is judged whether the accuracy of each operation proportion conforms to the configuration in the global configuration information. The precision of the operation scale, otherwise the verification fails.

Optionally, the configuration file is verified, and if the configuration file verification is passed, it also includes: clearing the test directory and the verification directory; creating a test item set including at least one item to be tested according to the global configuration information .

Optionally, test the target test item to obtain test results, including:

Take out the operation group from the test waiting queue;

determining each operation item in the operation group;

Analyze the operation item to determine the operation to be performed by the operation object;

Perform an operation on the operation object to obtain a test result.

Optionally, the method further includes: verifying the test result, including:

Based on the operation of the operation object of the operation item, perform the same operation on the same operation object of the file system used for verification, and obtain the operation result;

Compare test results with operational results;

If they are consistent, the verification is passed; otherwise, the inconsistent operation results and test results are output to the verification result log.

The embodiments of this specification also provide a cluster file system testing device, including:

a reading module for reading a configuration file; the configuration file includes global configuration information and configuration information of the item to be tested;

A creation module is used to create a test item set including at least one to-be-tested item according to the global configuration information;

a selection module for selecting a target test item from the test item set according to the configuration information of the item to be tested;

The test module is used to test the target test item to obtain the test result.

As can be seen from the above, the method and device for testing a cluster file system provided by one or more embodiments of the present specification, by reading the configuration file including the global configuration information and the configuration information of the item to be tested, create A test item set including at least one to-be-tested item, according to the configuration information of the to-be-tested item, select a target test item from the test item set, test the target test item, and obtain a test result. This manual can realize the test of the cluster file system.

Description of drawings

In order to more clearly illustrate one or more embodiments of the present specification or the technical solutions in the prior art, the following briefly introduces the accompanying drawings used in the description of the embodiments or the prior art. Obviously, in the following description The accompanying drawings are only one or more embodiments of the present specification, and for those of ordinary skill in the art, other drawings can also be obtained from these drawings without any creative effort.

1 is a schematic flowchart of a method according to one or more embodiments of this specification;

FIG. 2 is a block diagram of an apparatus structure according to one or more embodiments of this specification;

FIG. 3 is a structural block diagram of an electronic device according to one or more embodiments of the specification.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present disclosure clearer, the present disclosure will be further described in detail below with reference to the specific embodiments and the accompanying drawings.

It should be noted that, unless otherwise defined, the technical or scientific terms used in one or more embodiments of the present specification shall have the usual meanings understood by those with ordinary skill in the art to which this disclosure belongs. The terms "first," "second," and similar terms used in one or more embodiments of this specification do not denote any order, quantity, or importance, but are merely used to distinguish the various components. "Comprises" or "comprising" and similar words mean that the elements or things appearing before the word encompass the elements or things recited after the word and their equivalents, but do not exclude other elements or things. Words like "connected" or "connected" are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "Up", "Down", "Left", "Right", etc. are only used to represent the relative positional relationship, and when the absolute position of the described object changes, the relative positional relationship may also change accordingly.

As shown in FIG. 1, one or more embodiments of this specification provide a method for testing a cluster file system, including:

S101: read a configuration file; the configuration file includes global configuration information and configuration information of the item to be tested;

In this embodiment, in order to implement the cluster file system test, a configurable configuration file is created, and the configuration file includes global configuration information and various configuration information of the item to be tested in the cluster file system.

In some embodiments, the global configuration information includes initial configuration information for testing the cluster file system. The configuration information of the item to be tested includes the system call operation content and operation ratio of the item to be tested; the item to be tested of the cluster file system includes one or more of files, targets, and soft links. The configuration information of the file in the configuration file includes the system call operation content and operation ratio that need to open the file, the system call operation content and operation ratio that does not need to open the file; the configuration information of the directory in the configuration file includes the system call operation content and operation ratio that need to open the directory. Operation ratio, the system call operation content and operation ratio of the directory do not need to be opened; the configuration information of the soft link in the configuration file includes the system call operation content and operation ratio of the soft link, etc.

S102: Create a test item set according to the global configuration information;

In this embodiment, creating a test item set including at least one item to be tested according to the global configuration information in the configuration file includes: adding the system call operation content of the item to be tested to the idle operation according to the global configuration information in the configuration file List; the idle operation list stores parameters such as the type (directory, file and soft link) and name of the item to be tested, the type of system call operation, the total number of operations, the file type, and the specific operation behavior corresponding to the type of system call operation. Parameters are set according to the relevant configuration information in the configuration file.

S103: Select a target test item from the created test item set according to the configuration information of the item to be tested;

In this embodiment, selecting a target test item from the created test item set according to the configuration information of the item to be tested includes: randomly selecting a target test item from the test item set according to the operation ratio corresponding to each item to be tested, and selecting The output target test items are added to the test waiting queue.

S104: Test the target test item to obtain a test result.

In this embodiment, after the target test item is selected, the target test item is tested, and a test result is obtained. In some manners, testing the target test item to obtain the test result includes: when it is determined that the test waiting queue is full, performing a test on each target test item in the test waiting queue, and obtaining the test result after the test is completed.

In this embodiment, in order to test the cluster file system, a configuration file for testing each item to be tested in the cluster file system is first established. During the test, the configuration file is read, and according to the global configuration information in the configuration file, Create a test item set, and then select the target test item from the created test item set according to the configuration information of the item to be tested, test the target test item, and obtain the test result of the item to be tested in the cluster file system after the test is completed. The test function of the system provides the basis for optimizing the cluster file system.

In this embodiment, after the configuration file is read in step S101, the method further includes: verifying the configuration file, and if the configuration file is verified successfully, performing step S102 to create a test item set according to the configuration file.

In some embodiments, referring to Table 1, the configuration file specifically includes a test directory (the mount directory of the cluster file system storage pool), the verification directory (the mount directory of the file system used to verify the test result of the cluster file system, For example, the disk or disk array mount directory of the kernel file system), global configuration information, file configuration information, directory configuration information, soft connection configuration information and other configuration items. Among them, the global configuration information includes file operation ratio, directory operation ratio, soft connection operation ratio, log level, precision of operation ratio, data block size written/read, maximum/minimum value of data block written/read, Maximum directory depth, the number of directories created by initialization, the number of files created by initialization, the number of soft links created by initialization, the total number of items to be tested, the mount point of the cluster file system, and the mount point of the file system used to verify the test results of the cluster file system Load point, log directory (used to save various logs generated during the test), number of worker threads, length of test waiting queue, number of items to be tested that need to open files, number of items to be tested that do not need to open files, and directories to be opened The number of items to be tested, the number of items to be tested that do not need to open the directory, the number of items to be tested with soft links, the proportion of operations to open directories, the proportion of operations to create new directories, the proportion of operations to open files, the proportion of operations to create new files, etc.

Among them, in the test process, the execution result of each step is recorded in the corresponding log file, and the corresponding log level is set for each log file. The log level determines the confidence level of the information output during the execution of the corresponding step, and the log level The larger the value, the more detailed the output, and the log files can be used to trace the execution process and improve the test efficiency.

As shown in Table 1, the configuration information of the file includes the system call operation content that needs to open the file and the operation proportion of each operation content, the system call operation content that does not need to open the file, and the operation proportion of each operation content. Among them, the system call operations that need to open files include write, read, fallocate, ftruncate, fsync, fsetxattr, fgetxattr, fremovexattr, flock, fchown, fchmod, futimes, fstat, etc.; the operation ratio of all system call operations that need to open files The sum should be 100% and each operation scale should be as accurate as the configured operation scale. System call operations that do not need to open files include rename, symlink, link, truncate, setxattr, getxattr, removexattr, access, chown, chmod, utimes, stat, unlink, statfs, etc.; The sum of the operation scales should be 100%, and each operation scale should be as accurate as the configured operation scale.

The configuration information of the directory includes the system call operation content that needs to open the directory and the operation proportion of each operation content, the system call operation content that does not need to open the directory, and the operation proportion of each operation content. Among them, the system call operation content that needs to open the directory includes fsync, fsetxattr, fgetxattr, fremovexattr, readdir, flock, fchown, fchmod, futimes, fstat, etc.; the sum of the operation ratio of all system call operation content that needs to open the directory should be 100% , the precision of each operation scale should reach the precision of the configured operation scale. The system call operation information that does not need to open the directory includes access, rename, symlink, setxattr, getxattr, removexattr, chown, chmod, utimes, rmdir, stat, statfs, etc.; the sum of the operation proportions of all the system call operation contents that do not need to open the directory Should be 100%, each operation scale should be as accurate as the configured operation scale.

The configuration information of the soft connection includes the operation content of the system call of the soft connection and the operation proportion of each operation content. The system call operation content of the soft connection includes readlink and unlink, and the sum of the operation proportions of the two operation content should be 100%. Each operating scale should be as accurate as the configured operating scale.

Table 1

As shown in Table 1, the file size generated during the test is determined by the two configuration items MAX_OP_SIZE and MINI_OP_SIZE, and the file size range that can be generated is [MINI_OP_SIZE, MAX_OP_SIZE+1024*1024], which can be used to estimate the required size of the test. File system (integrated file system or file system used for verification) size. The number of files, directories, and soft links created during initialization. The values of the three configuration items can be equal. Optionally, the value can be an order of magnitude smaller than the total number of items to be tested, which can ensure the test effect and make reasonable use of the system. resource. During the test, the size of the data block written each time needs to be consistent with the size of the data block read each time, and the size of the data block can be divisible by MAX_OP_SIZE or MINI_OP_SIZE.

In some embodiments, verifying the configuration file includes: judging whether the test directory and the verification directory are included, if not (the test directory and/or the verification directory are not specified, or the specified directory does not exist), then Verification fails; judges various types of operations (system call operations that require file opening, system call operations that do not require file opening, system call operations that require opening directories, system call operations that do not require opening operations, and system call operations that require soft connections ) is 100%, if there is at least one type of operation whose sum is not 100%, then the verification fails; judge whether the accuracy of each operation ratio conforms to the configured accuracy of the operation ratio, if If the precision of at least one operation scale does not meet the precision of the configured operation scale, the verification fails.

In some ways, during the specific test, the global configuration information in the configuration file and/or various configuration information of the item to be tested can be configured and modified according to the actual test content and test requirements, so as to achieve the test purpose. For example, in each test, configure and modify configuration items such as the number of files or directories in the configuration file to be tested, the operation ratio of the system call operation content, the size of the file read/write data block, and the accuracy of the operation ratio, so as to The effects of flexible configuration and dynamic testing are achieved, so that the cluster file system testing method of this embodiment has good compatibility and expansibility.

In this embodiment, after the configuration file is read in step S101, the method further includes: verifying the configuration file, and if the verification passes, clearing the test directory and verifying directory information according to the test directory and verification directory information in the configuration file The directory is used for testing; if the configuration file verification fails, output prompt operation information to the file verification log according to the failed verification items.

In this embodiment, in the step S103, according to the configuration information of the item to be tested, the target test item is selected from the test item set, including:

According to the operation ratio of each item to be tested in the configuration file, the target test item is randomly selected from the idle operation list;

Create an operation group according to the selected target test item;

Add the action group to the test waiting queue.

In some embodiments, the operation group includes at least one operation item of the target test item, and the operation item includes options such as operation object, operation object type, operation premise, and whether the operation object already exists. Among them, the operation premise can be set to open or close. In order to better simulate the actual test environment, the operation premise is randomly determined to be open or closed. For the operation object is a file or directory, when the operation premise is open, the operation item There is no need to perform the system call operation content of opening a file or opening a directory. When the operation premise is closed, the operation item needs to perform the system call content of opening a file or opening a directory. For example, if the operation object is a specific file, the operation object type is a file, the specific file already exists, and the operation premise is determined according to the random number to be opened, then during the test, the file does not need to perform the system call operation content of opening the file.

In this embodiment, according to the operation ratio of each item to be tested in the configuration file, a target test item is randomly selected from the idle operation list, an operation group is created according to the selected target test item, and the operation group is added to the test waiting queue. The target test item is randomly selected from all the items to be tested, which can simulate the actual operation of the cluster file system by the user.

In some embodiments, the operation group is added to the test waiting queue, and when it is determined that the test waiting queue is full, the operation group is taken out from the test waiting queue to perform operations on the operation objects in the operation group, which can make full use of system resources and reduce Test time and improve test efficiency.

In this embodiment, in the step S104, the target test item is tested to obtain a test result, including:

Remove the action group from the test waiting queue;

Determine each operation item in the operation group;

Analyze the operation item to determine the operation that the operation object needs to perform;

Perform an operation on the operation object to get the test result.

In this embodiment, during the test, the operation group is taken out from the test waiting queue, and each operation item in the operation group is analyzed to obtain options such as the operation object, the operation object type, the operation premise, and whether the operation object already exists, and the operation is determined. The operation that the object needs to perform, perform the operation on the operation object, and get the test result. Wherein, if the operation object is a file or a directory, according to whether the operation premise is open or closed, it is determined whether to execute the system call operation content of opening the file or opening the directory.

For example, for directory operations: randomly select whether to operate on an existing directory or create a new directory. If it is an operation on an existing directory, select an idle directory from the idle operation list, add the idle directory to the busy directory list, and add the idle directory to the busy directory list. Add one to the reference counts of the parent directory and all grandparent directories of the free directory; randomly determine whether the operation of the free directory is to open the directory (determine the operation premise according to the random number), if so, according to the number of operation items that need to open the directory in the global configuration information (The example in Table 1 is 3), select the number of operation items from the operation content that needs to open the directory, and add the selected operation items to the test waiting queue; if the operation of the idle directory is not to open the directory, according to the global configuration information The number of operation items that do not need to open the directory, select the number of operation items from the operation content that does not need to open the directory, and add the selected operation items to the test waiting queue. For the operation of creating a new directory, select the parent directory of the new directory from the existing directory, create a new directory under the parent directory and randomly generate the directory name, construct the operation item of the new directory, add the operation item to the test waiting queue, and put it in the test waiting queue. The reference count of the parent directory and all ancestor directories is incremented by 1. According to the length of the waiting queue configured in the global configuration information, when it is judged that the test waiting queue is full, use the operation log thread to import all operation items in the test waiting queue into the operation log, use the scheduling thread to retrieve all operation items from the operation log, and use the job The thread performs the corresponding operation on each operation item; after the operation of all operation items is executed, the reference count of the parent directory and ancestor directory involved in the directory operation is decremented by 1, and the directory in the busy directory list is moved into the idle operation list.

For file operations: randomly select whether to operate on an existing file or create a new file. If it is an operation on an existing file, select an idle file from the idle operation list, add the idle file to the busy file list, and select the parent of the idle file. Add one to the reference count of the directory and all grandparent directories; randomly determine whether the operation of the free file is to open a file (determine the operation premise according to the random number), if so, according to the number of operation items that need to open the file in the global configuration information (Table 1 example is 500), select the number of operation items from the operation content that needs to open the file, and add the selected operation items to the test waiting queue; if the operation of the idle file is not to open the file, it does not need to be opened according to the global configuration information. The number of operation items of the file, select the number of operation items from the operation contents that do not need to open the file, and add the selected operation items to the test waiting queue. For the new file operation, select the parent directory of the new file from the existing files, create a new file in the parent directory and generate the file name randomly, construct the operation item of the new file, add the operation item to the test waiting queue, and put it in the test waiting queue. The reference count of the parent directory and all ancestor directories is incremented by 1. When it is judged that the test waiting queue is full, use the operation log thread to import all the operation items in the test waiting queue into the operation log, use the scheduling thread to take out all the operation items from the operation log, and use the worker thread to perform the corresponding operation on each operation item; After the operations of all operation items are executed, the reference counts of the parent directories and ancestor directories involved in the file operation are decremented by 1, and the files in the busy file list are moved into the idle operation list.

For the soft link operation, select an idle soft connection from the existing soft connection operation list in the idle operation list, construct the operation item of the idle soft connection, add the operation item to the test waiting queue, and add the soft connection to the In the busy soft connection list, add one to the reference count of its parent directory and grandparent directory; when it is judged that the test waiting queue is full, use the operation log thread to import all operation groups in the test waiting queue into the operation log, and use the scheduling thread to Extract all operation items from the operation log, and use worker threads to perform corresponding operations on each operation item; after the operations of all operation items are executed, the reference count of the parent directory and ancestor directory involved in the soft link operation is decremented by 1, which will be busy. The soft connection in the soft connection list is moved into the idle operation list.

In this embodiment, the cluster file system testing method further includes: verifying the test result, including:

Based on the operation of the operation object of the operation item, perform the same operation on the same operation object of the file system used for verification, and obtain the operation result;

Compare test results with operational results;

If they are consistent, the verification is passed; otherwise, the inconsistent operation results and test results are output to the verification result log.

In this embodiment, based on the test results of the items to be tested in the cluster file system, the operation results of the file system used for verification are compared and verified, and the verification results with inconsistent results are output to the verification result log, which can realize Simultaneous testing and comparison of the cluster file system and the system kernel file system reduces the time cost and improves the test efficiency. Moreover, through the simultaneous operation and result comparison between the cluster file system and the system kernel file system, it can be determined that the two perform system call operations. Existing differences, and then optimize the cluster file system according to the recorded differences, thereby improving the compatibility and portability of the cluster file system.

Optionally, the system kernel file system includes, for example, UFS, ZFS, ext3, XFS, NTFS and other file systems, which are not specifically limited in this specification.

It should be noted that the methods of one or more embodiments of this specification may be executed by a single device, such as a computer or a server. The method in this embodiment can also be applied in a distributed scenario, and is completed by the cooperation of multiple devices. In the case of such a distributed scenario, one device among the multiple devices may only execute one or more steps in the method of one or more embodiments of the present specification, and the multiple devices may perform operations on each other. interact to complete the described method.

The foregoing describes specific embodiments of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that in the embodiments and still achieve desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

As shown in FIG. 2 , an embodiment of this specification further provides a cluster file system testing device, including:

a reading module for reading a configuration file; the configuration file includes global configuration information and configuration information of the item to be tested;

A creation module is used to create a test item set including at least one to-be-tested item according to the global configuration information;

a selection module for selecting a target test item from the test item set according to the configuration information of the item to be tested;

The test module is used to test the target test item and obtain the test result.

For the convenience of description, when describing the above device, the functions are divided into various modules and described respectively. Of course, when implementing one or more embodiments of this specification, the functions of each module may be implemented in one or more software and/or hardware.

The apparatuses in the foregoing embodiments are used to implement the corresponding methods in the foregoing embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

FIG. 3 shows a schematic diagram of a more specific hardware structure of an electronic device provided in this embodiment. The device may include: a processor 1010 , a memory 1020 , an input/output interface 1030 , a communication interface 1040 and a bus 1050 . The processor 1010 , the memory 1020 , the input/output interface 1030 and the communication interface 1040 realize the communication connection among each other within the device through the bus 1050 .

The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit, central processing unit), a microprocessor, an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, and is used to execute related program to implement the technical solutions provided by the embodiments of this specification.

The memory 1020 may be implemented in the form of a ROM (Read Only Memory, read only memory), a RAM (Random Access Memory, random access memory), a static storage device, a dynamic storage device, and the like. The memory 1020 may store an operating system and other application programs. When implementing the technical solutions provided by the embodiments of this specification through software or firmware, the relevant program codes are stored in the memory 1020 and invoked by the processor 1010 for execution.

The input/output interface 1030 is used to connect the input/output module to realize information input and output. The input/output/module can be configured in the device as a component (not shown in the figure), or can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, and the like.

The communication interface 1040 is used to connect a communication module (not shown in the figure), so as to realize the communication interaction between the device and other devices. The communication module may implement communication through wired means (eg, USB, network cable, etc.), or may implement communication through wireless means (eg, mobile network, WIFI, Bluetooth, etc.).

Bus 1050 includes a path to transfer information between the various components of the device (eg, processor 1010, memory 1020, input/output interface 1030, and communication interface 1040).

It should be noted that although the above-mentioned device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040 and the bus 1050, in the specific implementation process, the device may also include necessary components for normal operation. other components. In addition, those skilled in the art can understand that, the above-mentioned device may only include components necessary to implement the solutions of the embodiments of the present specification, rather than all the components shown in the figures.

The computer readable medium of this embodiment includes both permanent and non-permanent, removable and non-removable media and can be implemented by any method or technology for information storage. Information may be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Flash Memory or other memory technology, Compact Disc Read Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission medium that can be used to store information that can be accessed by a computing device.

It should be understood by those of ordinary skill in the art that the discussion of any of the above embodiments is only exemplary, and is not intended to imply that the scope of the present disclosure (including the claims) is limited to these examples; under the spirit of the present disclosure, the above embodiments or Technical features in different embodiments may also be combined, steps may be carried out in any order, and there are many other variations of the different aspects of one or more embodiments of this specification as described above, which are not in detail for the sake of brevity supply.

Additionally, in order to simplify illustration and discussion, and in order not to obscure one or more embodiments of this specification, the figures provided may or may not be shown in connection with integrated circuit (IC) chips and other components. Well known power/ground connections. Furthermore, devices may be shown in block diagram form in order to avoid obscuring one or more embodiments of this description, and this also takes into account the fact that details regarding the implementation of such block diagram devices are highly dependent on the implementation of the invention (ie, these details should be well within the understanding of those skilled in the art) of the platform describing one or more embodiments. Where specific details (eg, circuits) are set forth to describe exemplary embodiments of the present disclosure, it will be apparent to those skilled in the art that these specific details may be used without or with variations One or more embodiments of this specification are implemented below. Accordingly, these descriptions are to be considered illustrative rather than restrictive.

Although the present disclosure has been described in conjunction with specific embodiments thereof, many alternatives, modifications, and variations to these embodiments will be apparent to those of ordinary skill in the art from the foregoing description. For example, other memory architectures (eg, dynamic RAM (DRAM)) may use the discussed embodiments.

The embodiment or embodiments of this specification are intended to cover all such alternatives, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omission, modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of the present specification should be included within the protection scope of the present disclosure.

Claims (10)

1. A cluster file system test method is characterized by comprising the following steps:

reading a configuration file; the configuration file comprises global configuration information and configuration information of the item to be tested;

according to the global configuration information, creating a test item set comprising at least one item to be tested;

selecting a target test item from the test item set according to the configuration information of the item to be tested;

and testing the target test item to obtain a test result.

2. The method of claim 1, wherein the global configuration information comprises initialization configuration information for testing a cluster file system; the configuration information of the item to be tested comprises the system calling operation content and the operation proportion of the item to be tested.

3. The method of claim 2, wherein creating a set of test items including at least one item under test according to the global configuration information comprises: and adding the system call operation content of the item to be tested into an idle operation list according to the global configuration information.

4. The method of claim 3, wherein selecting a target test item from the set of test items according to the configuration information of the item under test comprises:

randomly selecting a target test item from the idle operation list according to the operation proportion of the item to be tested;

creating an operation group according to the selected target test item; the operation group comprises operation items of at least one target test item;

and adding the operation group into a test waiting queue.

5. The method of claim 4, wherein the operation item comprises an operation object, an operation object type, an operation precondition, whether an operation object already exists; and randomly determining whether the operation precondition is open or closed, if the operation object is a file or a directory, when the operation precondition is open, the operation item does not need to execute the system call operation content for opening the file or opening the directory, and when the operation precondition is closed, the operation item needs to execute the system call content for opening the file or opening the directory.

6. The method of claim 1, after reading the configuration file, further comprising: verifying the configuration file, and if the configuration file passes verification, creating a test item set comprising at least one item to be tested according to the global configuration information;

verifying the configuration file includes: judging whether a test directory for mounting the cluster file system and a check directory for mounting the file system for checking are included, and if not, checking is not passed; judging whether the sum of the operation proportions of various types of operations of various items to be detected is 100%, and if the sum of the operation proportions of at least one operation is not 100%, the verification is not passed; and judging whether the precision of each operation proportion accords with the precision of the operation proportion configured in the global configuration information, if not, the verification is not passed.

7. The method of claim 6, wherein the configuration file is verified, and further comprising, if the configuration file is verified, the step of: emptying the test directory and the check directory; and creating a test item set comprising at least one item to be tested according to the global configuration information.

8. The method of claim 4, wherein testing the target test item to obtain a test result comprises:

fetching an operation group from the test wait queue;

determining each operation item in the operation group;

analyzing the operation item, and determining the operation needed to be executed by the operation object;

and executing operation on the operation object to obtain a test result.

9. The method of claim 8, further comprising: and verifying the test result, including:

based on the operation of the operation object of the operation item, the same operation is executed on the same operation object of the file system for verification, and an operation result is obtained;

comparing the test result with the operation result;

if the operation result is consistent with the test result, the test result passes the verification, otherwise, the inconsistent operation result and the test result are output to a verification result log.

10. A cluster file system testing device, comprising:

the reading module is used for reading the configuration file; the configuration file comprises global configuration information and configuration information of the item to be tested;

the creating module is used for creating a test item set comprising at least one item to be tested according to the global configuration information;

the selection module is used for selecting a target test item from the test item set according to the configuration information of the item to be tested;

and the test module is used for testing the target test item to obtain a test result.

Images