File access method and device, electronic equipment and storage medium

Abstract

This invention relates to the field of computer technology and discloses a file access method, apparatus, electronic device, and storage medium. Based on a file access request sent by a user, the corresponding file access type is determined. A target file name is generated based on the original file name represented by the file access request, and then a unique target access identifier is determined. In the case of case-insensitive access, the target file is determined based on a preset index table, the unique target access identifier, and the target file name. By converting the original file name into a unique target access identifier, different file access types are all converted into a unified unique target access identifier. The target file is then determined using the unique target access identifier, enabling file access in both case-sensitive and case-insensitive systems, thus achieving cross-system file access.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically to a file access method, apparatus, electronic device, and storage medium. Background Technology

[0002] In distributed storage systems, due to the different ways that different operating systems handle file names, Windows systems use a case-insensitive file access method by default, while Linux / Unix systems are case-sensitive. This leads to the problem that file access requests from different operating systems may have file names that are inconsistent with the file names in the storage system.

[0003] In related technologies, files are typically stored in a case-sensitive manner. This causes the file name to be inconsistent with the name in the storage system when accessed by users in case-insensitive operating systems, making it impossible to retrieve the target file. Therefore, distributed storage systems have cross-operating system compatibility issues. Summary of the Invention

[0004] This application provides a file access method, apparatus, electronic device, and storage medium to at least solve the cross-operating system compatibility problem of distributed storage systems in related technologies.

[0005] This application provides a file access method, including: Get the file access request sent by the user; Based on the file access request, determine the corresponding file access type; among which, file access types include case-insensitive access. Generate the target file name based on the original file name represented by the file access request; Based on the target file name, determine the unique target access identifier for the file access request; When the file access type is case-insensitive, the target access file is determined based on a preset index table, using a unique target access identifier and the target file name.

[0006] This application also provides a file access device, including: The acquisition module is used to acquire file access requests sent by users; The first determining module is used to determine the corresponding file access type based on the file access request; the file access type includes case-insensitive access. The name generation module is used to generate the target file name based on the original file name represented by the file access request; The second determination module is used to determine the unique target access identifier of the file access request based on the target file name; The third determination module is used to determine the target access file based on a preset index table, according to the unique target access identifier and the target file name, when the file access type is case-insensitive access.

[0007] This application also provides a distributed storage system, which includes: multiple operating systems and storage systems; Users can send file access requests to the storage system through any operating system; The storage system responds to file access requests using any of the above file access methods.

[0008] This application also provides an electronic device, including: a memory for storing a computer program; and a processor for implementing any of the above-described file access methods when executing the computer program.

[0009] This application also provides a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of any of the above-described file access methods.

[0010] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of any of the above-described file access methods.

[0011] This application achieves cross-system file access by determining the corresponding file access type based on the user's file access request, generating a target file name based on the original file name represented by the file access request, and then determining the corresponding unique target access identifier. In the case of case-insensitive access, the target access file is determined based on a preset index table, the unique target access identifier, and the target file name. By converting the original file name into a unique target access identifier, different file access types are converted into a unified unique target access identifier. The target access file is then determined through the unique target access identifier, enabling both case-sensitive and case-insensitive systems to access files. Attached Figure Description

[0012] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 This is a schematic diagram of the structure of the file access system on which the embodiments of this application are based; Figure 2 A flowchart illustrating the file access method provided in this application embodiment; Figure 3 A flowchart illustrating an exemplary file access method provided in an embodiment of this application; Figure 4 A schematic diagram of the structure of the file access device provided in the embodiments of this application; Figure 5 This is a schematic diagram of the structure of a distributed storage system provided in an embodiment of this application; Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0014] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of this application.

[0015] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0016] In current distributed Samba client application scenarios, there are application requirements for case-insensitive access. To achieve this, we add a case-insensitive queue to the directory inode to record case-insensitive records in that directory, but this queue is directly bound to the directory inode. Distributed storage systems face the issue of filename case sensitivity. Different operating systems handle filenames differently; Windows systems use a case-insensitive file access method by default, while Linux / Unix systems are strictly case-sensitive. There are cross-platform file access requirements in the storage environment, and case sensitivity can cause service interruptions.

[0017] Current mainstream distributed storage systems, such as CephFS, HDFS, and AWS S3, primarily handle case sensitivity by enforcing a uniform case-sensitive policy. Most systems choose to enforce a single case-sensitive policy, which is often sensitive and leads to numerous "file not found" errors when accessing files from Windows clients. Alternatively, some systems maintain a global case-sensitive mapping dictionary, storing all possible variations of "Document.txt" such as "DOCUMENT.TXT" and "document.txt". In a cluster with 100 million files, this can increase metadata memory usage by over 40% and increase directory traversal latency by 3-5 times. Real-time conversion solutions suffer from severe performance issues, increasing the average latency of a single lookup operation from 2ms to 15ms. In high-frequency, small-file access scenarios such as deep learning training, overall throughput can decrease by up to 60%.

[0018] To address the aforementioned technical problems, this application provides a file access method, apparatus, electronic device, and storage medium. The method includes: acquiring a file access request sent by a user; determining a corresponding file access type based on the file access request; wherein the file access type includes case-insensitive access; generating a target file name based on the original file name represented by the file access request; determining a unique target access identifier for the file access request based on the target file name; and, in the case where the file access type is case-insensitive access, determining the target access file based on a preset index table, the unique target access identifier, and the target file name.

[0019] The method provided by the above scheme determines the corresponding file access type based on the file access request sent by the user, generates the target file name based on the original file name represented by the file access request, and then determines the corresponding unique target access identifier. In the case of case-insensitive access, the target access file is determined based on a preset index table, according to the unique target access identifier and the target file name. By converting the original file name into a unique target access identifier, different file access types are all converted into a unified unique target access identifier. The target access file is then determined through the unique target access identifier, enabling file access to be achieved in both case-sensitive and case-insensitive systems, thus realizing cross-system file access.

[0020] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0021] The specific application environment architecture or specific hardware architecture on which the file access method depends is described here.

[0022] First, the structure of the file access system upon which this application is based will be described: The file access method, apparatus, electronic device, and storage medium provided in this application are suitable for implementing file access in cross-system scenarios, such as... Figure 1 The diagram shows the structure of a file access system based on an embodiment of this application. It mainly includes a target file to be accessed, a data acquisition device, and a file access device. The data acquisition device is used to acquire file access requests, and the file access device, based on the file access method provided in this embodiment, enables file access in a case-insensitive system.

[0023] This application provides a file access method for enabling file access in a case-insensitive system. The execution subject of this application is an electronic device, such as a server, desktop computer, laptop computer, tablet computer, or other electronic devices capable of file access.

[0024] like Figure 2 The diagram shown is a flowchart illustrating a file access method provided in an embodiment of this application. The method includes: Step 201: Obtain the file access request sent by the user.

[0025] Step 202: Determine the corresponding file access type based on the file access request.

[0026] Among them, file access types include case-insensitive access.

[0027] Specifically, users send file access requests through different operating systems and according to the corresponding network file protocols. By parsing the file access requests, the source of the user, the network file protocol used, and the corresponding operating system are determined. Based on the type of operating system, the file access type is determined, which includes case-insensitive access and case-sensitive access.

[0028] Accordingly, by parsing the file access request and determining the corresponding file access type based on the network file protocol used, a foundation is provided for selecting the appropriate file access path in the future.

[0029] Step 203: Generate the target file name based on the original file name represented by the file access request.

[0030] Specifically, the original filename is case-sensitive, and the target filename is generated according to preset rules. The target filename is usually case-insensitive. For example, if the original filename of a file access request is ReadMe.txt, and the preset rule is to change the original filename to all lowercase, then the corresponding target filename will be readme.txt.

[0031] Step 204: Determine the unique target access identifier for the file access request based on the target file name.

[0032] Specifically, a unique target access identifier is typically generated based on the target file name using a cryptographic hash algorithm.

[0033] Accordingly, by converting the original file name into a unified target file name, and then generating a corresponding unique target access identifier based on the target file name, a unique mapping relationship between the original file name and the file is established. At the same time, the original file names of different operating systems are all converted into a unified unique target access identifier, which solves the problem of files not being found due to inconsistent capitalization, and allows case-insensitive systems to access files in the storage system.

[0034] Furthermore, by using a unique target access identifier, the time complexity of querying the target access file is reduced, avoiding the need to traverse and search for the target access file in the storage system. By using key-value queries, the efficiency of retrieving the target access file is improved.

[0035] Step 205: When the file access type is case-insensitive access, the target access file is determined based on the preset index table, according to the unique target access identifier and the target file name.

[0036] Specifically, the preset index table includes a unique target access identifier and the storage address of the corresponding target access file. Based on the unique target access identifier and the target file name, the storage address of the target access file is determined in the preset index table, and thus the target access file is determined.

[0037] Correspondingly, the pre-defined index table establishes a mapping relationship between unique target access identifiers and target access files. This allows case-insensitive systems to establish a mapping relationship between the original file name and the target access file through the unique target access identifier. Consequently, case-insensitive systems can also determine the target access file based on the original file name. This enables the distributed storage system to handle file access requests from both case-sensitive and case-insensitive systems, thus improving the compatibility of the distributed storage system.

[0038] Based on the above embodiments, as an implementable approach, in one embodiment, determining the corresponding file access type according to the file access request includes: Step 2021: Determine the target communication protocol based on the protocol type represented by the file access request; Step 2022: Determine the target operating system based on the target communication protocol; Step 2023: Determine the corresponding file access type based on the target operating system.

[0039] Specifically, the target communication protocol is determined based on the protocol type represented by the file access request. For example, the target operating system for the NFS protocol is Linux, while the target operating system for the SMB protocol is Windows. Windows is case-insensitive, while Linux is case-sensitive. Therefore, the corresponding file access type is determined by the protocol type represented by the file access request.

[0040] Specifically, in one embodiment, when the file access type is case-sensitive access, the target access file is determined based on a preset index table, according to the unique target access identifier and the original file name.

[0041] Specifically, in one embodiment, a target file list is determined based on a preset index table and a unique target access identifier; and the target access file is retrieved from the target file list based on the original file name.

[0042] Specifically, the target file list contains files that share the same target file name but have different original file names, along with their storage location information in the storage system.

[0043] The pre-defined index table includes a unique target access identifier and its corresponding target file list storage location information. Based on the unique target access identifier, the storage location information of the corresponding target file list is determined, and based on this storage location information, the target file list is determined. Since the target file list contains at least one original filename and its corresponding file storage location information, for case-sensitive access types, the target access file is further determined from the target file list based on the original filename.

[0044] For example, the original file name is ReadMe.txt, the corresponding file access type is case-sensitive access, the generated target file name is readme.txt, and its corresponding unique target access identifier is 0x4F9A2C1E. The corresponding preset index table is shown in Table 1 below: Table 1 Preset Index Table

[0045] Based on the storage location information / index / lists / readme_list.bin, the system loads the corresponding list of target files, as shown in Table 2 below: Table 2 Target File List

[0046] The system matches the user-requested original file name "ReadMe.txt" in the loaded target file list. Upon successful matching, the system obtains the corresponding file storage location information as inode=1002. Based on this physical location information (inode=1002), the system locates and accesses the target file ReadMe.txt in the storage system.

[0047] Accordingly, by determining the target file list in a pre-defined index table based on a unique target access identifier, sequential traversal and querying within the storage system are avoided. Then, based on the original file name, the target access file is determined from the target file list. Since the number of records in the target file list is relatively small, this two-level search mechanism reduces the time complexity of the query and improves query efficiency. Furthermore, by processing filenames and directory names separately, memory usage is only related to the actual size of the accessed files, rather than the total size of the file system.

[0048] Specifically, in one embodiment, the historical access count of the target access file is accumulated to determine the cumulative value; if the cumulative value is greater than a preset access threshold, the target access file is determined to be a frequently accessed file; the frequently accessed file is sent to memory so that the user can quickly retrieve the frequently accessed file in memory.

[0049] For example, if the target access file is ReadMe.txt, stored on the disk, and the target access file is accessed 11 times within a unit of time, with a preset call threshold of 10 times, when the system detects that the cumulative value 11>10, it determines that the target access file is a frequently accessed file and caches the file from the disk to a hash table in memory. When the next file access request indicates that the target access file is accessed, the target access file is retrieved from the hash table in memory without accessing the disk index.

[0050] If a frequently accessed file is not accessed again within a preset time period, it is removed from memory and its cumulative value is reset. Based on the cumulative value and the preset call threshold, the automatic migration of hot and cold data is realized.

[0051] Correspondingly, since memory access is faster than disk access, by identifying frequently accessed files and pre-loading them into memory, subsequent related access requests can be responded to directly in memory, improving file access efficiency. At the same time, the time taken for most invalid queries, such as the first access, can be reduced to O(1). Memory resources are concentrated on serving active files, improving the hit rate, while cold data does not affect system throughput.

[0052] Specifically, in one embodiment, the original file name represented by the file access request is converted into a case-insensitive alias according to a case-insensitive alias generation strategy; the case-insensitive alias is then used as the target file name.

[0053] Specifically, the original filename is case-sensitive, and a case-insensitive alias is generated based on a case-insensitive alias generation strategy. The target filename is typically case-insensitive. For example, if the original filename of a file access request is ReadMe.txt, and the case-insensitive alias generation strategy modifies the original filename to all lowercase, then the corresponding target filename will be readme.txt.

[0054] Accordingly, the case-insensitive alias generation strategy is determined according to the requirements and can be adapted to a variety of application scenarios.

[0055] For example, such as Figure 3 The diagram illustrates an exemplary file access method provided in this application. Operating systems include Linux and Windows, encompassing both case-sensitive and case-insensitive systems. Each system accesses the middleware service components via different protocols. For example, Linux clients can access the Nfs-ganesha service via the Nfs+VIP protocol, while Windows clients access the Samba service via the Smb protocol. Some Linux / Windows clients can also access the service via the Vsftp service using the FTP protocol. Additionally, kernel clients directly interface with the underlying layer. The metadata server coordinates the interaction between the various operating systems and the storage system. Requests from Linux and Windows clients first generate corresponding target file names, then generate unique target access identifiers using a hash algorithm. These identifiers are submitted to the metadata server (MDS) via the CephFS client library (libcfsfs) and the RADOS client library (librados). A Bloom filter queries a preset index table in the MDS to obtain a list of target files, which is then matched against the original file names to ultimately locate the target file in the storage system. Finally, the actual data read / write operations are performed by the backend storage system. The backend storage system is hosted by a RADOS cluster consisting of OSD / Mon / Rados.

[0056] Specifically, in one embodiment, in a distributed storage system, when multiple file access requests are received simultaneously, they are stored in a case-sensitive access queue and a case-insensitive access queue according to their corresponding file access types. At the same time, according to the priority of the file access requests, higher priority file access requests are responded to first. Since the processing paths for case-sensitive access and case-insensitive access are different, by storing the file access requests in the queues, the corresponding file access requests can be executed directly according to their respective processing paths, avoiding interference between different processing paths and improving the response efficiency of file access.

[0057] The file access method provided in this application includes: obtaining a file access request sent by a user; determining the corresponding file access type based on the file access request; wherein the file access type includes case-insensitive access; generating a target file name based on the original file name represented by the file access request; determining a unique target access identifier for the file access request based on the target file name; and, in the case where the file access type is case-insensitive access, determining the target access file based on a preset index table, the unique target access identifier, and the target file name.

[0058] The method provided by the above scheme determines the corresponding file access type based on the file access request sent by the user, generates the target file name based on the original file name represented by the file access request, and then determines the corresponding unique target access identifier. In the case of case-insensitive access, the target access file is determined based on a preset index table, according to the unique target access identifier and the target file name. By converting the original file name into a unique target access identifier, different file access types are all converted into a unified unique target access identifier. The target access file is then determined through the unique target access identifier, enabling file access to be achieved in both case-sensitive and case-insensitive systems, thus realizing cross-system file access.

[0059] Furthermore, by parsing file access requests and determining the corresponding file access type based on the network file protocol used, a foundation is laid for subsequently selecting the appropriate file access path. By converting the original filename into a unified target filename, and then generating a corresponding unique target access identifier based on the target filename, a unique mapping relationship between the original filename and the file is established. Simultaneously, this ensures that original filenames from different operating systems are converted into a unified unique target access identifier, resolving the problem of files being unfindable due to inconsistent capitalization, allowing case-insensitive systems to access files in the storage system. Furthermore, the unique target access identifier reduces the time complexity of target file lookups, avoiding traversing the storage system to search for the target file, and improving the efficiency of retrieving target files through key-value lookups. A pre-defined index table establishes a mapping between unique target access identifiers and target access files. This allows case-insensitive systems to determine the target file based on the original filename using the unique target access identifier, thus enabling both case-insensitive and case-insensitive systems to access files. This improves the compatibility of the distributed storage system. By determining the target file list in the pre-defined index table based on the unique target access identifier, sequential traversal of the storage system is avoided. Then, the target file is determined from the target file list based on the original filename. Since the number of records in the target file list is relatively small, this two-level search mechanism reduces the time complexity of the query and improves query efficiency. Furthermore, by processing filenames and directory names separately, memory usage is only related to the actual size of the accessed files, rather than the total size of the file system. Since memory access is faster than disk access, frequently accessed files are identified and pre-loaded into memory, allowing subsequent access requests to be handled directly in memory, thus improving file access efficiency. This also reduces the time taken for most invalid queries, such as the initial access, to O(1). Memory resources are concentrated on serving active files, improving the hit rate, while cold data does not affect system throughput. The case-insensitive alias generation strategy is determined according to requirements and can be adapted to various application scenarios.

[0060] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method.

[0061] Embodiments of this application also provide a file access apparatus for executing the file access method provided in the above embodiments.

[0062] like Figure 4 The diagram shown is a structural schematic of a file access device provided in an embodiment of this application. The file access device 40 includes: an acquisition module 401, a first determination module 402, a name generation module 403, a second determination module 404, and a third determination module 405.

[0063] The system includes: an acquisition module for acquiring file access requests sent by users; a first determination module for determining the corresponding file access type based on the file access request, wherein the file access type includes case-insensitive access; a name generation module for generating a target file name based on the original file name represented by the file access request; a second determination module for determining a unique target access identifier for the file access request based on the target file name; and a third determination module for determining the target access file based on a preset index table, the unique target access identifier, and the target file name, when the file access type is case-insensitive access.

[0064] Specifically, in one embodiment, the first determining module is further configured to: Based on the protocol type represented by the file access request, determine the target communication protocol; based on the target communication protocol, determine the target operating system; based on the target operating system, determine the corresponding file access type.

[0065] Specifically, in one embodiment, the file access device further includes: The fourth determination module is used to determine the target access file based on a preset index table, a unique target access identifier, and the original file name when the file access type is case-sensitive.

[0066] Specifically, in one embodiment, the fourth determining module is further configured to: Based on a pre-defined index table, a list of target files is determined according to a unique target access identifier; the target access file is then retrieved from the list of target files based on the original file name.

[0067] Specifically, in one embodiment, the file access device further includes: The migration module is used to accumulate the historical access count of the target file and determine the cumulative value; if the cumulative value is greater than the preset call threshold, the target file is determined to be a frequently accessed file; the frequently accessed file is sent to memory so that the user can quickly retrieve the frequently accessed file in memory.

[0068] Specifically, in one embodiment, the name generation module is further configured to: According to the case-insensitive alias generation strategy, the original file name represented by the file access request is converted into a case-insensitive alias; the case-insensitive alias is then used as the target file name.

[0069] For a description of the features in the embodiment corresponding to the file access device, please refer to the relevant description in the embodiment corresponding to the file access method, which will not be repeated here.

[0070] Embodiments of this application also provide a distributed storage system for executing the file access method provided in the above embodiments.

[0071] like Figure 5 The diagram shown is a schematic representation of the distributed storage system provided in an embodiment of this application. The system includes: multiple operating systems and a storage system; Users send file access requests to the storage system through any operating system; the storage system responds to the file access requests using any of the above file access methods.

[0072] For a description of the features in the embodiments corresponding to the distributed storage system, please refer to the relevant descriptions in the embodiments corresponding to the file access method, which will not be repeated here.

[0073] Embodiments of this application also provide an electronic device, such as... Figure 6 The diagram shown is a schematic diagram of the structure of an electronic device provided in an embodiment of this application, including a processor 10 and a memory 20. The memory 20 stores a computer program, and the processor 10 is configured to run the computer program to perform the steps in any of the above-described file access method embodiments.

[0074] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above-described file access method embodiments when it is run.

[0075] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0076] Embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above-described file access method embodiments.

[0077] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in any of the above-described file access method embodiments.

[0078] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0079] The foregoing has provided a detailed description of a file access method, apparatus, electronic device, and storage medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only intended to aid in understanding the method and core ideas of this application. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A file access method, characterized in that, The method includes: Get the file access request sent by the user; Based on the file access request, determine the corresponding file access type; wherein, the file access type includes case-insensitive access; Generate the target file name based on the original file name represented by the file access request; Based on the target file name, a unique target access identifier for the file access request is determined; When the file access type is case-insensitive access, the target access file is determined based on the preset index table, according to the unique target access identifier and the target file name.

2. The file access method according to claim 1, characterized in that, The step of determining the corresponding file access type based on the file access request includes: The target communication protocol is determined based on the protocol type represented by the file access request; The target operating system is determined based on the target communication protocol. Determine the corresponding file access type based on the target operating system.

3. The file access method according to claim 1, characterized in that, The method further includes: When the file access type is case-sensitive, the target access file is determined based on a preset index table, according to the unique target access identifier and the original file name.

4. The file access method according to claim 3, characterized in that, When the file access type is case-sensitive, the target access file is determined based on a preset index table, according to the unique target access identifier and the original file name, including: Based on a preset index table, a list of target files is determined according to the unique target access identifier; Based on the original file name, the target access file is retrieved from the target file list.

5. The file access method according to claim 1, characterized in that, The method further includes: Accumulate the historical access count of the target file and determine the cumulative value; If the cumulative value is greater than a preset call threshold, the target access file is determined to be a frequently accessed file; The frequently accessed files are sent to memory so that users can quickly retrieve them from memory.

6. The file access method according to claim 1, characterized in that, The step of generating the target file name based on the original file name represented by the file access request includes: According to the case-insensitive alias generation strategy, the original file name represented by the file access request is converted into a case-insensitive alias; Use the case-insensitive alias as the target file name.

7. A file access device, characterized in that, The device includes: The acquisition module is used to acquire file access requests sent by users; The first determining module is used to determine the corresponding file access type based on the file access request; wherein, the file access type includes case-insensitive access; The name generation module is used to generate a target file name based on the original file name represented by the file access request; The second determining module is used to determine a unique target access identifier for the file access request based on the target file name; The third determination module is used to determine the target access file based on a preset index table, according to the unique target access identifier and the target file name, when the file access type is case-insensitive access.

8. A distributed storage system, characterized in that, The system includes: multiple operating systems and storage systems; The user sends a file access request to the storage system through any of the operating systems described; The storage system responds to the file access request using the file access method as described in any one of claims 1 to 6.

9. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the file access method as described in any one of claims 1 to 6 when executing the computer program.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the file access method as described in any one of claims 1 to 6.

Images