WO2016191964A1

WO2016191964A1 - Management method and device of file system

Info

Publication number: WO2016191964A1
Application number: PCT/CN2015/080371
Authority: WO
Inventors: 王金波
Original assignee: 华为技术有限公司
Priority date: 2015-05-29
Filing date: 2015-05-29
Publication date: 2016-12-08
Also published as: CN107111549A; CN107111549B

Abstract

A management method and device of a file system. The method comprises: allocating a data block bitmap area for a file system in a first consecutive address segment of a storage apparatus (101); allocating N partitions for the file system in a second consecutive address segment of the storage apparatus, wherein each of the N partitions is used to store system metadata of each of the partitions (102); and allocating a shared data block area of the N partitions for the file system in a third consecutive address segment of the storage apparatus, wherein the shared data block area is used to store a file (103). The data block bitmap area is used to store a first use identifier configured to indicate whether a data block of the shared data block area is used, and each of the data blocks corresponds to the first use identifier. The first consecutive address segment, the second consecutive address segment, and the third consecutive address segment form a consecutive address segment.

Description

File system management method and device

Technical field

The present application relates to the field of electronic technologies, and in particular, to a file system management method and apparatus.

Background technique

As shown in FIG. 1a, it is a schematic diagram of a file system in a storage device. The storage space in the storage device is divided into system storage space and user storage space. The system storage space typically contains a plurality of fixed partitions, such as partition 1, partition 2 to partition N in Figure 1a. The size of each fixed partition has been designed by the designer at the time of shipment from the factory, and the possibility of being able to be changed after leaving the factory is minimal.

Please refer to FIG. 1a and FIG. 1b at the same time, and FIG. 1b is a schematic diagram of further layout of the partition 1 in FIG. 1a. After the file system is formatted for the system storage space, the partition 1 includes a super block area, a data block bitmap area, an inode bitmap area, an inode area, and a data block area. After formatting, not only the size of partition 1 is fixed, but the location of each zone is also fixed.

The super block area is used to record the system information of the file system of the partition 1, such as the type and size of the file system. The data block bitmap area is defined by the data structure of the bitmap, and each bit represents the use of a data block. For example, a value of 0 indicates that the data block corresponding to the bit is not used, and a value of 1 indicates that the data block corresponding to the bit has been used. The index node bitmap area is also defined by the data structure of the bitmap, and each bit represents the use of an index node. Each index node of the inode area corresponds to a file. The index node records the attributes of the file and the storage address of the file in the data block. The file can be found in the data block by the index node. The data block is used to store files.

Partition 2 to partition N are laid out in the same way as partition 1.

Generally, in order to ensure the scalability of the system and the continuity of the product, each fixed partition is allocated a storage space larger than the space required by the partition, so that the storage space is wasted.

In addition, in actual use, it is often the case that partition 1 has been used up, but partition 2 has free space, or partition 1 has free space and partition 2 has run out. In order to solve such problems, Designers will continue to expand the size of partition 1 or partition 2 in the new product, then the system storage space will increase, so the user storage space will be compressed, so there is a problem of low storage space utilization.

Summary of the invention

The embodiment of the present invention provides a file system management method and device, which are used to solve the technical problem of low storage space utilization in the prior art.

The first aspect of the present application provides a file system management method, including:

Allocating a data block bitmap area to the file system on a first consecutive address segment of the storage device;

Allocating N partitions to the file system on a second consecutive address segment of the storage device, each partition of the N partitions respectively for storing system metadata of each partition; N is greater than 1 Integer

Allocating a shared data block area of the N partitions for the file system on a third consecutive address segment of the storage device, the shared data block area is for storing a file; the data block bitmap area is used for Storing a first usage identifier, where the first usage identifier is used to indicate whether a data block in the shared data block area is used, and each of the data blocks corresponds to one of the first usage identifiers; wherein the first The contiguous address segment, the second contiguous address segment, and the third contiguous address segment form a contiguous address segment.

With reference to the first aspect, in a first possible implementation manner of the first aspect, each of the partitions includes an index node area and an index node bitmap area, where the index node of the index node area is used for recording and storing a storage address of a file in the shared data block area; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used; each of the index nodes corresponds to One of the second usage identifiers;

After the shared data block area of the N partitions is allocated to the file system on the third consecutive address segment of the storage device, the method further includes:

Receiving a request to create a file in an i-th partition of the N partitions; the request includes The size of the file;

Determining, by the first usage identifier, an unused data block in the shared data block area;

Determining a size of a remaining capacity in the shared data block area according to the number and size of the unused data blocks;

Determining, according to the size of the file and the size of the remaining capacity, whether the remaining capacity is sufficient to create the file;

Determining, when the remaining capacity is sufficient to create the file, a storage address to be stored in the shared data block area, and searching for an unused portion in an index node bitmap area of the i-th partition Index node;

When there is an unused index node, selecting one of the unused index nodes, writing an attribute of the file and the storage address;

Changing the second usage identifier corresponding to the one index node in the bitmap node bitmap area to a value indicating that the one index node has been used;

Storing the file in a data block corresponding to the storage address in the shared data block area;

The first usage identifier of the data block corresponding to the storage address is changed in the data block bitmap to a value indicating that the data block has been used.

With reference to the first aspect, in a second possible implementation manner of the first aspect, each of the partitions includes an index node area and an index node bitmap area, where the index node of the index node area is used for recording and storing An attribute of the file in the shared data block and a storage address; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used, and each of the index nodes Corresponding to one of the second use identifiers,

Receiving a request to delete a file by the partition j in the N partitions;

Finding a corresponding index node in an index node area of the partition j according to an attribute of the file:

Determining, according to the storage address recorded by the index node, a data block corresponding to the storage address in the shared data block;

Changing the first usage identifier of the data block corresponding to the storage address in the data block bitmap area to a value indicating that the data block is not used;

Changing the second usage identifier of the corresponding index node in the index node bitmap area of the partition j to a value indicating that the corresponding index node is not used.

The second aspect of the present application provides a file system management method, including:

Allocating, by the file system, a first partition on a second consecutive address segment of the storage device, where the first partition is configured to store system metadata of the first partition;

Allocating a second partition to the file system on a third consecutive address segment of the storage device, where the second partition is configured to store system metadata of the second partition;

Allocating a shared data block area of the first partition and the second partition to the file system on a fourth consecutive address segment of the storage device; wherein the shared data block area is used to store a file; The data block bitmap area is configured to store a first usage identifier, where the first usage identifier is used to indicate whether a data block in the shared data block area is used, and each of the data blocks corresponds to one of the first Using an identifier; the first consecutive address segment, the second consecutive address segment, the third consecutive address segment, and the fourth consecutive address segment form a contiguous address segment, the fourth consecutive The address segment is located between the second consecutive address segment and the third consecutive address segment.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the first partition includes an index node area and an index node bitmap area, where the index node of the index node area is used for recording and storing An attribute of the file in the shared data block and a storage address; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used; each of the index nodes Corresponding to one of the second use identifiers;

After the allocating the shared data block area of the first partition and the second partition to the file system on the fourth consecutive address segment of the storage device, the method further includes:

Receiving a request to create a file in the first partition; the request includes a size of the file;

Determining, when the remaining capacity is sufficient to create the file, a storage address to be stored in the shared data block area, and searching for an unused portion in an index node bitmap area of the first partition Index node

With reference to the second aspect, in a second possible implementation manner of the second aspect, the first partition includes an index node area and an index node bitmap area, where the index node of the index node area is used for recording and storing An attribute of the file in the shared data block and a storage address; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used, and each of the index nodes Corresponding to one of the second use identifiers,

Receiving a request to delete a file in the first partition;

Finding a corresponding index node in an index node area of the first partition according to an attribute of the file:

The first use identifier of a data block corresponding to the storage address in the data block bitmap area Change to a value indicating that the data block is not used;

Changing the second usage identifier of the corresponding index node in the index node bitmap area of the first partition to a value indicating that the corresponding index node is not used.

The third aspect of the present application provides a file system management method, including:

Allocating a super block area to the file system on a first consecutive address segment of the storage device, where the super block area is used to record system information of the file system; the system information includes a type and size of the file system ;

Allocating a bitmap area to the file system on a second consecutive address segment of the storage device;

Allocating a shared area to the file system on a third consecutive address segment of the storage device, the shared area is configured to store a file and an index node; and the index node is configured to record a file stored in the shared area a storage address; the bitmap area is configured to store a usage identifier, where the usage identifier is used to indicate whether a data block in the shared area is used, and each of the data blocks corresponds to one of the usage identifiers; A contiguous address segment, the second contiguous address segment, and the third contiguous address segment form a contiguous address segment.

In conjunction with the third aspect, in a first possible implementation manner of the third aspect, the method further includes:

When the space is allocated to the index node in the shared area, the first address end of the shared area is allocated to the second address end;

When the space is allocated to the file in the shared area, the second address end of the shared area is allocated to the first address end.

With reference to the third aspect, or the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, the file system is allocated on a third consecutive address segment of the storage device After the shared area, the method further includes:

Receiving a request for creating a file; the request includes a size of the file;

Determining an unused data block in the shared area according to the usage identifier;

Determining a size of a remaining capacity in the shared area according to the number and size of the unused data blocks;

Determining, according to the size of the file and the size of the remaining capacity, whether the remaining capacity is sufficient to create the file and storing an index node corresponding to the file;

When the remaining capacity is sufficient to store the file and store an index node corresponding to the file, create the file on the unused data block and record a storage address of the file in the corresponding index In the node;

Changing the usage identifier of the data block corresponding to the storage address and the index node in the bitmap area to a value indicating that the data block has been used.

In conjunction with the third aspect or the second possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the method further includes:

And updating a space size value occupied by all the index nodes stored in the shared area recorded in the super block area and a space size value occupied by all the files stored in the shared area.

In conjunction with the third aspect, or the first possible implementation manner of the third aspect, in a fourth possible implementation manner of the third aspect, the index node further records an attribute of the file,

After the shared area is allocated to the file system on the third consecutive address segment of the storage device, the method further includes:

Receiving a request for querying a file, the request including an attribute of the file;

Querying an index node corresponding to the attribute in the shared area;

Searching for a file corresponding to the storage address in the shared area according to a storage address recorded in the corresponding index node.

A fourth aspect of the present application provides a file system management method, including:

a data block bitmap allocation module, configured to allocate a data block bitmap area to the file system on a first consecutive address segment of the storage device;

a metadata partition allocation module, configured to allocate N partitions to the file system on a second consecutive address segment of the storage device, where each partition of the N partitions is used to store each partition System metadata; N is an integer greater than one;

a data block allocation module, configured to allocate a common data block area of the N partitions to the file system on a third consecutive address segment of the storage device, where the shared data block area is used to store a file; The data block bitmap area is configured to store a first usage identifier, where the first usage identifier is used to indicate whether a data block in the shared data block area is used, and each of the data blocks corresponds to one of the first An identifier is used; wherein the first consecutive address segment, the second consecutive address segment, and the third consecutive address segment form a contiguous address segment.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, each of the partitions includes an index node area and an index node bitmap area, where the index node of the index node area is used for recording and storing a storage address of a file in the shared data block area; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used; each of the index nodes corresponds to a second use identifier; the device further comprises:

a receiving module, configured to receive a request for creating a file in an i-th partition of the N partitions; the request includes a size of the file;

a processing module, configured to determine, by using the first usage identifier, an unused data block in the shared data block region; determining a remaining portion in the shared data block region according to the number and size of the unused data blocks a size of the capacity; determining, according to the size of the file and the size of the remaining capacity, whether the remaining capacity is sufficient to create the file; when the remaining capacity is sufficient to create the file, determining that the file is to be stored in the Determining a storage address in the shared data block area, and searching whether there is an unused index node in the index node bitmap area of the i-th partition; when there is an unused index node, selecting the unused An index node in the index node, writing an attribute of the file and the storage address; changing the second usage identifier corresponding to the one index node in the bitmap node bitmap area to indicate the a value that has been used by an index node; storing the file in a data block corresponding to the storage address in the shared data block area; The first usage identifier of the data block corresponding to the storage address is changed to a value indicating that the data block has been used.

With reference to the fourth aspect, in a second possible implementation manner of the fourth aspect, each of the partitions includes an index node area and an index node bitmap area, where the index node of the index node area is used for recording and storing An attribute of the file in the shared data block and a storage address; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is enabled Each of the index nodes corresponds to one of the second usage identifiers, and the device further includes:

a receiving module, configured to receive a request for deleting a file in the partition j in the N partitions;

a processing module, configured to search, according to an attribute of the file, a corresponding index node in an index node area of the partition j: determining, according to a storage address recorded by the index node, data corresponding to the storage address in the shared data block a block; changing, in the data block bitmap area, the first usage identifier of a data block corresponding to the storage address to a value indicating that the data block is not used; and an index node bit of the partition j The second usage identifier of the corresponding index node is changed in the map area to a value indicating that the corresponding index node is not used.

The fifth aspect of the present application provides a file system management apparatus, including:

a metadata partition allocation module, configured to allocate a first partition to the file system on a second consecutive address segment of the storage device, where the first partition is configured to store system metadata of the first partition; Assigning a second partition to the file system on a third consecutive address segment of the storage device, where the second partition is configured to store system metadata of the second partition;

a data block allocation module, configured to allocate a common data block area of the first partition and the second partition to the file system on a fourth consecutive address segment of the storage device; wherein the shared data The block area is configured to store a file; the data block bitmap area is configured to store a first use identifier, and the first use identifier is used to indicate whether a data block in the shared data block area is used, each of the data The block corresponds to one of the first usage identifiers; the first consecutive address segment, the second consecutive address segment, the third consecutive address segment, and the fourth consecutive address segment form a continuous address segment The fourth consecutive address segment is located between the second consecutive address segment and the third consecutive address segment.

With reference to the fifth aspect, in a first possible implementation manner of the fifth aspect, the first partition includes an index node area and an index node bitmap area, where the index node of the index node area is used for recording and storing An attribute of the file in the shared data block and a storage address; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is enabled Each of the index nodes corresponds to one of the second usage identifiers; the device further includes:

a receiving module, configured to receive a request for creating a file in the first partition; the request includes a size of the file;

a processing module, configured to determine, by using the first usage identifier, an unused data block in the shared data block region; determining a remaining portion in the shared data block region according to the number and size of the unused data blocks a size of the capacity; determining, according to the size of the file and the size of the remaining capacity, whether the remaining capacity is sufficient to create the file; when the remaining capacity is sufficient to create the file, determining that the file is to be stored in the Determining a storage address in the shared data block area, and searching whether there is an unused index node in the index node bitmap area of the first partition; when there is an unused index node, selecting the unused one An index node in the index node, writing an attribute of the file and the storage address; changing the second usage identifier corresponding to the one index node in the bitmap node bitmap area to represent the one a value at which an index node has been used; storing the file in a data block corresponding to the storage address in the shared data block area; The data block corresponding to the memory address using a first identifier to change the value has been used to represent the data block.

With reference to the fifth aspect, in a second possible implementation manner of the fifth aspect, the first partition includes an index node area and an index node bitmap area, where the index node of the index node area is used for recording and storing An attribute of the file in the shared data block and a storage address; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used, and each of the index nodes Corresponding to one of the second use identifiers,

The device also includes:

a receiving module, configured to receive a request to delete a file in the first partition;

a processing module, configured to search, according to an attribute of the file, a corresponding index node in an index node area of the first partition: determining, according to a storage address recorded by the index node, a corresponding to the storage address in the shared data block a data block; changing the first usage identifier of the data block corresponding to the storage address in the data block bitmap area to a value indicating that the data block is not used; and indexing the first partition The second usage identifier change of the corresponding index node in the bitmap area A value indicating that the corresponding index node is not used.

The sixth aspect of the present application provides a file system management apparatus, including:

a super block allocation module, configured to allocate a super block area for the file system on a first consecutive address segment of the storage device, where the super block area is used to record system information of the file system; The type and size of the file system;

a bitmap allocation module, configured to allocate a bitmap area to the file system on a second consecutive address segment of the storage device;

a shared area allocation module, configured to allocate a shared area to the file system on a third consecutive address segment of the storage device, where the shared area is used for storing files and an index node; and the index node is used for recording and storing a storage address of the file in the shared area; the bitmap area is configured to store a usage identifier, where the usage identifier is used to indicate whether a data block in the shared area is used, and each of the data blocks corresponds to a The usage identifier is used; the first consecutive address segment, the second consecutive address segment, and the third consecutive address segment form a contiguous address segment.

With reference to the sixth aspect, in a first possible implementation manner of the sixth aspect, the device further includes a processing module, when the space is allocated to the index node in the shared area, from the shared area The first address end is allocated to the second address end direction; when the shared area allocates space for the file, the second address end of the shared area is allocated to the first address end direction.

In conjunction with the sixth aspect, in a second possible implementation manner of the first aspect, the device further includes:

a receiving module, configured to receive a request for creating a file; the request includes a size of the file;

a processing module, configured to determine, according to the usage identifier, an unused data block in the shared area; determining a size of a remaining capacity in the shared area according to the number and size of the unused data blocks; Determining a size of the file and a size of the remaining capacity to determine whether the remaining capacity is sufficient to create the file and storing an index node corresponding to the file; when the remaining capacity is sufficient to store the file and store an index corresponding to the file a node, creating the file on the unused data block and recording a storage address of the file in the corresponding index node; The usage identifier of the data block corresponding to the storage address and the index node in the bitmap area is changed to a value indicating that the data block has been used.

With reference to the second possible implementation manner of the sixth aspect, in a third possible implementation manner of the sixth aspect, the processing module is further configured to: update the storage in the shared area recorded in the super block a value of the size of the space occupied by all of the index nodes and a value of the size of the space occupied by all of the files stored in the shared area.

In conjunction with the sixth aspect, in a fourth possible implementation manner of the sixth aspect, the device further includes:

a receiving module, configured to receive a request for querying a file, where the request includes an attribute of the file;

a processing module, configured to query an index node corresponding to the attribute in the shared area; and search for a file corresponding to the storage address in the shared area according to the storage address recorded in the corresponding index node.

A seventh aspect of the present application provides an electronic device, including:

Memory

a processor for allocating a data block bitmap area to the file system on a first consecutive address segment of the memory; assigning N to the file system on a second consecutive address segment of the memory a partition, each partition of the N partitions being used to store system metadata of each partition; N is an integer greater than 1; and the file system is allocated on a third consecutive address segment of the memory a shared data block area of the N partitions, where the shared data block area is used to store a file; the data block bitmap area is used to store a first use identifier, and the first use identifier is used to represent the shared data Whether the data blocks in the block area are used, each of the data blocks corresponding to one of the first usage identifiers; wherein the first consecutive address segment, the second consecutive address segment, and the third continuous The address segments form a contiguous address segment.

With reference to the seventh aspect, in a first possible implementation manner of the seventh aspect, each of the partitions includes an index node area and an index node bitmap area, where the index node of the index node area is used for recording and storing a storage address of a file in the shared data block area; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used; The index node corresponds to one of the second usage identifiers, and the electronic device further includes an input device.

The input device is configured to receive a request for creating a file in an i th partition of the N partitions; the request includes a size of the file;

The processor is further configured to: determine, by using the first usage identifier, an unused data block in the shared data block area; determine the shared data block area according to the number and size of the unused data blocks. a size of the remaining capacity; determining, according to the size of the file and the size of the remaining capacity, whether the remaining capacity is sufficient to create the file; when the remaining capacity is sufficient to create the file, determining that the file is to be Storing a storage address in the shared data block area, and searching for an unused index node in an index node bitmap area of the i-th partition; when there is an unused index node, selecting the An index node of an unused index node, writes an attribute of the file and the storage address; and changes the second usage identifier corresponding to the one index node in the bitmap node bitmap area to a value indicating that the one index node has been used; storing the file in a data block corresponding to the storage address in the shared data block area; The first usage identifier of the data block corresponding to the storage address in the figure is changed to a value indicating that the data block has been used.

With reference to the seventh aspect, in a second possible implementation manner of the seventh aspect, each of the partitions includes an index node area and an index node bitmap area, where the index node of the index node area is used for recording and storing An attribute of the file in the shared data block and a storage address; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used, and each of the index nodes Corresponding to one of the second usage identifiers, the electronic device further includes an input device,

The input device is configured to receive a request for deleting a file by a partition j in the N partitions;

The processor is further configured to: search, according to an attribute of the file, a corresponding index node in an index node area of the partition j: determining, in the shared data block, the storage address according to a storage address recorded by the index node Corresponding data block; changing the first usage identifier of the data block corresponding to the storage address in the data block bitmap area to a value indicating that the data block is not used; indexing the partition j Changing the second usage identifier of the corresponding index node in the node bitmap area to A value indicating that the corresponding index node is not used.

An eighth aspect of the present application provides an electronic device, including:

Memory

a processor for allocating a data block bitmap area to the file system on a first consecutive address segment of the memory; assigning a first to the file system on a second consecutive address segment of the memory a partition, the first partition is configured to store system metadata of the first partition; a second partition is allocated to the file system on a third consecutive address segment of the memory, the second partition is configured to store System metadata of the second partition; a shared data block region of the first partition and the second partition is allocated to the file system on a fourth consecutive address segment of the memory; wherein a shared data block area for storing a file; the data block bitmap area is for storing a first use identifier, and the first use identifier is used to indicate whether a data block in the shared data block area is used, each of the The data block corresponds to one of the first usage identifiers; the first consecutive address segment, the second consecutive address segment, the third consecutive address segment, and the fourth consecutive address segment are consecutive Address segment, Said fourth consecutive addresses between the second consecutive addresses and consecutive addresses of said third segment.

With reference to the eighth aspect, in a first possible implementation manner of the eighth aspect, the first partition includes an index node area and an index node bitmap area, where the index node of the index node area is used for recording and storing An attribute of the file in the shared data block and a storage address; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used; each of the index nodes Corresponding to one of the second usage identifiers; the electronic device further includes an input device,

The input device is configured to receive a request for creating a file in the first partition; the request includes a size of the file;

The processor is further configured to: determine, by using the first usage identifier, an unused data block in the shared data block area; determine the shared data block area according to the number and size of the unused data blocks. The size of the remaining capacity; determining whether the remaining capacity is sufficient to create the file according to the size of the file and the size of the remaining capacity; when the remaining capacity is sufficient to create the file Determining, that the file is to be stored in the shared data block area, and searching for an unused index node in the index node bitmap area of the first partition; when there is an unused When the node is indexed, one of the unused index nodes is selected, the attribute of the file and the storage address are written; and the corresponding location of the index node in the bitmap area corresponding to the one index node is The second usage identifier is changed to a value indicating that the one index node has been used; the file is stored in a data block corresponding to the storage address in the shared data block area; the data block bitmap is The first usage identifier of the data block corresponding to the storage address is changed to a value indicating that the data block has been used.

With reference to the first aspect, in a second possible implementation manner of the eighth aspect, the first partition includes an index node area and an index node bitmap area, where the index node of the index node area is used for recording and storing An attribute of the file in the shared data block and a storage address; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used, and each of the index nodes Corresponding to one of the second usage identifiers, the electronic device further includes an input device,

The input device is configured to receive a request to delete a file in the first partition;

The processor is further configured to: search, according to an attribute of the file, a corresponding index node in an index node area of the first partition: determining, in the shared data block, the storage according to a storage address recorded by the index node a data block corresponding to the address; changing the first usage identifier of the data block corresponding to the storage address in the bitmap area of the data block to a value indicating that the data block is not used; The second usage identifier of the corresponding index node in the index node bitmap area is changed to a value indicating that the corresponding index node is not used.

The ninth aspect of the present application provides an electronic device, including:

Memory

a processor, configured to allocate a super block area for the file system on a first consecutive address segment of the memory, the super block area for recording system information of the file system; a type, a size of a file system; a bitmap area is allocated to the file system on a second consecutive address segment of the memory; and the file system is on a third consecutive address segment of the memory Allocating a shared area for storing a file and an index node; the index node is configured to record a storage address of a file stored in the shared area; and the bitmap area is configured to store a use identifier, Using an identifier for indicating whether a data block in the shared area is used, each of the data blocks corresponding to one of the usage identifiers; the first consecutive address segment, the second consecutive address segment, and the The third consecutive address segment constitutes a contiguous address segment.

With reference to the ninth aspect, in a first possible implementation manner of the ninth aspect, the processor is further configured to: when the space is allocated to the index node in the shared area, the first from the shared area The address end is allocated to the second address end direction; when the shared area allocates space for the file, the second address end of the shared area is allocated to the first address end direction.

In conjunction with the ninth aspect, in a second possible implementation manner of the ninth aspect, the electronic device further includes an input device,

The input device is configured to receive a request for creating a file; the request includes a size of the file;

The processor is further configured to: determine, according to the usage identifier, an unused data block in the shared area; determine a size of a remaining capacity in the shared area according to the number and size of the unused data blocks. Determining, according to the size of the file and the size of the remaining capacity, whether the remaining capacity is sufficient to create the file and storing an index node corresponding to the file; when the remaining capacity is sufficient to store the file and store the file And corresponding to the index node, creating the file on the unused data block and recording a storage address of the file in the corresponding index node; and the bitmap address and the storage address The usage identifier of the data block corresponding to the index node is changed to a value indicating that the data block has been used.

In conjunction with the second possible implementation of the ninth aspect, in a third possible implementation manner of the ninth aspect, the processor is further configured to: update the storage in the shared area recorded in the super block area The size of the space occupied by all of the index nodes and the size of the space occupied by all of the files stored in the shared area.

In conjunction with the ninth aspect, in a fourth possible implementation manner of the ninth aspect, the electronic device further includes an input device,

The input device is configured to receive a request for querying a file, where the request includes an attribute of the file;

The processor is further configured to: query an index node corresponding to the attribute in the shared area; and search for a storage address corresponding to the storage address in the shared area according to a storage address recorded in the corresponding index node. file.

One or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages:

In the embodiment of the present application, the data block area of each partition is shared, and then all the partitions also share the same data block bitmap. When it is necessary to store data in a certain partition, as long as the data block bitmap shows that the data block area has enough remaining capacity, the data can be stored in the data block area. In the prior art, when data needs to be stored in a certain partition, if the data block bitmap of a certain partition shows that the data block area does not have enough remaining capacity, the data cannot be stored. The adjacent partition of a partition has space, but due to the limitation of the layout, data cannot be stored in the data block area of the adjacent partition. Therefore, compared with the prior art, the file system management method of the embodiment of the present application enables the storage space to be fully utilized, thereby reducing the wasted space.

DRAWINGS

1a-1b are schematic diagrams showing a layout of a file system in a prior art on a storage device;

2 is a flowchart of a method for managing a file system according to an embodiment of the present application;

3a-3b are schematic diagrams of layouts of multiple file systems provided on a storage device according to an embodiment of the present application;

4 is a flowchart of a method for creating a file in a file system according to an embodiment of the present application;

FIG. 5 is a flowchart of a method for deleting a file in a file system according to an embodiment of the present disclosure;

FIG. 6 is a flowchart of another method for managing a file system according to an embodiment of the present application;

7a-7b are schematic diagrams of layout of another file system on a storage device according to an embodiment of the present application;

FIG. 8 is a flowchart of still another method for managing a file system according to an embodiment of the present application;

FIG. 9 is a schematic diagram of a layout of another system on a storage device according to an embodiment of the present disclosure;

FIG. 10 is a flowchart of another method for creating a file in a file system according to an embodiment of the present disclosure;

FIG. 11 is a flowchart of a method for searching for a file in a file system according to an embodiment of the present application;

FIG. 12 is a functional block diagram of a file system management apparatus according to an embodiment of the present application;

FIG. 13 is a structural diagram of an electronic device according to an embodiment of the present application;

FIG. 14 is a functional block diagram of another file system management apparatus according to an embodiment of the present application;

FIG. 15 is a structural diagram of another electronic device according to an embodiment of the present disclosure;

FIG. 16 is a functional block diagram of still another file system management apparatus according to an embodiment of the present application;

FIG. 17 is a structural diagram of still another electronic device according to an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present application. It is a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

Please refer to FIG. 2 , which is a flowchart of a method for managing a file system according to an embodiment of the present application.

As shown in Figure 2, the method includes:

Step 101: Allocating a data block bitmap area to the file system on a first consecutive address segment of the storage device;

Step 102: Allocate N partitions to the file system on a second consecutive address segment of the storage device. Each partition of the N partitions is used to store system metadata of each partition respectively; N is greater than 1 Integer

Step 103: Allocate a shared data block area of N partitions for the file system on a third consecutive address segment of the storage device, where the shared data block area is used for storing files.

The data block bitmap area is used to store the first usage identifier, and the first usage identifier is used to indicate whether the data block in the shared data block area is used, and each data block corresponds to a first usage identifier.

The first consecutive address segment, the second consecutive address segment, and the third consecutive address segment form a continuous address segment.

Specifically, the data block bitmap area is defined by the data structure of the bitmap, and each bit represents the use of a data block. That is, the size of a first use identifier is one bit. The first usage identifier is, for example, 0 and 1, with 0 indicating that the data block is not used. Use 1 to indicate that the data block has been used. Of course, in actual use, the first usage identifier may be other data as long as it can indicate whether a certain data block is used.

In step 102, N partitions are allocated to the system on the storage device. Specifically, the number of Ns may be determined according to the purpose, that is, the role of each partition is different. In other words, the type of file corresponding to each partition is different. For example, partitioning can be performed according to the partitioning method in the prior art, that is, the file system in the prior art has several partitions, and several partitions are allocated in step 102.

Optionally, the size of each partition may be the same or different. Since the type and number of metadata stored in each partition are different, the size of N partitions can be specifically allocated according to the type and number of stored metadata.

In a specific implementation process, the order between step 101, step 102, and step 103 may be arbitrarily changed, or three steps may be performed simultaneously.

It should be noted that the storage device in this embodiment and the following embodiments may be a physical storage space of a single hard disk or a USB disk, or may be a partial storage space on a hard disk or a USB disk. For example, if the total size of a hard disk is 500G, the storage device in the embodiment of the present application may be the entire 500G storage space or 200G storage space.

Generally speaking, when a user triggers an operation of formatting a storage device, the storage device is installed. The electronic device can perform steps 101 to 103.

Optionally, consecutive address segments in the embodiment of the present application indicate that the logical addresses are consecutive. Therefore, in steps 101 to 103, the respective areas are allocated in accordance with consecutive logical addresses.

Further, a case where the first consecutive address segment, the second consecutive address segment, and the third consecutive address segment form a continuous address segment is, for example, a logical tail address of the data block bitmap area and a first of the N partitions The logical first address of the partitions is contiguous, and the logical tail address of the last partition of the N partitions and the logical first address of the shared data block area are consecutive. Accordingly, step 102 specifically includes allocating N partitions to the file system on a second consecutive address segment starting from a next address of a logical tail address of the data block bitmap region. Step 103 specifically includes allocating N partition shared data block regions to the file system on a third consecutive address segment starting from a next address of a logical tail address of a last partition of the N partitions.

Optionally, when all the areas are allocated, the allocation may be performed in a direction from a low address end to a high address end, or may be allocated in a direction from a high address end to a low address end. Specifically, for example, the address of the second consecutive address segment is higher than the first consecutive address segment, and the address of the third consecutive address segment is higher than the second consecutive address segment.

In the actual application, please refer to the following specific examples for the location of each zone.

The first example is as shown in FIG. 3a. FIG. 3a is a schematic diagram of a layout structure after the file system is laid out on the storage device according to the file system management method shown in FIG. 2.

In this example, the data block bitmap area is at the low address end. N partitions are immediately followed by a data block bitmap area layout, and N partitions are located on the high and low side of the data block bitmap area. The shared data block area is then followed by the last partition layout of the N partitions. The address between the first address of the data block bitmap area and the tail address of the shared data block area is continuous.

Optionally, when storing data to each area, it may be stored in a direction from a low address end to a high address end.

For the second example, please refer to FIG. 3b. FIG. 3b is a schematic diagram of a layout structure after the file system is laid out on the storage device according to the file system management method shown in FIG. 2.

The second example is different from the first example in that the shared data block area is allocated in the data block bitmap area and N blocks. Between partitions.

It can be seen from the above description that the file system management method of the embodiment of the present application extracts the data blocks of the N partitions to form a continuous storage space, and the data block bitmap area of each area is also separated from the prior art. Coming out to form a continuous bitmap area for storing a first usage identifier indicating whether the data block of the shared data block area is used. Therefore, in the embodiment of the present application, as long as the data block bitmap shows that the data block area has sufficient remaining capacity, the data can be stored in the data block area. In the prior art, when data needs to be stored in a certain partition, if the data block bitmap of a certain partition shows that the data block area does not have enough remaining capacity, the data cannot be stored. The adjacent partition of a partition has space, but due to the limitation of the layout, data cannot be stored in the data block area of the adjacent partition. Therefore, compared with the prior art, the file system management method of the embodiment of the present application enables the storage space to be fully utilized, thereby reducing the wasted space. At the same time, the file system management method in the embodiment of the present application avoids the problem that each partition design is larger than the required size, thereby compressing the user storage space, thereby avoiding waste of the storage space.

Further, the file system management method in the embodiment of the present application only needs to know how much space the entire file system requires, and does not need to know the size of each specific partition, thereby improving the research and development efficiency of the designer.

Further, when the method described in FIG. 2 and its embodiment is applied in the user storage space, it is also possible to realize the technical effect that the file can be stored in any one partition as long as there is sufficient storage space in the shared data block area. For example, when a user stores a movie in the D-disc, as long as there is sufficient storage space in the shared data block area, the storage operation can be responded, thereby storing the movie data in the D-disc. In the prior art, if there is not enough storage space in the data block area of the D disk, the movie data cannot be stored in the D disk, but can only be changed to other partition disks having free storage space, such as an E disk. . Therefore, the method in the embodiment of the present application is more convenient for the user to use than the prior art.

In a further embodiment, each partition of the N partitions includes a super block area, an index node bitmap area, and an index node area. The super block area is used to record system information of the file system of each partition, such as the type and size of the file system. Further, the super block area is also used to record the remaining area of the shared data block area. Remaining capacity. The index node of the inode area is used to record the storage address of the file stored in the shared block area. Further, the inode also records the properties of the file. Attributes include information that uniquely identifies a file, such as the name of a file. The file can be found in the shared data block area by the index node. An index node corresponds to the storage address of a file. Further, the attribute also includes information such as the size of the file.

The index node bitmap area is used to store the second usage identifier, and the second usage identifier is used to indicate whether the index node is used. Each index node corresponds to a second usage identifier. The index node bitmap area can also be defined by the data structure of the bitmap. Each bit represents the use of an index node or not.

Because in the embodiment of the present application, the data blocks of each partition are extracted to form an overall shared data block area, and in order to ensure that each partition has greater capability to use the shared data block, the index node bitmap and the index node area are also Large points can be allocated appropriately. For example, with partition 1 as an example, in the existing technical solution, partition 1 has 10000 data blocks, and 2500 index node spaces may be allocated. It is now possible to allocate 5000 index node spaces to partition 1 because each index node and index node The bitmap space is small and the space used is negligible. This ensures that the index node of each partition is sufficient when there are free data blocks, so that as long as the free data block is large enough to store the file, the file can be stored in any partition.

Of course, in actual use, the number of inodes is specifically related to the type of data stored in the partition. For example, if the partition is primarily used to store big data, the number of index nodes can be less. If the partition is mainly used to store small data, but the amount of data is large, the number of index nodes can be a little more.

The following is an example of the process of creating a file in a partition after performing system layout in accordance with the method shown in FIG. 2. For example, as shown in Figure 4, create a file in partition i.

First, a request to add a file to the partition i is received, the request including the size of the file. The unused data blocks in the shared data block area are then determined by the first usage identification. For example: 0 means that the data block is not used, and 1 means that the data block has been used. Then all the data blocks corresponding to 0 are unused data blocks. The size of the remaining capacity in the shared data block area is then determined based on the number and size of unused data blocks. Because the size of each data block is known, so according to The amount and size of the data blocks used can be used to calculate the size of the remaining capacity. This part of the content is well known to those skilled in the art, so it will not be described here.

After determining the remaining capacity size in the shared data block area, it is determined whether the remaining capacity is sufficient to create the file according to the size of the file and the size of the remaining capacity. For example, the remaining capacity is 10MB. If the size of the newly added file is 8MB, the result of the determination is that the remaining capacity is sufficient. If the size of the newly added file is 15MB, then the result of the determination is that the remaining capacity is not enough.

If the remaining capacity is insufficient to create the file, the user interface (UI) can be used to prompt the user for insufficient disk space.

If the remaining capacity is sufficient to create the file, then it is determined that the file is to be stored in the shared data block area, and the index node of the partition i is searched for an unused index node. . Wherein, determining that the file is to be stored in a storage address in the shared data block area, specifically, determining a data block to be stored in an unused data block, and then the address of the data block is The storage address where the file will be stored. This part of the content is well known to those skilled in the art, so it will not be described here.

Generally, the number of inodes is set to be sufficient. As mentioned above, the index node area can be allocated slightly larger, which ensures that when there is enough remaining capacity in the shared data block area to create a file, the inode area has An inode that is not being used. Of course, if there is an extreme situation, the index node has been allocated, then the UI can also prompt the user that the index node of partition 1 has been allocated.

When an unused index node is found, the file is assigned an index node, and the attributes of the file and the storage address are populated in the index node. The second usage identifier corresponding to the one index node is then changed in the index node bitmap area to a value indicating that the one index node has been used.

The file is written to a data block in the shared data block area corresponding to the storage address. The first usage identification of the data block corresponding to the storage address is then changed in the data block bitmap area to a value indicating that the data block has been used. For example, in the data block bitmap area, the first use identifier of the occupied data block is set to 1, indicating that the data block has been used.

It should be noted that in the above steps, in the case of no conflict, the steps between the steps The order can be exchanged.

It can be seen that after the file system management method in the embodiment of the present application lays out the system, the shared data block is a resource pool, and the data can be performed by querying the data block bitmap to find that there is sufficient remaining capacity in the shared data block area. storage. Compared with the prior art, if the capacity of the partition that needs the newly added file is insufficient, the file cannot be added, and the data block corresponding to the other partition is wasted. Therefore, the file system management method in the embodiment of the present application can save storage space.

Next, the process of deleting a file by the partition j in the N partitions will be described. Please refer to Figure 5 for details.

First, a request to delete a file in partition j is received. Specifically, for example, the user selects a file on the partition j, such as the D disk, and then right clicks, and selects the “delete” option in the right-click menu, then the electronic device receives the request to delete the file.

Then, the corresponding index node is searched in the index node area of the partition j according to the attributes of the file. Specifically, as previously mentioned, the metadata includes the storage address of the file. Further, the metadata may further include an attribute of the file, the attribute including an attribute value that can uniquely identify a file, such as a name of the file. Optionally, the attribute may also include the size of the file, and the like. Therefore, the attributes in the metadata can be matched with the metadata recorded by each index node in the inode area. When the matching is successful, the index node that successfully matches is the index node corresponding to the file.

After finding the index node corresponding to the file, determining a data block corresponding to the storage address in the shared data block according to the storage address recorded by the index node. The first usage identification of the data block corresponding to the storage address is then changed in the data block bitmap area to a value indicating that the data block is not used. This step means that the data blocks occupied by the deleted files are recycled. In actual use, the files in the data block may be erased after determining the data blocks occupied by the file. Of course, the erasing operation may not be performed because the first usage identifier corresponding to the data block has been changed to a value indicating that the data block is not used in the data block bitmap, so if there is a file created later At the time of request, when the remaining capacity in the shared data block area is determined, the state of the data block is unused, that is, new data can be stored. Therefore, if new data is stored on the data block, it is only necessary to overwrite the original data in the data block.

Next, in the index node bitmap area of the partition j, the second usage identifier of the corresponding index node is changed to a value indicating that the corresponding index node is not used, and the index node corresponding to the file is recovered. . Similarly, the attributes of the file and the storage address in the corresponding index node may also be deleted, or may not be deleted, but the attributes of the file and the storage address may be directly overwritten at the next storage.

Based on the same inventive concept as the method shown in FIG. 2, the embodiment of the present application further provides a file system, where the file system includes: a data block bitmap area, N partitions, and a shared data block area. The meanings of these areas and the layout relationship between them are the same as those described in the foregoing method shown in FIG. 2 and its embodiments, and therefore will not be described herein.

Next, please refer to FIG. 6 , which is a flowchart of another method for managing a file system according to an embodiment of the present application. As shown in FIG. 6, the method includes:

Step 201: Allocating a data block bitmap area to the file system on a first consecutive address segment of the storage device;

Step 202: Allocating a first partition to the file system on a second consecutive address segment of the storage device, where the first partition is used to store system metadata of the first partition;

Step 203: Allocating a second partition to the file system on a third consecutive address segment of the storage device, where the second partition is configured to store system metadata of the second partition.

Step 204: Allocating a shared data block area of the first partition and the second partition to the file system on a fourth consecutive address segment of the storage device; wherein, the shared data block area is used for storing a file; and the data block bitmap area is And configured to store a first usage identifier, where the first usage identifier is used to indicate whether a data block in the shared data block region is used, and each data block corresponds to a first usage identifier.

The first consecutive address segment, the second consecutive address segment, the third consecutive address segment, and the fourth consecutive address segment form a contiguous address segment. The fourth consecutive address segment is located between the second consecutive address segment and the third consecutive address segment.

The meaning of the consecutive address segments and the meaning of the consecutive address segments are the same as those described in the foregoing FIG. 2 and its embodiments.

As shown in FIG. 7a, the file system is laid out according to the file system management method shown in FIG. After the layout diagram.

In this example, the data block bitmap area is located at the lower address end, and the partition 1 is immediately followed by the data block bitmap area and is located at the high address side of the data block bitmap area. Then, the shared data block area is next to the partition 1 and is located on the high address side of the partition 1. Then, the partition 2 is next to the shared data block area and is located on the high address side of the shared data block area.

Of course, in actual use, the positional relationship between the zones can be other situations, for example, the reverse of the sequence of FIG. 7a, the data block bitmap area is located at the high address end, and the partition 2 is located at the low address end.

Similar to FIG. 2 and its embodiment, the first partition and the second partition also include a super block area, an index node area, and an index node bitmap area. The meanings of the super block area, the inode area, and the index node bitmap area are similar to those described above, and therefore will not be described herein.

It should be noted that, in the case where the shared data block is located between the first partition and the second partition, the order and location of the super block area, the index node bitmap area, and the index node area included in the partition located at the lower address end of the shared data block area The order of the super block area, the index node bitmap area, and the index node area included in the partition of the high address side of the shared data block area may be reversed.

For example, referring to FIG. 7b, the partition 1 and the partition 2 are respectively located at the lower address end and the upper address end of the shared data block area. The order of the three sub-partitions of the partition 1 in the direction from the low address end to the high address end is the super block area, the index node bitmap area, and the index node area. The three sub-partitions of partition 2 are in the direction from the low address end to the high address end, and are respectively in the order of the index node area, the index node bitmap area, and the super block area. Therefore, the file system of partition 2 is "reverse growth".

For the file system layout manner in this embodiment, the process of creating a file in the first partition or the second partition is the same as the process of creating a file described above, that is, the foregoing partition i may be replaced with the first partition or the second partition. The process of deleting a file in the first partition or the second partition is the same as the process of deleting the file described above, that is, the aforementioned partition j may be replaced with the first partition or the second partition. For the sake of brevity of the description, it will not be repeated here.

Based on the same inventive concept as the method shown in FIG. 6, the embodiment of the present application provides a file system, where the file system includes: a data block bitmap area, a first partition, a shared data block area, and a second partition. Wherein, the meaning and layout of each zone are the same as those described in the foregoing method and its embodiment shown in FIG. So I won't go into details here.

Next, please refer to FIG. 8 , which is a flowchart of still another method for managing a file system according to an embodiment of the present application. As shown in Figure 8, the method includes:

Step 301: Allocating a super block area to the file system on a first consecutive address segment of the storage device, where the super block area is used to record system information of the file system; the system information includes a type and a size of the file system;

Step 302: Allocating a bitmap area to the file system on a second consecutive address segment of the storage device;

Step 303: Allocate a shared area to the file system on a third consecutive address segment of the storage device, where the shared area is used to store files and index nodes.

The index node is used to record the storage address of the file stored in the shared area. The bitmap area is used to store the usage identifier, and the usage identifier is used to indicate whether the data block in the shared area is used. Each data block corresponds to a usage identifier. The first consecutive address segment, the second consecutive address segment, and the third consecutive address segment form a contiguous address segment.

Further, the super block area is also used to record the size of the space occupied by all the index nodes in the shared area and the space occupied by all the files in the shared area. Further, the super block area is also used to record the total size of the shared area. The size of the remaining space in the shared area can be obtained according to the total size of the shared area, the size of the space occupied by all the index nodes, and the size of the space occupied by all the files. The information described above recorded in the super block area facilitates subsequent management of the partition corresponding to the super block area.

Further, the index node of the inode area is also used to record the attributes of the file stored in the data block area. Properties include information that uniquely identifies a file, such as a file name. Further, the attribute also includes information such as file size.

In the above embodiments, the storage address is, for example, information indicating an address such as an address pointer, an address itself, or an address offset.

In the prior art, as shown in FIG. 1b, when the partition 1 is used to store large files, the index node area often has a lot of space to use, thus causing waste of storage space. In this embodiment, the remaining area of the index node is also used as the storage space of the storage file, so the storage is reduced. The waste of storage space increases the utilization of storage space.

Specifically, please refer to FIG. 9 , which is a schematic diagram of the layout of the file system on the storage device after the file system is laid out according to the method shown in FIG. 8 .

Optionally, the storage space is conveniently utilized, so the method further includes: when the index node is allocated space for the index node, the first address end of the shared area is allocated to the second address end; when in the shared area When space is allocated for a file, allocation is made from the second address end of the shared area to the first address end. Specifically, the first address end is, for example, a low address end, and the second address end is, for example, a high address end.

Based on the same inventive concept as the method shown in FIG. 8, the embodiment of the present application provides a file system, where the file system includes: a super block area, a bitmap area, and a shared area. The meaning and layout of each area are the same as those described in the foregoing method shown in FIG. 8 and its embodiments, and therefore are not described herein again.

Next, please refer to FIG. 10, which is a flowchart of a method for creating a file in a file system according to an embodiment of the present application. The layout of the file system on the storage device is performed, for example, in accordance with the layout shown in FIG.

As shown in FIG. 10, the method includes:

Step 401: Receive a request for creating a file, where the request includes a size of the file.

Step 402: Determine, according to the usage identifier in the bitmap area, an unused data block in the shared area.

Step 403: Determine the size of the remaining capacity in the shared area according to the number and size of the unused data blocks.

Step 404: Determine, according to the size of the file and the size of the remaining capacity, whether the remaining capacity is sufficient to create the file and store an index node corresponding to the file.

Step 405: When the remaining capacity is sufficient to store the file and store the index node corresponding to the file, create the file on the unused data block and record the storage address of the file in the corresponding index node;

Step 406: Change the usage identifier of the data block corresponding to the storage address and the index node in the bitmap area to a value indicating that the data block has been used.

The storage address is, for example, an address pointer, and may of course be the address itself or an address. A bias or the like is used to indicate information of an address.

It can be seen that, in the prior art, even if there is a remaining storage space in the index node area, and a new file cannot be created when it is determined that the remaining space of the data block area is insufficient, in the embodiment of the present application, Because the index node and the file use the same shared area together, as long as there is enough storage space in the shared area to store the file and the corresponding index node of the file, the file can be stored, thereby improving the utilization of the storage space and reducing the storage. The waste of space.

As described above, when the storage area is allocated to the index node in the shared area, it is allocated from the low address end to the high address end. When creating a file, the storage space is allocated from the high address side to the low address side. In this way, the space occupied by the index node and the space occupied by the file is a complete continuous storage space, which is convenient for storing various sizes of data, and avoids the need to randomly allocate space, and the shared area has several discontinuities. The storage space, such that the size of the file that can be stored is easily limited, so the method in this embodiment can further improve the utilization of the storage space.

Optionally, after step 406, the method further includes: updating a space size value occupied by all index nodes stored in the shared area recorded in the super block area and a space size value occupied by all files stored in the shared area. Since the space occupied by the index node in the shared area and the space occupied by the file have changed through steps 401 to 406, the update is performed after step 406. This allows the superblock to keep track of the latest situation and facilitate subsequent management of the entire partition.

The process of creating a file is described above, and the process of how to find a file will be described next. Please refer to FIG. 11 , which is a flowchart of a method for searching for a file in a file system according to an embodiment of the present application.

As shown in FIG. 11, the method includes:

Step 501: Receive a request for querying a file, where the request includes an attribute of the file;

Step 502: Query an index node corresponding to the attribute in the shared area.

Step 503: Search for a file corresponding to the storage address in the shared area according to the storage address recorded in the corresponding index node.

In step 501, the request for receiving the query file may be a request triggered by the query operation itself, or may be a request triggered by another operation request, for example, deleting the file, and The process of triggering a file search first.

After the file is found according to the method shown in FIG. 11, the file may be subjected to a desired operation, such as deletion.

After deleting the file, the method further includes: modifying the usage identifier corresponding to the storage address and the index node in the bitmap area to a value indicating that the storage address and the data block corresponding to the index node have been used.

Based on the same inventive concept, with reference to FIG. 12, it is a functional block diagram of a file system management apparatus according to an embodiment of the present application, which is used to implement the file system management method shown in FIG. 2 to FIG. 5 of the present invention. For the meaning of the terms involved in the above, please refer to the contents described in the foregoing embodiments. The file system management device includes: a data block bitmap allocation module 601, configured to allocate a data block bitmap area for the file system on a first consecutive address segment of the storage device; the metadata partition allocation module 602 </ RTI> for allocating N partitions to the file system on a second consecutive address segment of the storage device, each partition of the N partitions respectively for storing system metadata of each partition; N is greater than An integer of 1; a data block allocating module 603, configured to allocate, for the file system, a shared data block area of the N partitions on a third consecutive address segment of the storage device, where the shared data block area is used to store a file; The data block bitmap area is configured to store a first usage identifier, where the first usage identifier is used to indicate whether a data block in the shared data block area is used, and each of the data blocks corresponds to one of the first An identifier is used; wherein the first consecutive address segment, the second consecutive address segment, and the third consecutive address segment form a contiguous address segment.

Optionally, each partition includes an index node area and an index node bitmap area, where the index node of the index node area is used to record a storage address of a file stored in the shared data block area; the index node bitmap The device is configured to store a second usage identifier, where the second usage identifier is used to indicate whether the index node is used; each of the index nodes corresponds to one of the second usage identifiers;

a processing module, configured to determine, by using the first usage identifier, that the shared data block area is not enabled a data block; determining a size of the remaining capacity in the shared data block area according to the number and size of the unused data blocks; determining the remaining according to the size of the file and the size of the remaining capacity Whether the capacity is sufficient to create the file; when the remaining capacity is sufficient to create the file, determine a storage address to be stored in the shared data block area, and an index node bit in the i-th partition The map area is searched for whether there is an unused index node; when there is an unused index node, one of the unused index nodes is selected, and the attribute of the file and the storage address are written; Changing the second usage identifier corresponding to the one index node in the bitmap node bitmap area to a value indicating that the one index node has been used; storing the file in the shared data block area a data block corresponding to the storage address; changing the first usage identifier of the data block corresponding to the storage address in the data block bitmap to represent the data The value that the block has been used.

Optionally, each partition includes an index node area and an index node bitmap area, where the index node of the index node area is used to record attributes of the file stored in the shared data block and a storage address; the index node bit The device area is configured to store a second usage identifier, where the second usage identifier is used to indicate whether the index node is used, and each of the index nodes corresponds to one of the second usage identifiers, and the device further includes:

a processing module, configured to search, according to an attribute of the file, a corresponding index node in an index node area of the partition j: determining, according to a storage address recorded by the index node, data corresponding to the storage address in the shared data block Blocking; changing the first usage identifier of the data block corresponding to the storage address in the data block bitmap area to a value indicating that the data block is not used; and using an index node bitmap of the partition j The second usage identifier of the corresponding index node in the zone is changed to a value indicating that the corresponding index node is not used.

The various changes and specific examples in the foregoing file system management method in the foregoing embodiments of FIG. 2 to FIG. 5 are also applicable to the management apparatus of the present embodiment. The foregoing detailed description of the file system management method can be clearly understood by those skilled in the art. Knowing the implementation method of the management device in this embodiment, for the sake of brevity of the description, it will not be described in detail herein.

Based on the same inventive concept, with reference to FIG. 13 , a structural block diagram of an electronic device according to an embodiment of the present application is used to implement the file system management method shown in FIG. 2 to FIG. 5 of the present invention. For the meaning of the terms, please refer to the content described in the foregoing embodiments. The electronic device includes a processor 701, a transmitter 702, a receiver 703, a memory 704, and an input device 705. The processor 701 may be a general-purpose central processing unit (CPU), may be an application specific integrated circuit (ASIC), and may be one or more integrated circuits for controlling program execution. The number of memories 704 can be one or more. The memory 704 is, for example, a hard disk or a USB disk. These memories 704, receiver 703 and transmitter 702 are connected to the processor 701 via a bus. The receiver 703 and the transmitter 702 are configured to perform network communication with an external device, and specifically communicate with an external device through a network such as an Ethernet, a wireless access network, or a wireless local area network. Receiver 703 and transmitter 702 may be physically separate components or may be physically identical components. The input device 705 can be, for example, a keyboard, a mouse, or a touch pad.

Specifically, the processor 701 is configured to allocate a data block bitmap area to the file system on a first consecutive address segment of the memory 704; and to the file system on a second consecutive address segment of the memory 704. N partitions are allocated, each of the N partitions being used to store system metadata for each partition; N is an integer greater than 1; the file is on a third consecutive address segment of memory 704 The system allocates a shared data block area of the N partitions, the shared data block area is used to store a file; the data block bitmap area is used to store a first use identifier, and the first use identifier is used to indicate the Whether the data blocks in the shared data block area are used, each of the data blocks corresponding to one of the first use identifiers; wherein the first consecutive address segment, the second consecutive address segment, and the first Three consecutive address segments form a contiguous address segment.

Optionally, each partition includes an index node area and an index node bitmap area, where the index node of the index node area is used to record a storage address of a file stored in the shared data block area; the index node bitmap The area is used to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used; each of the index nodes corresponds to one of the second usage identifiers. The input device 705 is configured to receive a request for creating a file in an i-th partition of the N partitions; the request Included in the size of the file; the processor 701 is further configured to: determine, by using the first usage identifier, an unused data block in the shared data block area; according to the number and size of the unused data blocks Determining a size of the remaining capacity in the shared data block area; determining, according to the size of the file and the size of the remaining capacity, whether the remaining capacity is sufficient to create the file; when the remaining capacity is sufficient to create the file Determining whether the file is to be stored in a storage address in the shared data block area, and searching for an unused index node in an index node bitmap area of the i-th partition; when there is an unused When the node is indexed, one of the unused index nodes is selected, the attribute of the file and the storage address are written; and the corresponding location of the index node in the bitmap area corresponding to the one index node is Changing the second usage identifier to a value indicating that the one index node has been used; storing the file in the shared data block area corresponding to the storage address And the first usage identifier of the data block corresponding to the storage address in the data block bitmap is changed to a value indicating that the data block has been used.

Optionally, each partition includes an index node area and an index node bitmap area, where the index node of the index node area is used to record attributes of the file stored in the shared data block and a storage address; the index node bit The map area is configured to store a second usage identifier, where the second usage identifier is used to indicate whether the index node is used, and each of the index nodes corresponds to one of the second usage identifiers. The input device 705 is configured to receive a request for deleting a file by the partition j in the N partitions. The processor 701 is further configured to: search, according to an attribute of the file, a corresponding index node in an index node area of the partition j: determining, according to a storage address recorded by the index node, that the shared data block corresponds to the storage address Data block; changing the first usage identifier of the data block corresponding to the storage address in the data block bitmap area to a value indicating that the data block is not used; and indexing the partition j The second usage identifier of the corresponding index node in the bitmap area is changed to a value indicating that the corresponding index node is not used.

The various changes and specific examples in the foregoing file system management method in the foregoing embodiments of FIG. 2 to FIG. 5 are also applicable to the electronic device of the present embodiment. The foregoing detailed description of the file system management method can be clearly understood by those skilled in the art. The implementation method of the electronic device in this embodiment is known, so for the sake of brevity of the description, it will not be described in detail herein.

Based on the same inventive concept, with reference to FIG. 14 , a functional block diagram of another file system management apparatus provided by an embodiment of the present application is used to implement the file system management method shown in FIG. 6 to FIG. 7 b of the present invention. For the meaning of the terms involved in the examples, please refer to the contents described in the foregoing embodiments. The management device includes: a data block bitmap allocation module 801, configured to allocate a data block bitmap area for the file system on a first consecutive address segment of the storage device; and a metadata partition allocation module 802 for Assigning, to the file system, a first partition on a second consecutive address segment of the storage device, the first partition for storing system metadata of the first partition; and a third consecutive address of the storage device Assigning a second partition to the file system, the second partition is configured to store system metadata of the second partition, and the data block allocating module 803 is configured to be in a fourth consecutive address segment of the storage device. And allocating, for the file system, the shared data block area of the first partition and the second partition; wherein the shared data block area is used for storing a file; and the data block bitmap area is used for storing the first Using the identifier, the first usage identifier is used to indicate whether a data block in the shared data block area is used, and each of the data blocks corresponds to one of the first usage identifiers; the first consecutive address segment, The second consecutive address segment, the third consecutive address segment, and the fourth consecutive address segment form a contiguous address segment, and the fourth consecutive address segment is located at the second consecutive address segment and Between the third consecutive address segments.

Optionally, the first partition includes an index node area and an index node bitmap area, where the index node of the index node area is used to record attributes of the file stored in the shared data block and a storage address; the index node bit The mapping area is configured to store a second usage identifier, where the second usage identifier is used to indicate whether the index node is used; each of the index nodes corresponds to one of the second usage identifiers;

a processing module, configured to determine, by using the first usage identifier, an unused data block in the shared data block region; determining a remaining portion in the shared data block region according to the number and size of the unused data blocks a size of the capacity; determining, according to the size of the file and the size of the remaining capacity, whether the remaining capacity is sufficient to create the file; when the remaining capacity is sufficient to create the file Determining whether the file is to be stored in a storage address in the shared data block area, and searching for an unused index node in an index node bitmap area of the first partition; when there is an unused index a node, selecting one of the unused index nodes, writing an attribute of the file and the storage address; and referring to the index node in the index node corresponding to the one index node The second usage identifier is changed to a value indicating that the one index node has been used; the file is stored in a data block corresponding to the storage address in the shared data block area; and the data block bitmap is The first usage identifier of the data block corresponding to the storage address is changed to a value indicating that the data block has been used.

Optionally, the first partition includes an index node area and an index node bitmap area, where the index node of the index node area is used to record attributes of the file stored in the shared data block and a storage address; the index node bit The map area is configured to store a second usage identifier, where the second usage identifier is used to indicate whether the index node is used, and each of the index nodes corresponds to one of the second usage identifiers.

The device also includes:

a processing module, configured to search, according to an attribute of the file, a corresponding index node in an index node area of the first partition: determining, according to a storage address recorded by the index node, a corresponding to the storage address in the shared data block a data block; changing the first usage identifier of the data block corresponding to the storage address in the data block bitmap area to a value indicating that the data block is not used; and indexing the first partition The second usage identifier of the corresponding index node in the bitmap area is changed to a value indicating that the corresponding index node is not used.

The various changes and specific examples in the foregoing file system management method in the foregoing embodiments of FIG. 6 to FIG. 7b are also applicable to the management apparatus of the present embodiment. The foregoing detailed description of the file system management method can be clearly understood by those skilled in the art. Knowing the implementation method of the management device in this embodiment, for the sake of brevity of the description, it will not be described in detail herein.

Based on the same inventive concept, with reference to FIG. 15 , a structural block diagram of an electronic device according to an embodiment of the present application is used to implement the file system management method shown in FIG. 6 to FIG. 7 b of the present invention. For the meaning of the terms, please refer to the content described in the foregoing embodiments. The electronic device The processor 901, the transmitter 902, the receiver 903, the memory 904, and the input device 905 are included. The processor 901 may be a general-purpose central processing unit (CPU), may be an application specific integrated circuit (ASIC), and may be one or more integrated circuits for controlling program execution. The number of memories 904 can be one or more. The memory 904 is, for example, a hard disk as a USB flash drive. These memories 904, receiver 903 and transmitter 902 are connected to the processor 901 via a bus. The receiver 903 and the transmitter 902 are configured to perform network communication with an external device, and specifically communicate with an external device through a network such as an Ethernet, a wireless access network, or a wireless local area network. The receiver 903 and the transmitter 902 may be physically separate components or may be physically the same component. The input device 905 is, for example, a mouse, a keyboard, or a touch panel.

Specifically, the processor 901 is configured to allocate a data block bitmap area to the file system on a first consecutive address segment of the memory 904; and to the file system on a second consecutive address segment of the memory 904. Allocating a first partition for storing system metadata of the first partition; assigning a second partition to the file system on a third consecutive address segment of the memory 904, the second partition And storing the system metadata of the second partition; and sharing, on the fourth consecutive address segment of the memory 904, the shared data block area of the first partition and the second partition for the file system; The shared data block area is configured to store a file; the data block bitmap area is configured to store a first use identifier, and the first use identifier is used to indicate whether a data block in the shared data block area is used, and each The data block corresponds to one of the first usage identifiers; the first consecutive address segment, the second consecutive address segment, the third consecutive address segment, and the fourth consecutive address segment form a continuous the address of Between the fourth consecutive addresses in the second consecutive addresses and the third consecutive addresses.

Optionally, the first partition includes an index node area and an index node bitmap area, where the index node of the index node area is used to record attributes of the file stored in the shared data block and a storage address; the index node bit The map area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used; each of the index nodes corresponds to one of the second usage identifiers.

The input device 905 is configured to receive a request for creating a file in the first partition, where the request includes a size of the file, and the processor 901 is further configured to: determine, by using the first usage identifier, the shared number Determining an unused data block in the block area; determining a size of the remaining capacity in the shared data block area according to the number and size of the unused data blocks; according to the size of the file and the remaining capacity a size, determining whether the remaining capacity is sufficient to create the file; when the remaining capacity is sufficient to create the file, determining that the file is to be stored in a storage address in the shared data block area, and at the first The indexed index node of the partition finds whether there is an unused index node; when there is an unused index node, selects one of the unused index nodes, writes the attributes of the file and The storage address; changing the second usage identifier corresponding to the one index node in the bitmap node bitmap area to a value indicating that the one index node has been used; storing the file in the And a data block corresponding to the storage address in the shared data block area; changing the first use identifier of the data block corresponding to the storage address in the data block bitmap Value represents the data block has been used.

The input device 905 is configured to receive a request for deleting a file in the first partition; the processor 901 is further configured to: search, according to an attribute of the file, a corresponding index node in an index node area of the first partition: record according to the index node The storage address determines a data block corresponding to the storage address in the shared data block; changing the first use identifier of the data block corresponding to the storage address in the data block bitmap area to indicate the a value that the data block is not used; changing the second usage identifier of the corresponding index node in the index node bitmap area of the first partition to a value indicating that the corresponding index node is not used.

The various changes and specific examples in the foregoing file system management method in the foregoing embodiments of FIG. 6 to FIG. 7b are also applicable to the electronic device of the present embodiment. The foregoing detailed description of the file system management method can be clearly understood by those skilled in the art. The implementation method of the electronic device in this embodiment is known, so for the sake of brevity of the description, it will not be described in detail herein.

Based on the same inventive concept, referring to FIG. 16 , a file system provided by an embodiment of the present application is provided. The functional block diagram of the management device is used to implement the file system management method shown in FIG. 8 to FIG. 11 of the present invention. For the meanings of the terms involved in this embodiment, refer to the content described in the foregoing embodiments. The management device includes: a super block allocation module 1001, configured to allocate a super block area for the file system on a first consecutive address segment of the storage device, where the super block area is used to record system information of the file system; The system information includes a type and a size of the file system; the bitmap allocation module 1002 is configured to allocate a bitmap area to the file system on a second consecutive address segment of the storage device; the shared area allocation module 1003 And a shared area for the file system on a third consecutive address segment of the storage device, where the shared area is used for storing files and an index node; and the index node is used for recording and storing in the shared area. a storage address of the file; the bitmap area is configured to store a usage identifier, where the usage identifier is used to indicate whether a data block in the shared area is used, and each of the data blocks corresponds to one of the usage identifiers; The first consecutive address segment, the second consecutive address segment, and the third consecutive address segment form a contiguous address segment.

Optionally, the device further includes: a processing module, configured to allocate from the first address end to the second address end of the shared area when the shared area allocates space for the index node; When the shared area allocates space for the file, the shared area is allocated from the second address end of the shared area to the first address end.

Optionally, the device further includes:

a processing module, configured to determine, according to the usage identifier, an unused data block in the shared area; determining a size of a remaining capacity in the shared area according to the number and size of the unused data blocks; Determining a size of the file and a size of the remaining capacity to determine whether the remaining capacity is sufficient to create the file and storing an index node corresponding to the file; when the remaining capacity is sufficient to store the file and store an index corresponding to the file a node, creating the file on the unused data block and recording a storage address of the file in the corresponding index node; storing the bitmap area with the storage address and the The usage identifier of the data block corresponding to the index node is changed to a value indicating that the data block has been used.

Optionally, the processing module is further configured to: update a space size value occupied by all the index nodes stored in the shared area recorded in the super block, and a space occupied by all the files stored in the shared area Size value.

Optionally, the device further includes:

The various changes and specific examples in the foregoing file system management method in the foregoing embodiments of FIG. 8 to FIG. 11 are also applicable to the management apparatus of the present embodiment. The foregoing detailed description of the method for searching for a file can be clearly understood by those skilled in the art. Knowing the implementation method of the management device in this embodiment, for the sake of brevity of the description, it will not be described in detail herein.

Based on the same inventive concept, with reference to FIG. 17, a structural block diagram of an electronic device according to an embodiment of the present application is used to implement the file system management method shown in FIG. 8 to FIG. 11 of the present invention. For the meaning of the terms, please refer to the content described in the foregoing embodiments. The electronic device includes a processor 1201, a transmitter 1202, a receiver 1203, a memory 1204, and an input device 1205. The processor 1201 may be a general-purpose central processing unit (CPU), may be an application specific integrated circuit (ASIC), and may be one or more integrated circuits for controlling program execution. The number of memories 1204 can be one or more. The memory 1204 is, for example, a hard disk as a USB flash drive. These memories 1204, receivers 1203, and transmitters 1202 are coupled to the processor 1201 via a bus. The receiver 1203 and the transmitter 1202 are configured to perform network communication with an external device, and specifically communicate with an external device through a network such as an Ethernet, a wireless access network, or a wireless local area network. Receiver 1203 and transmitter 1202 may be physically separate components or may be physically identical components. The input device 1205 can be a mouse, a keyboard, or a touchpad.

Specifically, the processor 1201 is configured to allocate a super block area to the file system on a first consecutive address segment of the memory 1204, where the super block area is used to record system information of the file system; The system information includes a type and size of the file system; a bitmap area is allocated to the file system on a second consecutive address segment of the memory 1204; and the file is on a third consecutive address segment of the memory 1204. The system allocates a shared area for storing a file and an index node; the index node is configured to record a storage address of a file stored in the shared area; and the bitmap area is configured to store a usage identifier, Using an identifier for indicating whether a data block in the shared area is used, each of the data blocks corresponding to one of the usage identifiers; the first consecutive address segment, the second consecutive address segment, and the The third consecutive address segment constitutes a contiguous address segment.

Optionally, the processor 1201 is further configured to: when the shared area allocates space for the index node, allocate from a first address end to a second address end of the shared area; when in the sharing When the area allocates space for the file, the area is allocated from the second address end of the shared area to the first address end.

Optionally, the input device 1205 is configured to receive a request for creating a file, where the request includes a size of the file, and the processor 1201 is further configured to: determine, according to the usage identifier, that the shared area is not used. a data block; determining a size of the remaining capacity in the shared area according to the number and size of the unused data blocks; determining whether the remaining capacity is sufficient to create a location according to the size of the file and the size of the remaining capacity a file and an index node corresponding to the file; when the remaining capacity is sufficient to store the file and store an index node corresponding to the file, create the file on the unused data block and Recording a storage address of the file in the corresponding index node; changing a usage identifier of the data block corresponding to the storage address and the index node in the bitmap area to indicate that the data block has been used value.

Optionally, the processor 1201 is further configured to: update a space size value occupied by all the index nodes stored in the shared area recorded in the super block area, and all the file occupations stored in the shared area. The size of the space.

Optionally, the input device 1205 is configured to receive a request for querying a file, where the request includes an attribute of the file, and the processor 1201 is further configured to: query an index node corresponding to the attribute in the shared area; The storage address recorded in the corresponding index node searches for a file corresponding to the storage address in the shared area.

The various changes and specific examples in the foregoing file system management method in the foregoing embodiments of FIG. 8 to FIG. 11 are also applicable to the electronic device of the present embodiment. Those skilled in the art can clearly understand the foregoing detailed description of the method for searching for a file. The implementation method of the electronic device in this embodiment is known, so for the sake of brevity of the description, it will not be described in detail herein.

One or more technical solutions provided in the application embodiments have at least the following technical effects or advantages:

It will be apparent to those skilled in the art that various modifications and changes can be made in the present application without departing from the spirit and scope of the application. Thus, it is intended that the present invention cover the modifications and variations of the present invention.

Claims

A method for managing a file system, comprising:

Allocating a data block bitmap area to the file system on a first consecutive address segment of the storage device;

Allocating N partitions to the file system on a second consecutive address segment of the storage device, each partition of the N partitions respectively for storing system metadata of each partition; N is greater than 1 Integer

Allocating a shared data block area of the N partitions for the file system on a third consecutive address segment of the storage device, the shared data block area is for storing a file; the data block bitmap area is used for Storing a first usage identifier, where the first usage identifier is used to indicate whether a data block in the shared data block area is used, and each of the data blocks corresponds to one of the first usage identifiers; wherein the first The contiguous address segment, the second contiguous address segment, and the third contiguous address segment form a contiguous address segment.
The method according to claim 1, wherein each of the partitions includes an index node area and an index node bitmap area, and an index node of the index node area is used for recording in the shared data block area. a storage address of the file; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used; each of the index nodes corresponds to one of the second usage Identification

After the shared data block area of the N partitions is allocated to the file system on the third consecutive address segment of the storage device, the method further includes:

Receiving a request to create a file in an i-th partition of the N partitions; the request includes a size of the file;

Determining, by the first usage identifier, an unused data block in the shared data block area;

Determining a size of a remaining capacity in the shared data block area according to the number and size of the unused data blocks;

Determining whether the remaining capacity is sufficient according to the size of the file and the size of the remaining capacity Enough to create the file;

Determining, when the remaining capacity is sufficient to create the file, a storage address to be stored in the shared data block area, and searching for an unused portion in an index node bitmap area of the i-th partition Index node;

When there is an unused index node, selecting one of the unused index nodes, writing an attribute of the file and the storage address;

Changing the second usage identifier corresponding to the one index node in the bitmap node bitmap area to a value indicating that the one index node has been used;

Storing the file in a data block corresponding to the storage address in the shared data block area;

The first usage identifier of the data block corresponding to the storage address is changed in the data block bitmap to a value indicating that the data block has been used.
The method of claim 1 wherein said each partition comprises an index node area and an index node bitmap area, said index node area index node for recording files stored in said common data block The attribute and the storage address; the index node bitmap area is configured to store a second usage identifier, the second usage identifier is used to indicate whether the index node is used, and each of the index nodes corresponds to one of the second Use the logo,

After the shared data block area of the N partitions is allocated to the file system on the third consecutive address segment of the storage device, the method further includes:

Receiving a request to delete a file by the partition j in the N partitions;

Finding a corresponding index node in an index node area of the partition j according to an attribute of the file:

Determining, according to the storage address recorded by the index node, a data block corresponding to the storage address in the shared data block;

Changing the first usage identifier of the data block corresponding to the storage address in the data block bitmap area to a value indicating that the data block is not used;

Changing the second usage identifier of the corresponding index node in the index node bitmap area of the partition j to a value indicating that the corresponding index node is not used.
A method for managing a file system, comprising:

Allocating a data block bitmap area to the file system on a first consecutive address segment of the storage device;

Allocating, by the file system, a first partition on a second consecutive address segment of the storage device, where the first partition is configured to store system metadata of the first partition;

Allocating a second partition to the file system on a third consecutive address segment of the storage device, where the second partition is configured to store system metadata of the second partition;

Allocating a shared data block area of the first partition and the second partition to the file system on a fourth consecutive address segment of the storage device; wherein the shared data block area is used to store a file; The data block bitmap area is configured to store a first usage identifier, where the first usage identifier is used to indicate whether a data block in the shared data block area is used, and each of the data blocks corresponds to one of the first Using an identifier; the first consecutive address segment, the second consecutive address segment, the third consecutive address segment, and the fourth consecutive address segment form a contiguous address segment, the fourth consecutive The address segment is located between the second consecutive address segment and the third consecutive address segment.
The method of claim 4, wherein the first partition comprises an index node area and an index node bitmap area, and an index node of the index node area is used to record a file stored in the shared data block And an address of the storage node; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used; each of the index nodes corresponds to one of the second Use the logo;

After the allocating the shared data block area of the first partition and the second partition to the file system on the fourth consecutive address segment of the storage device, the method further includes:

Receiving a request to create a file in the first partition; the request includes a size of the file;

Determining, by the first usage identifier, an unused data block in the shared data block area;

Determining a size of a remaining capacity in the shared data block area according to the number and size of the unused data blocks;

Determining, according to the size of the file and the size of the remaining capacity, whether the remaining capacity is sufficient to create the file;

Determining that the file is to be stored in the total when the remaining capacity is sufficient to create the file Using the storage address in the data block area, and searching for an unused index node in the index node bitmap area of the first partition;

When there is an unused index node, selecting one of the unused index nodes, writing an attribute of the file and the storage address;

Changing the second usage identifier corresponding to the one index node in the bitmap node bitmap area to a value indicating that the one index node has been used;

Storing the file in a data block corresponding to the storage address in the shared data block area;

The first usage identifier of the data block corresponding to the storage address is changed in the data block bitmap to a value indicating that the data block has been used.
The method of claim 4, wherein the first partition comprises an index node area and an index node bitmap area, and an index node of the index node area is used to record a file stored in the shared data block The attribute and the storage address; the index node bitmap area is configured to store a second usage identifier, the second usage identifier is used to indicate whether the index node is used, and each of the index nodes corresponds to one of the second Use the logo,

After the allocating the shared data block area of the first partition and the second partition to the file system on the fourth consecutive address segment of the storage device, the method further includes:

Receiving a request to delete a file in the first partition;

Finding a corresponding index node in an index node area of the first partition according to an attribute of the file:

Determining, according to the storage address recorded by the index node, a data block corresponding to the storage address in the shared data block;

Changing the first usage identifier of the data block corresponding to the storage address in the data block bitmap area to a value indicating that the data block is not used;

Changing the second usage identifier of the corresponding index node in the index node bitmap area of the first partition to a value indicating that the corresponding index node is not used.
A method for managing a file system, comprising:

Allocating a superblock area to the file system on a first consecutive address segment of the storage device, The super block area is used to record system information of the file system; the system information includes a type and a size of the file system;

Allocating a bitmap area to the file system on a second consecutive address segment of the storage device;

Allocating a shared area to the file system on a third consecutive address segment of the storage device, the shared area is configured to store a file and an index node; and the index node is configured to record a file stored in the shared area a storage address; the bitmap area is configured to store a usage identifier, where the usage identifier is used to indicate whether a data block in the shared area is used, and each of the data blocks corresponds to one of the usage identifiers; A contiguous address segment, the second contiguous address segment, and the third contiguous address segment form a contiguous address segment.
The method of claim 7 wherein the method further comprises:

When the space is allocated to the index node in the shared area, the first address end of the shared area is allocated to the second address end;

When the space is allocated to the file in the shared area, the second address end of the shared area is allocated to the first address end.
The method of claim 7 or 8, wherein after the sharing of the shared area for the file system on the third consecutive address segment of the storage device, the method further comprises:

Receiving a request for creating a file; the request includes a size of the file;

Determining an unused data block in the shared area according to the usage identifier;

Determining a size of a remaining capacity in the shared area according to the number and size of the unused data blocks;

Determining, according to the size of the file and the size of the remaining capacity, whether the remaining capacity is sufficient to create the file and storing an index node corresponding to the file;

When the remaining capacity is sufficient to store the file and store an index node corresponding to the file, create the file on the unused data block and record a storage address of the file in the corresponding index In the node;

Changing the usage identifier of the data block corresponding to the storage address and the index node in the bitmap area to a value indicating that the data block has been used.
The method of claim 9 wherein the method further comprises:

And updating a space size value occupied by all the index nodes stored in the shared area recorded in the super block area and a space size value occupied by all the files stored in the shared area.
The method according to claim 7 or 8, wherein said index node further records attributes of the file,

After the shared area is allocated to the file system on the third consecutive address segment of the storage device, the method further includes:

Receiving a request for querying a file, the request including an attribute of the file;

Querying an index node corresponding to the attribute in the shared area;

Searching for a file corresponding to the storage address in the shared area according to a storage address recorded in the corresponding index node.
A file system management device, comprising:

a data block bitmap allocation module, configured to allocate a data block bitmap area to the file system on a first consecutive address segment of the storage device;

a metadata partition allocation module, configured to allocate N partitions to the file system on a second consecutive address segment of the storage device, where each partition of the N partitions is used to store each partition System metadata; N is an integer greater than one;

a data block allocation module, configured to allocate, to the file system, a common data block area of the N partitions on a third consecutive address segment of the storage device, where the shared data block area is used to store a file; The data block bitmap area is configured to store a first use identifier, where the first use identifier is used to indicate whether a data block in the shared data block area is used, and each of the data blocks corresponds to one of the first use identifiers Wherein the first consecutive address segment, the second consecutive address segment, and the third consecutive address segment form a contiguous address segment.
The apparatus according to claim 12, wherein each of the partitions includes an index node area and an index node bitmap area, and an index node of the index node area is used for recording in the shared data block area. a storage address of the file; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used; each of the indexes The node corresponds to one of the second usage identifiers; the device further includes:

a receiving module, configured to receive a request for creating a file in an i-th partition of the N partitions; the request includes a size of the file;

a processing module, configured to determine, by using the first usage identifier, an unused data block in the shared data block region; determining a remaining portion in the shared data block region according to the number and size of the unused data blocks a size of the capacity; determining, according to the size of the file and the size of the remaining capacity, whether the remaining capacity is sufficient to create the file; when the remaining capacity is sufficient to create the file, determining that the file is to be stored in the Determining a storage address in the shared data block area, and searching whether there is an unused index node in the index node bitmap area of the i-th partition; when there is an unused index node, selecting the unused An index node in the index node, writing an attribute of the file and the storage address; changing the second usage identifier corresponding to the one index node in the bitmap node bitmap area to indicate the a value that has been used by an index node; storing the file in a data block corresponding to the storage address in the shared data block area; The first usage identifier of the data block corresponding to the storage address is changed to a value indicating that the data block has been used.
The apparatus according to claim 12, wherein each of the partitions includes an index node area and an index node bitmap area, and an index node of the index node area is used to record a file stored in the shared data block The attribute and the storage address; the index node bitmap area is configured to store a second usage identifier, the second usage identifier is used to indicate whether the index node is used, and each of the index nodes corresponds to one of the second Using the identification, the device further includes:

a receiving module, configured to receive a request for deleting a file in the partition j in the N partitions;

a processing module, configured to search, according to an attribute of the file, a corresponding index node in an index node area of the partition j: determining, according to a storage address recorded by the index node, data corresponding to the storage address in the shared data block Blocking; changing the first usage identifier of the data block corresponding to the storage address in the data block bitmap area to a value indicating that the data block is not used; and using an index node bitmap of the partition j The second usage identifier of the corresponding index node in the zone is changed to a value indicating that the corresponding index node is not used.
A file system management device, comprising:

a data block bitmap allocation module, configured to allocate a data block bitmap area to the file system on a first consecutive address segment of the storage device;

a metadata partition allocation module, configured to allocate a first partition to the file system on a second consecutive address segment of the storage device, where the first partition is configured to store system metadata of the first partition; Assigning a second partition to the file system on a third consecutive address segment of the storage device, where the second partition is configured to store system metadata of the second partition;

a data block allocation module, configured to allocate a common data block area of the first partition and the second partition to the file system on a fourth consecutive address segment of the storage device; wherein the shared data The block area is configured to store a file; the data block bitmap area is configured to store a first use identifier, and the first use identifier is used to indicate whether a data block in the shared data block area is used, each of the data The block corresponds to one of the first usage identifiers; the first consecutive address segment, the second consecutive address segment, the third consecutive address segment, and the fourth consecutive address segment form a continuous address segment The fourth consecutive address segment is located between the second consecutive address segment and the third consecutive address segment.
The apparatus according to claim 15, wherein said first partition comprises an index node area and an index node bitmap area, and said index node area index node is for recording a file stored in said common data block And an address of the storage node; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used; each of the index nodes corresponds to one of the second The identification is used; the device further includes:

a receiving module, configured to receive a request for creating a file in the first partition; the request includes a size of the file;

a processing module, configured to determine, by using the first usage identifier, an unused data block in the shared data block region; determining a remaining portion in the shared data block region according to the number and size of the unused data blocks a size of the capacity; determining, according to the size of the file and the size of the remaining capacity, whether the remaining capacity is sufficient to create the file; when the remaining capacity is sufficient to create the file, determining that the file is to be stored in the a storage address in the shared data block area, and in the A partitioned index node bitmap area finds whether there is an unused index node; when there is an unused index node, selects one of the unused index nodes, and writes attributes of the file And the storage address; changing the second usage identifier corresponding to the one index node in the bitmap node bitmap area to a value indicating that the one index node has been used; storing the file in the location Determining, in the data block bitmap, the first use identifier of the data block corresponding to the storage address to indicate that the data block has been The value used.
The apparatus according to claim 15, wherein said first partition comprises an index node area and an index node bitmap area, and said index node area index node is for recording a file stored in said common data block The attribute and the storage address; the index node bitmap area is configured to store a second usage identifier, the second usage identifier is used to indicate whether the index node is used, and each of the index nodes corresponds to one of the second Use the logo,

The device also includes:

a receiving module, configured to receive a request to delete a file in the first partition;

a processing module, configured to search, according to an attribute of the file, a corresponding index node in an index node area of the first partition: determining, according to a storage address recorded by the index node, a corresponding to the storage address in the shared data block a data block; changing the first usage identifier of the data block corresponding to the storage address in the data block bitmap area to a value indicating that the data block is not used; and indexing the first partition The second usage identifier of the corresponding index node in the bitmap area is changed to a value indicating that the corresponding index node is not used.
A file system management device, comprising:

a super block allocation module, configured to allocate a super block area for the file system on a first consecutive address segment of the storage device, where the super block area is used to record system information of the file system; The type and size of the file system;

a bitmap allocation module, configured to allocate a bitmap area to the file system on a second consecutive address segment of the storage device;

a shared area allocation module, configured to be in the third consecutive address segment of the storage device The partition system is configured to store a file and an index node; the index node is configured to record a storage address of a file stored in the shared area; and the bitmap area is configured to store a usage identifier, The usage identifier is used to indicate whether a data block in the shared area is used, and each of the data blocks corresponds to one of the usage identifiers; the first consecutive address segment, the second consecutive address segment, and The third consecutive address segment constitutes a contiguous address segment.
The apparatus according to claim 18, wherein said apparatus further comprises: a processing module, configured to: when the space is allocated to said index node in said shared area, from said first address end of said shared area to said The second address end direction is allocated; when the space is allocated to the file in the shared area, the second address end of the shared area is allocated to the first address end direction.
The device of claim 18, wherein the device further comprises:

a receiving module, configured to receive a request for creating a file; the request includes a size of the file;

a processing module, configured to determine, according to the usage identifier, an unused data block in the shared area; determining a size of a remaining capacity in the shared area according to the number and size of the unused data blocks; Determining a size of the file and a size of the remaining capacity to determine whether the remaining capacity is sufficient to create the file and storing an index node corresponding to the file; when the remaining capacity is sufficient to store the file and store an index corresponding to the file a node, creating the file on the unused data block and recording a storage address of the file in the corresponding index node; storing the bitmap area with the storage address and the The usage identifier of the data block corresponding to the index node is changed to a value indicating that the data block has been used.
The device according to claim 20, wherein the processing module is further configured to: update a spatial size value occupied by all the index nodes stored in the shared area recorded in the super block, and the sharing The size of the space used by all of the files stored in the zone.
The device of claim 18, wherein the device further comprises:

a receiving module, configured to receive a request for querying a file, where the request includes an attribute of the file;

a processing module, configured to query an index node corresponding to the attribute in the shared area; and search for the storage address in the shared area according to a storage address recorded in the corresponding index node Corresponding file.
An electronic device, comprising:

Memory

a processor for allocating a data block bitmap area to the file system on a first consecutive address segment of the memory; assigning N to the file system on a second consecutive address segment of the memory a partition, each partition of the N partitions being used to store system metadata of each partition; N is an integer greater than 1; and the file system is allocated on a third consecutive address segment of the memory a shared data block area of the N partitions, where the shared data block area is used to store a file; the data block bitmap area is used to store a first use identifier, and the first use identifier is used to represent the shared data Whether the data blocks in the block area are used, each of the data blocks corresponding to one of the first usage identifiers; wherein the first consecutive address segment, the second consecutive address segment, and the third continuous The address segments form a contiguous address segment.
The electronic device according to claim 23, wherein each of the partitions includes an index node area and an index node bitmap area, and an index node of the index node area is used for recording in the shared data block area. a storage address of the file; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used; each of the index nodes corresponds to one of the second Using the identification, the electronic device further includes an input device,

The input device is configured to receive a request for creating a file in an i th partition of the N partitions; the request includes a size of the file;

The processor is further configured to: determine, by using the first usage identifier, an unused data block in the shared data block area; determine the shared data block area according to the number and size of the unused data blocks. a size of the remaining capacity; determining, according to the size of the file and the size of the remaining capacity, whether the remaining capacity is sufficient to create the file; when the remaining capacity is sufficient to create the file, determining that the file is to be Storing a storage address in the shared data block area, and searching for an unused index node in an index node bitmap area of the i-th partition; when there is an unused index node, selecting the An index node of an unused index node that writes an attribute of the file and the storage address; and the index node area of the index node and the one index section The second usage identifier corresponding to the point is changed to a value indicating that the one index node has been used; storing the file in a data block corresponding to the storage address in the shared data block area; The first usage identifier of the data block corresponding to the storage address is changed in the block bitmap to a value indicating that the data block has been used.
The electronic device according to claim 23, wherein each of the partitions includes an index node area and an index node bitmap area, and an index node of the index node area is used for recording in the shared data block. An attribute of the file and a storage address; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used, and each of the index nodes corresponds to one of the Second, using the identifier, the electronic device further includes an input device,

The input device is configured to receive a request for deleting a file by a partition j in the N partitions;

The processor is further configured to: search, according to an attribute of the file, a corresponding index node in an index node area of the partition j: determining, in the shared data block, the storage address according to a storage address recorded by the index node Corresponding data block; changing the first usage identifier of the data block corresponding to the storage address in the data block bitmap area to a value indicating that the data block is not used; indexing the partition j The second usage identifier of the corresponding index node in the node bitmap area is changed to a value indicating that the corresponding index node is not used.
An electronic device, comprising:

Memory

a processor for allocating a data block bitmap area to the file system on a first consecutive address segment of the memory; assigning a first to the file system on a second consecutive address segment of the memory a partition, the first partition is configured to store system metadata of the first partition; a second partition is allocated to the file system on a third consecutive address segment of the memory, the second partition is configured to store System metadata of the second partition; a shared data block region of the first partition and the second partition is allocated to the file system on a fourth consecutive address segment of the memory; wherein a shared data block area for storing a file; the data block bitmap area is for storing a first use identifier, and the first use identifier is used to indicate whether a data block in the shared data block area is used, each of the The data block corresponds to one of the first use identifiers; the first consecutive address segment, the second The consecutive address segments, the third consecutive address segment, and the fourth consecutive address segment form a contiguous address segment, the fourth consecutive address segment being located in the second consecutive address segment and the third Between consecutive address segments.
The electronic device according to claim 26, wherein the first partition comprises an index node area and an index node bitmap area, and the index node of the index node area is used for recording in the shared data block. An attribute of the file and a storage address; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used; each of the index nodes corresponds to one of the Second, using the identifier; the electronic device further includes an input device,

The input device is configured to receive a request for creating a file in the first partition; the request includes a size of the file;

The processor is further configured to: determine, by using the first usage identifier, an unused data block in the shared data block area; determine the shared data block area according to the number and size of the unused data blocks. a size of the remaining capacity; determining, according to the size of the file and the size of the remaining capacity, whether the remaining capacity is sufficient to create the file; when the remaining capacity is sufficient to create the file, determining that the file is to be Storing a storage address in the shared data block area, and searching for an unused index node in an index node bitmap area of the first partition; when there is an unused index node, selecting the un An index node of the used index node, writes an attribute of the file and the storage address; and changes the second use identifier corresponding to the one index node in the bitmap node bitmap area to a representation a value that the one index node has been used; storing the file in a data block corresponding to the storage address in the shared data block area; at the data block bit The address will be stored with the data block corresponding to a first change value using the identification data block has been used to represent the.
The electronic device according to claim 26, wherein the first partition comprises an index node area and an index node bitmap area, and the index node of the index node area is used for recording in the shared data block. An attribute of the file and a storage address; the index node bitmap area is configured to store a second usage identifier, and the second usage identifier is used to indicate whether the index node is used, and each of the index nodes corresponds to one of the Second, using the identifier, the electronic device further includes an input device,

The input device is configured to receive a request to delete a file in the first partition;

The processor is further configured to: search, according to an attribute of the file, a corresponding index node in an index node area of the first partition: determining, in the shared data block, the storage according to a storage address recorded by the index node a data block corresponding to the address; changing the first usage identifier of the data block corresponding to the storage address in the bitmap area of the data block to a value indicating that the data block is not used; The second usage identifier of the corresponding index node in the index node bitmap area is changed to a value indicating that the corresponding index node is not used.
An electronic device, comprising:

Memory

a processor, configured to allocate a super block area for the file system on a first consecutive address segment of the memory, the super block area for recording system information of the file system; a type, a size of a file system; a bitmap area is allocated to the file system on a second consecutive address segment of the memory; and a shared area is allocated to the file system on a third consecutive address segment of the memory, The shared area is configured to store a file and an index node; the index node is configured to record a storage address of a file stored in the shared area; the bitmap area is configured to store a use identifier, and the use identifier is used to represent Whether the data blocks in the shared area are used, each of the data blocks corresponding to one of the usage identifiers; the first consecutive address segment, the second consecutive address segment, and the third consecutive address Segments form a contiguous range of addresses.
The electronic device according to claim 29, wherein the processor is further configured to: when the space is allocated to the index node in the shared area, from the first address end to the second end of the shared area The address end direction is allocated; when the space is allocated to the file in the shared area, the second address end of the shared area is allocated to the first address end direction.
The electronic device according to claim 29, wherein said electronic device further comprises an input device,

The input device is configured to receive a request for creating a file; the request includes a size of the file;

The processor is further configured to: determine, according to the usage identifier, an unused number in the shared area Determining a size of the remaining capacity in the shared area according to the number and size of the unused data blocks; determining whether the remaining capacity is sufficient to create a location according to the size of the file and the size of the remaining capacity a file and an index node corresponding to the file; when the remaining capacity is sufficient to store the file and store an index node corresponding to the file, create the file on the unused data block and Recording a storage address of the file in the corresponding index node; changing a usage identifier of the data block corresponding to the storage address and the index node in the bitmap area to indicate that the data block has been used value.
The electronic device according to claim 31, wherein the processor is further configured to: update a space size value occupied by all the index nodes stored in the shared area recorded in the super block area, and The size of the space occupied by all the files stored in the shared area.
The electronic device according to claim 29, wherein said electronic device further comprises an input device,

The input device is configured to receive a request for querying a file, where the request includes an attribute of the file;

The processor is further configured to: query an index node corresponding to the attribute in the shared area; and search for a storage address corresponding to the storage address in the shared area according to a storage address recorded in the corresponding index node. file.