WO2016206070A1

WO2016206070A1 - File updating method and storage device

Info

Publication number: WO2016206070A1
Application number: PCT/CN2015/082442
Authority: WO
Inventors: 罗彩珠; 陈克平; 文刘飞
Original assignee: 华为技术有限公司
Priority date: 2015-06-26
Filing date: 2015-06-26
Publication date: 2016-12-29
Also published as: CN107430546A; CN107430546B

Abstract

The present invention relates to the field of file systems, and in particular, to a file updating method and a storage device. The method may comprise: receiving a file updating request, and writing second data into an allocated data block; determining a file block number of first data according to a first file offset; determining an index node of a first file according to a file identifier of the first file; recording, in a file updating table to which a first pointer in the index node of the first file points, a correspondence between the file block number of the first data and a logic block number of a data block for storing the second data, the logic block number being used for pointing to a physical address for storing the second data; and setting the state of the first data to invalid in a file state table to which a second pointer in the index node points. By means of the solution in the embodiments of the present invention, during data updating, because no content and no indirect block pointer in an index node need to be modified, modification of metadata during updating of file data of a file system can be reduced, thus improving the updating efficiency of the file data.

Description

File update method and storage device

Technical field

The present invention relates to the field of file systems, and in particular, to a file update method and a storage device.

Background technique

In the file system of the Linux operating system, each file contains file metadata and actual data. The file metadata includes file permissions (rxw) in Linux, file attributes (owner, group, time parameters, etc.) and save files. Data storage location. The file system usually stores the two pieces of data in different blocks, the permissions and attributes are placed in the index node, and the actual data is placed in the data block. There is also a super block that records the overall information of the entire file system. The index node records the attributes of the file. A file occupies an index node and records the location of the data block where the data of the file is located.

Since each index node and data block are numbered, and each file occupies an index node, the index node has a pointer to a logical block number of a data block for storing file data. Therefore, if the index node of the file can be found, then the logical block number of the data block storing the data can naturally be known, and the actual data of the file at the physical address can be read by the logical block number.

Existing file systems organize data blocks of files in a tree manner. When a file needs to be updated, a new data block is allocated according to the update data in the file to be updated, and the pointer of the old data block is pointed to the updated data block. Since the pointer is modified, the data block of the pointer is also stored. Must be updated. After a consistent set of updates is written to disk, the root block is automatically updated to point to the new tree, which contains the latest allocation information.

However, since each update operation is forced to be re-allocated, and the update data is updated, the pointer to the old data block needs to be pointed to the data block storing the update data, and the space overhead is large, and the metadata involved to be modified is relatively large and complicated. ,low efficiency.

Summary of the invention

The invention provides a file updating method, which can reduce the modification of the metadata when updating the file data of the file system, and has a simple method and can improve the update efficiency of the file data.

A first aspect of the embodiments of the present invention provides a file update method, which may include:

Receiving a file update request, where the file update request carries a file identifier of the first file, a first file offset, and second data, where the second data is used to update the first data in the first file; Allocating an idle data block to the second data according to a size of the second data;

Writing the second data into the allocated data block;

Determining, according to the first file offset, a file block number of the first data, where the file block number is used to identify a logical location of the first data;

Determining an index node of the first file according to the file identifier of the first file;

Corresponding relationship between a file block number of the first data and a logical block number of a data block storing the second data is recorded in a file update table pointed to by the first pointer in the index node of the first file, a logical block number is used to point to a physical address storing the second data;

Setting a state of the first data to be invalid in a file status table pointed to by the second pointer in the index node.

In conjunction with the first aspect, in a first possible implementation of the first aspect, the method may further include:

Receiving a file read request, where the file read request carries a file identifier of the second file and a second file offset;

Determining an index node of the second file according to the file identifier of the second file;

Determining, according to the second file offset, a file block number of the data to be read;

Determining, according to the file status table pointed by the second pointer in the index node of the second file, that the status of the data to be read is invalid;

Determining, according to the file update table pointed by the first pointer in the index node of the second file, a logical block number corresponding to the file block number of the data to be read;

Determining, according to a logical block number corresponding to the file block number of the data to be read, a physical address of the data to be read;

Reading the data to be read according to the physical address of the data to be read.

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

The update flag bit in the index node of the first file is set to have an update, and the update flag bit is used to determine an update status of the first file.

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

Before determining the state of the data to be read according to the file status table pointed to by the second pointer in the index node of the second file, the method further includes:

Determining that the second file has an update according to an update flag bit in the index node of the second file, the update flag bit is used to determine an update status of the second file.

The second aspect of the embodiment of the present invention further provides an apparatus, which may include:

a receiving module, configured to receive a file update request, where the file update request carries a file identifier of the first file, a first file offset, and second data, where the second data is used to update the first file First data;

An allocating module, configured to allocate an idle data block to the second data according to the size of the second data;

a writing module, configured to write the second data into the allocated data block;

a determining module, configured to determine, according to the first file offset, a file block number of the first data, where the file block number is used to identify a logical location of the first data;

And determining, according to the file identifier of the first file, an index node of the first file;

a recording module, configured to record, in a file update table pointed by the first pointer in the index node of the first file, a file block number of the first data and a logical block number of a data block storing the second data Corresponding relationship, the logical block number is used to point to a physical address storing the second data;

The state setting module sets the state of the first data to be invalid in a file state table pointed by the second pointer in the index node.

In conjunction with the second aspect, in a first possible implementation of the second aspect,

The receiving module is further configured to receive a file read request, where the file read request carries a file identifier of the second file and a second file offset;

The determining module is further configured to determine an index node of the second file according to the file identifier of the second file;

The storage device may further include:

a searching module, configured to determine, according to a file update table pointed by the first pointer in the index node of the second file, a logical block number corresponding to a file block number of the data to be read;

a reading module, configured to determine a physical address of the data to be read according to a logical block number corresponding to the file block number of the data to be read, and read the data to be read according to the physical address of the data to be read .

In conjunction with the second aspect, in a second possible implementation of the second aspect,

The status setting module is further configured to set an update flag bit in the index node of the first file to be updated, and the update flag bit is used to determine an update status of the first file.

In conjunction with the first possible implementation of the second aspect, in a third possible implementation of the second aspect,

The determining module is further configured to:

The third aspect of the embodiment of the present invention further provides a storage device, where the file system is established, and the storage device may include:

a memory for storing file data;

a controller, configured to receive a file update request, where the file update request carries a file identifier of the first file, a first file offset, and second data, where the second data is used for updating The first data in the file;

Allocating an idle data block to the second data according to a size of the second data in a memory;

Writing the second data into the allocated data block in the memory by caching;

Determining, according to the file offset, a file block number of the first data in the memory, where the file block number is used to identify a logical location of the first data;

Determining, according to the file identifier of the first file, an index node of the first file in the memory;

In conjunction with the third aspect, in a first possible implementation of the third aspect,

The controller is also used to:

In conjunction with the third aspect, in a second possible implementation manner of the third aspect, the controller is further configured to:

In conjunction with the first possible implementation of the third aspect, in a second possible implementation of the third aspect, the controller is further configured to:

Determining the second according to an update flag bit in an index node of the second file before determining a state of the data to be read according to a file state table pointed to by a second pointer in the index node of the second file The file has an update, and the update flag is used to determine an update status of the second file.

As can be seen from the above technical solutions, the embodiment of the present invention has the following advantages: the embodiment of the present invention has a first update pointer and a second pointer to the two tables in the index node because the file update table and the file state table are set. The update table stores the correspondence between the file block number of the file and the logical block number. When updating the data, the second data is first stored in the allocated free data block to determine the file block number of the first data, and then Determining an index node according to the first file, determining a file update table and a file status table, and then recording, in the file update table, a correspondence between a file block number of the first data and a logical block number of the data block storing the second data, It is possible to correspond to the new logical block number by the file block number, and After the status of the first data is set to invalid in the file status table, the data update operation can be completed. When the data is updated by the embodiment of the present invention, since it is not necessary to modify any content of the index node and any indirect block pointer, the metadata modification can be reduced when the file data of the file system is updated, and the copying and disk fragmentation of the data block can be reduced. And the method is simple, and the update efficiency of the file data can be improved.

DRAWINGS

1 is a schematic diagram of a storage system to which a file update method in an embodiment of the present invention is applied;

2 is a diagram showing a file system update state of a conventional copy-on-write technique;

FIG. 3 is a diagram of an embodiment of a file update method according to an embodiment of the present invention; FIG.

4 is a diagram showing another embodiment of a file updating method according to an embodiment of the present invention;

FIG. 5 is a diagram of another embodiment of a file update method according to an embodiment of the present invention; FIG.

FIG. 6 is a diagram of an embodiment of a storage device according to an embodiment of the present invention; FIG.

FIG. 7 is a diagram of another embodiment of a storage device according to an embodiment of the present invention; FIG.

FIG. 8 is a schematic structural diagram of a storage device according to an embodiment of the present invention;

Figure 9 is a diagram showing another embodiment of a storage device in an embodiment of the present invention.

detailed description

The embodiment of the invention provides a file updating method and a storage device, which are used to solve the problem that the metadata modified by the existing COW file system is more complicated and complicated, which leads to low efficiency and excessive disk fragmentation. The problem.

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is an embodiment of the invention, but not all of the embodiments.

The terms "first", "second", "third", "fourth", etc. (if present) in the specification and claims of the present invention and the above figures are used to distinguish similar objects without being used for Describe a specific order or order. It is to be understood that the data so used may be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than what is illustrated or described herein. In addition, the terms "comprises" and "comprises" and "comprises", and any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or device that comprises a series of steps or modules is not necessarily limited Those steps or modules listed are included, but may include other steps or modules not explicitly listed or inherent to such processes, methods, products or devices.

2 is a schematic structural diagram of a storage system according to an embodiment of the present invention. Referring to FIG. 1, the storage system is connected to a server 101 through a channel switch 102. The storage system includes at least one storage device 103. The channel switch 102 Each of the at least one storage device 103 is connected to the storage device 103. The file system module 1011 for managing the storage device is further disposed in the server 101. The system controls the storage device 103 through the file system module 1011 in the server 101 in cooperation with the channel switch 102, such as the file system module 1011 reading data from the storage device 103 through the Fibre Channel switch 102 or to the storage device. 103 stores data.

Those skilled in the art can know that the channel switch 102 can be a Fibre Channel switch or other channel switch capable of supporting a larger bandwidth, as long as there is sufficient bandwidth between the server 101 and the storage device 103 to transmit data.

A person skilled in the art can understand that, in addition to the storage system shown in FIG. 2, the embodiment of the present invention can also be applied to DAS Direct-Attached Storage, SAN Storage Area Network, and network connection. In the storage system of the type of the storage (NAS Network-Attached Storage), the application scenario of the embodiment of the present invention is not limited herein.

Of course, in addition to the aforementioned open array storage system, there are of course some non-array storage systems, such as a personal computer as a storage system.

Those skilled in the art will appreciate that when a system failure occurs in an operating system running in these storage systems, the file system therein must maintain consistency in order to function properly after the failure recovery. In order for the file system to achieve this effect, the prior art uses a copy-on-write technique for all data update operations, ie, constructing a new file system view on the storage device, and when all updates are safely written to disk, the new file system The view becomes valid. A file system using such a copy-on-write technique allocates a new block of data in an idle block (ie, an unused block) and writes the update data to the new data each time the data on the storage device is updated. Block, after the update data is successfully written, update the relevant metadata structure to point to the new data block.

The following describes the scenario of data update in the file system of the prior art. Please refer to FIG. 2. FIG. 2 is a file system update state diagram of a conventional copy-on-write technology. In the figure, point A is a file system tree. Root node, C node and E node are indexes pointing to the data block where the data in the file is located Node, when it is necessary to update the data block pointed to by the C node, the update data is written into the free new data block, and a new index node C' node is generated, and the C' node points to the new data block. Due to the copy-on-write technique, an idle data block is also allocated to the C' node, and since the A node needs to point to the C' node, the A node also needs to be modified. Similarly, due to the copy-on-write technique, this will occur. A new A' node points to the C' node, and the A' node also points to the E node. At this time, the file system allocates a new free data block for the A' node, and finally points the A node pointed to by the super block to point to A'. Node, complete the update of the data.

It should be noted that there may be an indirect Node B node between the A node and the C node, and the number of the B nodes may be more than one, such as having a B node and a D node at the same time, and the B node and the D node are at the same level. The B node points to the C node and the E node at the same time, and the D node points to the F node. The F node and the C node and the E node are both the index nodes pointing to the data block where the data in the file is located. At this time, when the data block pointed to by the C node needs to be performed, When updating, the A node does not directly point to the C node, but first points to the B node, and then the B node points to the C node. Therefore, when updating, it starts from the C node, first establishes the C' node, and then establishes the pointing to the C' node. The B' node, while the B' node points to the E node, and finally establishes the A' node pointing to the B' node, and the A' node points to the D node. Finally, the A node pointed to by the super block is changed to point to the A' node, and the data is completed. Update.

It can be seen that each modification of the user data will result in the copying and modification of a batch of related metadata blocks (such as C node, B node and A node). Due to the copy-on-write technology, the file system will not update the index node in situ (eg C nodes) and indirect pointers (such as Node B) must be copied and modified in a new location. And when submitting a superblock, the file system must force all blocks to be completely written to disk, which results in large delays, inefficiencies in the update operation, and invalid old blocks each time a new block of data needs to be allocated, which can result in a lot of disk fragmentation. .

In order to solve the above problem, a file update method is provided in the embodiment of the present invention, and the method can be applied to the application scenario shown in FIG. 1. Referring to FIG. 3, FIG. 3 is a schematic flowchart of a method for updating a file according to an embodiment of the present invention. The method may be executed by the server 101 in the storage system shown in FIG. 1 or by a file system module in a storage device. Can include the following:

301. Receive a file update request.

When data update is required, the data needs to be processed through the file system, and a file update request needs to be sent to the file system, and the file system receives such a text from other applications or systems. The file update request carries a file identifier of the first file, a first file offset, and second data, and the second data is used to update the first data in the file.

302. Allocate an idle data block to the second data according to the size of the second data.

After receiving the file update request, the file system allocates an idle data block for the second data according to the size of the second data to facilitate writing the second data.

303. Write the second data into the allocated data block.

After the free data block is allocated, the second data is written into the allocated data block.

304. Determine a file block number of the first data according to the file offset.

The file block number is used to identify the logical location of the first data, the file identifier can be used to determine the update file, and then the file block number of the first data can be obtained by the file offset.

When it is necessary to explain, the file block number is that the file is divided into several file blocks according to a fixed value of the preset file block size when storing, such as the first file here, and each file block is set to one. The file block number, and the first file offset is a specific value, which is used to determine the file block number corresponding to the first data to be updated, that is, when determining the file block number, only the corresponding first file offset needs to be known. The shift amount can be calculated by the first file offset and the preset fixed value.

For example, if the file population is taken as the X axis, the logical position corresponds to a specific point on the X axis, which is the starting point of the logical position, and the file block number corresponds to a segment of the line on the X axis, and the length of the line segment is The size of the file block; the first file offset is a specific point, and the file block number corresponding to the line segment is determined by judging the line segment in which the point falls.

305. Determine an index node of the first file according to the file identifier of the first file.

Since all the files stored on the disk have corresponding index nodes, the index node of the first file can be determined according to the file identifier of the first file.

306. Record a correspondence between a file block number of the first data and a logical block number of the data block storing the second data in a file update table pointed to by the first pointer in the index node of the first file.

A first pointer is set in the index node of the first file, the first pointer points to the file update table, and the first pointer in the index node can be determined according to the index node of the first file, so that the file update table can be determined, and the table is updated. The correspondence between the file block number of the file and the logical block number is stored.

After determining the update table, the file block number and storage of the first data can be recorded in the file update table. Corresponding relationship of the logical block numbers of the data blocks of the second data, so that the logical block numbers corresponding to the second data correspond to the file block numbers corresponding to the first data.

307. Set a state of the first data to be invalid in a file state table pointed to by the second pointer in the index node.

A second pointer is disposed in the index node of the first file, the second pointer points to the file state table, and the file state table is determined according to the second pointer, and the file state table stores a state for indicating validity of the data.

After determining the file status table, the status of the first data is set to invalid to indicate that the first data has been updated.

In the embodiment of the present invention, since the file update table and the file status table are set, the index node has a first pointer and a second pointer to the two tables, and the update table stores the file block number and the logical block number of the file. Correspondence relationship. When updating the data, the second data is first stored in the allocated free data block, the file block number of the first data is determined, and then the index node is determined according to the first file, and the file update table and the file status table are determined. The correspondence between the file block number of the first data and the logical block number of the data block storing the second data is recorded in the file update table, so that the file block number corresponds to the new logical block number, and then the file status is achieved. In the table, the status of the first data is set to be invalid, and the data update operation can be completed. When the data is updated by the embodiment of the present invention, since it is not necessary to modify any content of the index node and any indirect block pointer, the modification of the metadata can be reduced when the file data of the file system is updated, and the method is simple, and the file data can be improved. The update efficiency, and can reduce the copy of the data block and disk fragmentation, and ultimately achieve the purpose of improving the efficiency of the update operation.

In the embodiment of the present invention, since the file update table and the file status table are set, after the update flag bit is set, the update flag bit can be used to quickly identify whether the file corresponding to the index node is updated. It should be noted that the setting mode of the state in the file state table is more important, which directly affects whether the file system can quickly find the state of locating the first data. One of the setting modes is described below, which can improve the efficiency of the first data of the file system. .

Optionally, when the file is stored for the first time, the file status table in which the status of each data is recorded is arranged in the order of the file block number. Since the file block number is determined when the file is stored, the file block number is not determined. The corresponding logical block number is changed, so that the state of the data can be quickly obtained after the file block number of the data is known, and the state of the data is arranged in the order of the file block number, and the number can be known. According to the file block number, the state of quickly finding the data is beneficial to improve the efficiency of file update. For the first data, the efficiency of the file system setting the state corresponding to the first data can be improved, thereby improving the efficiency of file update. .

For example, in the file state table, the state of the data arranged in the order of the file block number is adopted, and when the second data is substituted for the first data and the state needs to be set to be invalid, the file of the first data is first passed. The block number looks up the state of the first data corresponding to the file block number in the file status table, and then sets the state of the first data to be invalid.

It should be noted that, in the embodiment of the present invention, an update flag bit may also be set in the index node to indicate that the data corresponding to the index node is updated; please refer to FIG. 4, which is another implementation of the file update method in the embodiment of the present invention. As shown in FIG. 4, in addition to the file update method shown in FIG. 3, steps 401 to 407 are similar to steps 301 to 307, and the file update method further includes

408. Set an update flag bit in an index node of the first file to be updated.

The update flag is used to determine the update status of the first file.

It can be understood that after the update flag is set, after the index node is determined, the update flag can be used to quickly identify whether the file corresponding to the index node is updated, although the identifier of the data in the file status table can be known. Whether there is data update, but there are two disadvantages. One is that the file status table needs to be determined by the second pointer in the index node of the first file, and the invalid identifier in the file status table is determined. Therefore, in the manner of the foregoing step 408, it is possible to directly learn from the index node of the first file whether the file corresponding to the index node is updated, and it is not necessary to determine the file state table by using the second pointer, thereby greatly improving the execution efficiency of the file system update. .

It should be noted that, after the file is updated, when the application or the operating system needs to read the file, the file system will read the file.

FIG. 5 is a schematic diagram of another embodiment of a method for updating a file according to an embodiment of the present invention. The method for reading data in the method for updating a file according to an embodiment of the present invention is as shown in FIG. 5 , and the update method in this embodiment may also be used. include:

501. Receive a file read request.

The file read request carries the file identifier of the second file and the second file offset. When the application or the operating system needs to read the file, the file read request is sent to the file system.

502. Determine an index node of the second file according to the file identifier of the second file.

After receiving the file read request, the index node corresponding to the second file is first determined according to the second file, so as to query the actual storage location of the data to be read according to the index node.

503. Determine a file block number of the data to be read according to the second file offset.

After determining the second file, the file block number of the data to be read can be determined by the second file offset for subsequent use.

504. Determine, according to the file status table pointed by the second pointer in the index node of the second file, that the status of the data to be read is invalid.

After the file status table is determined by the second pointer of the index node, the status of the data to be read in the file status table is determined. When it is determined that the status of the data to be read is invalid, the subsequent steps are performed.

505. Determine, according to the file update table pointed to by the first pointer in the index node of the second file, a logical block number corresponding to the file block number of the data to be read.

When it is determined that the state corresponding to the data to be read is invalid, the file update table is determined according to the first pointer of the index node, and then the logical block number corresponding to the file block number of the data to be read is determined by the file update table.

506. Determine a physical address of the data to be read according to a logical block number corresponding to the file block number of the data to be read.

After obtaining the logical block number of the data to be read, the physical address of the actual storage location of the data to be read may be determined according to the correspondence between the logical block number and the physical address.

507. Read data to be read according to a physical address of the data to be read.

After the physical address is obtained, the data stored in the physical disk can be read from the physical address, and the data reading process is completed.

It should be noted that, when actually reading data, it is necessary to first determine whether the data to be read is updated data, that is, whether the state of the data to be read is invalid, and determining the file block by using the index node of the second file. a chart, and determining a state of the data to be read therein, such as an invalid identifier, indicating that the data corresponding to the state is erroneous data through the existing read, and at this time, the file update table is determined by the index node of the second file, Find the location of the file block number corresponding to the data to be read in the file update table, and then find the updated logical block number of the data to be read, and read the physical disk to be read by the physical address corresponding to the logical block number. Data is taken, and the data is first read when reading by the solution of the embodiment of the present invention. The judgment is made, and then the subsequent reading operation is performed according to the judgment result. Since the data storage location on the index node is not directly read, when the reading is performed, the data reading error does not occur, and the reading table is read by reading. The logic block number reads the manner of the data to be read, further increasing the achievability of the file update method of the embodiment of the present invention.

Since the file update table and the file status table are set, and since the index node has the first pointer and the second pointer pointing to the two tables, when reading the data to be read, for the two types of data to be read, That is, the updated data and the unupdated data are different in reading manner, that is, when determining that the state of the data to be read is invalid and non-invalid, there are two different ways:

If the data to be read is the updated data, the data is read in the manner shown in steps 501 to 507 above. If the data to be read is unupdated data, the third pointer in the index node is pointed. The data block position reads the data to be read.

That is, if the state of the data to be read is not invalid, the file system reads the data by searching for the third pointer in the index node corresponding to the data to be read, and reading the data block position pointed by the third pointer. The data to be read.

It can be understood that, since it is determined that the data to be read is not invalid when it is determined that the data to be read is not updated, the data block position pointed by the third pointer in the index node can be read and read. data.

It should be noted that, in the case that the state of the data to be read is not invalid, the update table is first determined by the index node, and then the logical block number corresponding to the file block number of the data to be read is searched from the update table, and then passed. The logical block number reads the data to be read on the physical block corresponding to the logical block number, and the two reading modes can be arbitrarily set to one of them.

Optionally, in step 504, the data processing method may further include: before determining, according to the file state table pointed by the second pointer in the index node of the second file, the data processing method:

Determining that the second file is updated according to the update flag bit in the index node of the second file;

The update flag is used to determine an update status of the second file, and when it is determined that there is an update, triggering the second pointer of the index node according to the second file to determine the file status table.

It can be understood that the purpose of setting this update flag bit is to know whether the data corresponding to the index node is updated only by reading the index node, without first reading the file status table, and then searching the file status table. The state of the data to be read corresponding to the file block number of the data to be read, This state determines whether there is an update, thereby saving data reading time and improving data reading efficiency.

Optionally, the data processing method may further include: in step 504, before determining the state of the data to be read according to the file state table pointed by the second pointer in the index node of the second file, the data processing method may further include:

The second file is determined to be non-updated according to the update flag bit in the index node of the second file.

When it is determined that the update flag is no update, the data pointer pointing to the actual location of the data in the index node of the second file is directly acquired, and the data to be read on the physical address is read by the pointer.

Wherein, when reading the data to be read, if the index node of the second file corresponds to more data, the data pointer can also be used as the intermediate pointer to point to the actual pointer, and then the actual pointer points to the actual data to be read. .

It should be noted that, when it is determined that the update flag is no update, the data to be read may also be read in the manner of steps 504 to 507, and the selection may be performed according to the requirement of the read data.

The foregoing describes the implementation of the file update method in the embodiment of the present invention. The following describes the storage device in the embodiment of the present invention. Referring to FIG. 6, FIG. 6 is an embodiment of the storage device in the embodiment of the present invention, and FIG. 6 provides A storage device can include:

The receiving module 601 is configured to receive a file update request, where the file update request carries a file identifier of the first file, a first file offset, and second data, where the second data is used to update the first data in the first file;

The allocating module 602 is configured to allocate idle data blocks to the second data according to the size of the second data;

a writing module 603, configured to write the second data into the allocated data block;

a determining module 604, configured to determine a file block number of the first data according to the first file offset, where the file block number is used to identify a logical position of the first data;

a recording module 605, configured to record, in a file update table pointed by the first pointer in the index node of the first file, a correspondence between a file block number of the first data and a logical block number of the data block storing the second data, the logic block The number is used to point to the physical address where the second data is stored;

The state setting module 606 sets the state of the first data to be invalid in the file state table pointed to by the second pointer in the index node.

In the storage device of the embodiment of the present invention, since the file update table and the file state table are set, the index node has a first pointer and a second pointer pointing to the two tables, and the update table stores the file with the file. Corresponding relationship between the block number and the logical block number. When the data update request is received by the first receiving module 601, the second data is first stored in the allocated idle memory by the assigning module 602 through the writing module 603. In the data block, the file block number of the first data is determined by the determining module 604, and then the index node determines the file update table and the file status table according to the first file, and the first data is recorded in the file update table by the recording module 605. Corresponding relationship between the file block number and the logical block number of the data block storing the second data, so that the file block number corresponds to the new logical block number, and then the first data is set in the file status table by the state setting module 606. The status is set to invalid, and the data update operation can be completed. When the data is updated by the embodiment of the present invention, since it is not necessary to modify any content of the index node and any indirect block pointer, the modification of the metadata can be reduced when the file data of the file system is updated, and the method is simple, and the file data can be improved. Update efficiency. And it can reduce the copy of the data block and disk fragmentation, and finally achieve the purpose of improving the efficiency of the update operation.

Among them, it needs to be explained that

When the file is stored for the first time, the file status table in which the status of each data is recorded is arranged in the order of the file block number. Since the file block number is determined when the file is stored, the logical block number corresponding to the file block number is not used. The change is changed, so that the state of the data can be quickly obtained after knowing the file block number of the data. By arranging the state of the data in the order of the file block number, it is possible to quickly find the state of the data in the case of knowing the file block number of the data, which is advantageous for improving the efficiency of file update. For the first data, the efficiency of the file system setting the state corresponding to the first data can be improved, thereby improving the efficiency of file update.

Optionally, on the basis of the storage device shown in FIG. 6, the state setting module 606 is further configured to set the update flag bit in the index node of the first file to be updated.

The update flag is used to determine the update status of the first file.

It can be seen that the purpose of the state setting module 606 is to quickly identify whether the file corresponding to the index node is updated by using the update flag, although the status in the file status table can also be used to know whether there is data update, but the disadvantages are Two points, one of which is to determine the file status table through the second pointer in the index node of the first file, and determine the invalid identifier in the file status table. Therefore, the state setting module 606 can directly learn whether the file corresponding to the index node has an update from the index node of the first file, and does not need to determine the file state table by using the second pointer, thereby greatly improving the execution efficiency of the file system update.

It should be noted that the storage device in the embodiment of the present invention is not only convenient for writing data, but also can be quickly and accurately read when reading data, as shown in FIG. 7, FIG. 7 is stored in the embodiment of the present invention. Another embodiment of the device, as shown in FIG. 7, provides a storage device for reading data, wherein

The receiving module 701 is further configured to receive a file read request, where the file read request carries a file identifier of the second file and a second file offset;

The determining module 704 is further configured to determine an index node of the second file according to the file identifier of the second file; determine a file block number of the data to be read according to the second file offset; and use a second one of the index nodes according to the second file The file status table pointed to by the pointer determines that the status of the data to be read is invalid;

The storage device also includes:

The searching module 707 is configured to determine, according to the file update table pointed to by the first pointer in the index node of the second file, a logical block number corresponding to the file block number of the data to be read;

The reading module 708 is configured to determine a physical address of the data to be read according to the logical block number corresponding to the file block number of the data to be read, and read the data to be read according to the physical address of the data to be read.

When the storage device in the embodiment of the present invention actually reads data, the receiving module 704 first receives the file reading request, and then the determining module 704 determines the index node of the second file according to the file identifier of the second file. Then, the determining module 704 determines the file block number of the data to be read according to the second file offset. Before reading the data to be read, it is necessary to determine whether the data to be read is updated data, that is, to determine the pending reading. Whether the state of the data is invalid, the determining module 704 determines the file block text chart according to the index node of the second file, and determines the state of the data to be read therein, and if it is invalid, it indicates that the data corresponding to the state passes the current state. If the erroneous data is read, the search module 707 determines the file update table according to the index node of the second file, and finds the location of the file block number corresponding to the data to be read in the file update table, thereby finding the to-be-read. Taking the updated logical block number of the data, and then the reading module 708 determines the physicality of the data to be read according to the logical block number corresponding to the file block number of the data to be read. Address, and reads data to be read on a physical disk to the physical address corresponding to this logical block number.

It can be seen that, by using the solution of the embodiment of the present invention, the read data is first determined during reading, and then the subsequent read operation is performed according to the judgment result, since the data storage location on the index node is not directly read, so the read is performed. When the data reading error does not occur, and the manner of reading the data to be read by reading the logical block number in the update table, the file updating method of the embodiment of the present invention is further increased. The achievability.

It should be noted that, in the storage device shown in FIG. 7,

The determining module 704 is further configured to determine that the second file is updated according to the update flag bit in the index node of the second file.

The update flag is used to determine the update status of the second file. When the determination module 704 determines that there is an update, the determination module 704 determines the file status table according to the second pointer of the index node of the second file.

It can be understood that the purpose of setting this update flag bit is to know whether the data corresponding to the index node is updated only by reading the index node, without first reading the file status table, and then searching the file status table. In the state of the data to be read corresponding to the file block number of the data to be read, it is judged whether there is an update by the state, thereby saving data reading time and improving data reading efficiency.

The storage device in the embodiment of the present invention is described above. The following describes another storage device in the embodiment of the present invention. As shown in FIG. 8, FIG. 8 is a schematic structural diagram of a storage device according to an embodiment of the present invention. A file system is established in the device, and the storage device 8 includes:

a memory 801, configured to store file data;

The controller 802 is connected to the memory, and is configured to receive a file update request, where the file update request carries a file identifier of the first file, a first file offset, and second data, where the second data is used to update the file. First data;

Allocating an idle data block to the second data according to the size of the second data in the memory;

Writing the second data into the allocated data block in the memory through the cache;

Determining, according to the file offset, a file block number of the first data in the memory, the file block number being used to identify a logical location of the first data;

Determining an index node of the first file in the memory according to the file identifier of the first file;

Corresponding relationship between a file block number of the first data and a logical block number of the data block storing the second data is recorded in the file update table pointed to by the first pointer in the index node of the first file, and the logical block number is used to point to the storage The physical address of the second data;

The state of the first data is set to be invalid in the file state table pointed to by the second pointer in the index node.

The memory 801 is used to store file data. When updating data, the controller 802 firstly The second data is stored in the allocated free data block, and the file block number of the first data is determined, and then the controller 802 determines the index node according to the first file, determines the file update table and the file status table, and then the controller 802 is in the file. The correspondence between the file block number of the first data and the logical block number of the data block storing the second data is recorded in the update table, so that the file block number corresponds to the new logical block number, and then the controller 802 is in the file. In the state table, the state of the first data is set to be invalid, and the data update operation is completed. When the data is updated by the solution of the embodiment of the present invention, since the content of the index node and any indirect block pointers do not need to be modified, the data block is reduced. The copy and disk fragmentation ultimately achieve the purpose of improving the efficiency of the update operation.

It should be noted that, in addition to the foregoing operations of performing data update, the controller 802 may also perform a data reading operation, wherein the controller 802 may also perform the following operations:

Determining a file block number of the data to be read according to the second file offset;

Determining, according to the file update table pointed to by the first pointer in the index node of the second file, a logical block number corresponding to the file block number of the data to be read;

Determining a physical address of the data to be read according to a logical block number corresponding to a file block number of the data to be read;

The data to be read is read according to the physical address of the data to be read.

It can be understood that, when the storage device 8 in the embodiment of the present invention actually reads data, the file read request is first received by the controller 802, and then the controller 802 determines the second file according to the file identifier of the second file. The index node of the file, and then the controller 802 determines the file block number of the data to be read according to the second file offset. Before reading the data to be read, it is necessary to determine whether the data to be read is updated. Data, that is, determining whether the state of the data to be read is invalid, may be determined by the controller 802 according to the index node of the second file, and determining the state of the data to be read therein, if it is invalid, indicating The data corresponding to the status is erroneous data read by the existing one. At this time, the controller 802 determines the file update table according to the index node of the second file, and finds the position of the file block number corresponding to the data to be read in the file update table. And then find the updated logical block of the data to be read. And then the controller 802 determines the physical address of the data to be read according to the logical block number corresponding to the file block number of the data to be read, and the controller 802 reads the physical address on the physical disk through the physical address corresponding to the logical block number. The data to be read.

It should be noted that, in addition to the foregoing operations of performing data update and data reading, the controller 802 is further configured to:

It can be seen that the controller 802 can quickly identify whether the file corresponding to the index node is updated by using the update flag bit. Although the status of the data in the file status table can be used to know whether there is data update, there are two disadvantages. One is that the file status table needs to be determined by the second pointer in the index node of the first file, and the invalid identifier in the file status table is determined. Therefore, if the controller 802 can directly learn from the index node of the first file whether the file corresponding to the index node has an update, and does not need to determine the file state table by using the second pointer, the execution efficiency of the file system update is greatly improved.

Before determining the state of the data to be read according to the file state table pointed to by the second pointer in the index node of the second file, determining that the second file is updated according to the update flag bit in the index node of the second file, and updating the flag bit Determine the update status of the second file.

It can be seen that, before the file status table determines the status of the data to be read, the controller 802 determines that the second file is updated according to the update flag bit in the index node of the second file, and the update flag is used to determine the second file. update status. Therefore, if this step is used to update the update flag, it indicates that the second file has been updated. The existing read mode may not read the data to be read. Therefore, it is necessary to first go to the file status table to determine the pending read. The state of the data is fetched, and then the manner in which the data to be read is read is determined, thereby improving the execution efficiency of the file system update.

Optionally, a communication interface and a cache are further disposed in the storage device 8 in the embodiment of the present invention, where: the communication interface 803 is configured to allow the storage device to communicate with the external device;

The cache 804 is used for data interaction between the controller and the memory, and the cache is set between the controller and the storage.

The communication interface 803 is connected to the controller 802, and is used for the storage device and the external device. The line communication may be a physical wired interface such as an Ethernet interface or a fiber interface, or may be a wireless interface, which is determined by a specific application scenario of the storage device, and is not limited.

The cache 804 serves as a buffer between the memory 801 and the controller 802. Since the rate of the file data of the controller 802 is much larger than the read data of the memory 801, the cache 804 is read between the memory 801 and the controller 802, and the cache 804 is read. The rate at which the data is fetched is much larger than the memory 801, and is smaller than the rate at which the controller 802 reads the data. Therefore, by setting the buffer 804, the data that needs to be operated is read from the memory 801 into the cache 804 in advance, and then The controller 801 operates to greatly improve the reading efficiency of the data, thereby improving the operating efficiency of the storage device.

It should be noted that, in addition to the manner in which the plurality of memories 801 share one cache 804, the manner shown in FIG. 9 may be adopted, and FIG. 9 is in the embodiment of the present invention. Another embodiment of a storage device in which each memory 901 in storage device 9 uses a cache 904, respectively, and all caches 904 are then coupled to controller 902.

It should be noted that whether a single cache 904 or multiple caches 904 are used, the purpose is to serve as a buffer between the controller and the memory. When the memory 901 is very large, a cache 904 is preferably configured for each of the memories 901. When the number of the memory 904 is not large, a large buffer may be configured for the plurality of memories 904. Of course, the specific settings may be set according to other conditions, such as the rate of the buffer 904 and the controller 902 respectively. That is, the ratio of the memory 901.

In addition, the cache 904 can be a level one cache 904, or a multi-level cache 904 can be employed, wherein the closer to the cache 904 of the controller 902, the higher the rate at which data is accessed.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

The embodiment of the invention further provides a computer program product for data processing, comprising a computer readable storage medium storing program code, the program code comprising instructions for executing the method flow described in any one of the foregoing method embodiments. A person skilled in the art can understand that the foregoing storage medium includes: a USB flash drive, a mobile hard disk, a magnetic disk, an optical disk, a random access memory (RAM), a solid state disk (SSD), or a nonvolatile. A non-transitory machine readable medium that can store program code, such as a non-volatile memory.

It should be noted that the embodiments provided in the present application are merely illustrative. For example, the division of each component in the above embodiment may have another division manner in actual implementation. For example, multiple modules or components may be combined or integrated into another device, or some features may be omitted or not performed. In addition, the coupling or direct coupling or communication connection of the components shown or discussed may be through some communication interface, indirect coupling or communication connection of the modules, and may include electrical, mechanical, or other forms of connection.

It will be apparent to those skilled in the art that, for the convenience and brevity of the description, in the above embodiments, the description of each embodiment has its own emphasis, and the parts which are not described in detail in a certain embodiment can be referred to other implementations. A description of the example. Features disclosed in the embodiments of the invention, the claims, and the drawings may exist independently or in combination. Features described in hardware in the embodiments of the present invention may be implemented by software, and vice versa. There is no limit here.

Claims

A method for updating a file, the method being applied to a storage device having a file system, comprising:

Receiving a file update request, where the file update request carries a file identifier of the first file, a first file offset, and second data, where the second data is used to update the first data in the first file; Allocating an idle data block to the second data according to a size of the second data;

Writing the second data into the allocated data block;

Determining, according to the first file offset, a file block number of the first data, where the file block number is used to identify a logical location of the first data;

Determining an index node of the first file according to the file identifier of the first file;

Corresponding relationship between a file block number of the first data and a logical block number of a data block storing the second data is recorded in a file update table pointed to by the first pointer in the index node of the first file, a logical block number is used to point to a physical address storing the second data;

Setting a state of the first data to be invalid in a file status table pointed to by the second pointer in the index node.
The method for updating a file according to claim 1, wherein the method further comprises:

Receiving a file read request, where the file read request carries a file identifier of the second file and a second file offset;

Determining an index node of the second file according to the file identifier of the second file;

Determining, according to the second file offset, a file block number of the data to be read;

Determining, according to the file status table pointed by the second pointer in the index node of the second file, that the status of the data to be read is invalid;

Determining, according to the file update table pointed by the first pointer in the index node of the second file, a logical block number corresponding to the file block number of the data to be read;

Determining, according to a logical block number corresponding to the file block number of the data to be read, a physical address of the data to be read;

Reading the data to be read according to the physical address of the data to be read.
The method for updating a file according to claim 1, wherein the method further comprises:

Setting an update flag bit in the index node of the first file to have an update, the update flag The bit is used to determine an update status of the first file.
The file updating method according to claim 2, wherein the method determines the state of the data to be read according to a file state table pointed to by a second pointer in the index node of the second file Also includes:

Determining that the second file has an update according to an update flag bit in the index node of the second file, the update flag bit is used to determine an update status of the second file.
A storage device, comprising:

a receiving module, configured to receive a file update request, where the file update request carries a file identifier of the first file, a first file offset, and second data, where the second data is used to update the first file First data;

An allocating module, configured to allocate an idle data block to the second data according to the size of the second data;

a writing module, configured to write the second data into the allocated data block;

a determining module, configured to determine, according to the first file offset, a file block number of the first data, where the file block number is used to identify a logical location of the first data, and according to the first file The file identifier determines an index node of the first file;

a recording module, configured to record, in a file update table pointed by the first pointer in the index node of the first file, a file block number of the first data and a logical block number of a data block storing the second data Corresponding relationship, the logical block number is used to point to a physical address storing the second data;

The state setting module sets the state of the first data to be invalid in a file state table pointed by the second pointer in the index node.
A storage device according to claim 5, wherein:

The receiving module is further configured to receive a file read request, where the file read request carries a file identifier of the second file and a second file offset;

The determining module is further configured to determine an index node of the second file according to the file identifier of the second file, and determine a file block number of the data to be read according to the second file offset, according to the a file status table pointed to by the second pointer in the index node of the second file determines that the state of the data to be read is invalid;

The storage device further includes:

a searching module, configured to determine, according to a file update table pointed by the first pointer in the index node of the second file, a logical block number corresponding to a file block number of the data to be read;

a reading module, configured to determine a physical address of the data to be read according to a logical block number corresponding to the file block number of the data to be read, and read the data to be read according to the physical address of the data to be read .
A storage device according to claim 5, wherein:

The status setting module is further configured to set an update flag bit in the index node of the first file to be updated, and the update flag bit is used to determine an update status of the first file.
The storage device according to claim 6, wherein the determining module is further configured to:

Determining that the second file has an update according to an update flag bit in the index node of the second file, the update flag bit is used to determine an update status of the second file.
A storage device is characterized in that: a file system is established in the storage device, and the storage device includes:

a memory for storing file data;

a controller, configured to receive a file update request, where the file update request carries a file identifier of the first file, a first file offset, and second data, where the second data is used for updating The first data in the file;

Allocating an idle data block to the second data according to a size of the second data in a memory;

Writing the second data into the allocated data block in the memory by caching;

Determining, according to the file offset, a file block number of the first data in the memory, where the file block number is used to identify a logical location of the first data;

Determining, according to the file identifier of the first file, an index node of the first file in the memory;

Corresponding relationship between a file block number of the first data and a logical block number of a data block storing the second data is recorded in a file update table pointed to by the first pointer in the index node of the first file, a logical block number is used to point to a physical address storing the second data;

Setting a state of the first data to be invalid in a file status table pointed to by the second pointer in the index node.
The storage device according to claim 9, wherein the controller is further configured to:

Receiving a file read request, where the file read request carries a file identifier of the second file and a second file offset;

Determining an index node of the second file according to the file identifier of the second file;

Determining, according to the second file offset, a file block number of the data to be read;

Determining, according to the file status table pointed by the second pointer in the index node of the second file, that the status of the data to be read is invalid;

Determining, according to the file update table pointed by the first pointer in the index node of the second file, a logical block number corresponding to the file block number of the data to be read;

Determining, according to a logical block number corresponding to the file block number of the data to be read, a physical address of the data to be read;

Reading the data to be read according to the physical address of the data to be read.
The storage device according to claim 9, wherein the controller is further configured to:

The update flag bit in the index node of the first file is set to have an update, and the update flag bit is used to determine an update status of the first file.
The storage device according to claim 10, wherein the controller is further configured to:

Determining the second according to an update flag bit in an index node of the second file before determining a state of the data to be read according to a file state table pointed to by a second pointer in the index node of the second file The file has an update, and the update flag is used to determine an update status of the second file.