CN112446061A - Data undeletable method, mobile terminal and storage medium - Google Patents

Data undeletable method, mobile terminal and storage medium Download PDF

Info

Publication number
CN112446061A
CN112446061A CN202011293647.XA CN202011293647A CN112446061A CN 112446061 A CN112446061 A CN 112446061A CN 202011293647 A CN202011293647 A CN 202011293647A CN 112446061 A CN112446061 A CN 112446061A
Authority
CN
China
Prior art keywords
command
write
data
file
directory entry
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202011293647.XA
Other languages
Chinese (zh)
Inventor
林寅
吴大畏
李晓强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hefei Zhicun Microelectronics Co ltd
Original Assignee
Hefei Zhicun Microelectronics Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hefei Zhicun Microelectronics Co ltd filed Critical Hefei Zhicun Microelectronics Co ltd
Priority to CN202011293647.XA priority Critical patent/CN112446061A/en
Publication of CN112446061A publication Critical patent/CN112446061A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/70Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
    • G06F21/78Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure storage of data
    • G06F21/80Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure storage of data in storage media based on magnetic or optical technology, e.g. disks with sectors
    • G06F21/805Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure storage of data in storage media based on magnetic or optical technology, e.g. disks with sectors using a security table for the storage sub-system
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0628Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0652Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket

Abstract

The application discloses a method for undeletable data, a mobile terminal and a storage medium, which relate to the field of data storage, wherein the method comprises the following steps: acquiring the position information of a file in a storage device; receiving a user input command; judging the type of a command input by a user; when the user input command is a normal command, processing according to a normal command processing flow; according to the scheme, the connection between the storage device and the terminal can be judged, and when the command input by the user is a command for modifying or deleting the file position information, the connection between the storage device and the terminal is disconnected, so that the information safety in the storage device is ensured.

Description

Data undeletable method, mobile terminal and storage medium
Technical Field
The present application relates to the field of data storage, and in particular, to a method for undeletable data, a mobile terminal, and a storage medium.
Background
Files stored in the storage device can be modified and deleted. If it is to be ensured that the file is not deleted, the rights of modification and deletion need to be controlled by the software and the app via the software running on the host side or the app on the mobile device side. In addition, once the software or app is cracked, there is also a risk that the file is modified or deleted.
Therefore, how to ensure the security of the file in the storage device is an urgent problem to be solved, after the storage device is connected with the terminal, the original data is kept from being modified and deleted.
Disclosure of Invention
The method and the device aim to ensure the data security of the storage device and ensure that original data are not deleted and modified after the storage device is connected with the terminal.
The technical purpose of the application is realized by the following technical scheme: a method of non-deletable data, comprising the steps of:
acquiring the position information of a file in a storage device;
receiving a user input command;
judging the type of a command input by a user;
when the user input command is a normal command, processing according to a normal command processing flow;
and when the user input command is a command for modifying or deleting the file position information, disconnecting the storage equipment from the terminal.
The scheme of the application discloses a method for undeletable data, which judges whether the command is a command for modifying or deleting file position information or not through the command type input by a user, if so, the command is indicated to modify or delete information in a file, so that the connection between the storage device and a terminal is disconnected.
Further, the method for undeletable data, wherein the step of obtaining location information of the file in the storage device comprises:
reading sector data in the storage device, and analyzing the type of a file system;
analyzing the address information of the file allocation table, and storing the last effective cluster number;
the data table is retrieved and the location of the last active directory entry is stored.
According to the scheme, sector data of the storage device are read to analyze the type of the file system, different types of the file system are consistent in general direction and only different parameters are distinguished, address information of a file allocation table in the storage device is analyzed, the last effective cluster number is stored, the cluster number is the smallest unit, two identical file allocation tables are stored in a file allocation table area, management of storage space (cluster chain) occupied by files and management of free space are achieved through FATs, the FATs are important, and the two file allocation tables are stored so that when the first file is damaged, the second file is available. The file system divides and manages the storage space of the data area according to clusters, the clusters are basic units of space distribution and recovery, namely, one file always occupies a plurality of whole clusters, and the residual space of the last cluster used by the file is not used any more but wasted, so that the position of the last file is convenient to know by storing the last effective cluster number, and the data table is searched for storing the position of the last effective directory entry.
Further, the method for undeletable data, wherein the step of determining the type of the command input by the user comprises:
judging whether the command input by the user is a write-in command or not;
when the input command is not a write command, the input command is marked as a normal command.
According to the scheme of the application, the command type is judged for the command input by the user, and whether the command is a write command is judged firstly, because a general read command does not relate to data modification and deletion, when the command input by the user is not the write command, the input command is marked as a normal command, and the processing is carried out according to a normal flow.
Further, the method for undeletable data, wherein the step of determining whether the command input by the user is a write command further comprises:
when the input command is a write command, judging an operation area of the write command;
judging whether the write-in command is an operation data area;
when the write command is an operation data area, marking the write command as a normal command.
In the above solution of the present application, in the foregoing solution, when the command input by the user is not a write command, processing is performed according to a normal flow, and when the command input by the user is a write command, it is necessary to determine an operation area of the write command, where different operation areas and different permissions are different, for example, operating a data area, and writing into the data area indicates that file data is added, and no modification is involved, because a file directory is not changed, the processing is performed according to a normal command operation flow.
Further, the method for undeletable data, wherein the step of determining whether the write command is an operation data area further comprises:
when the write-in command is not an operation data area, judging whether the write-in command operates a directory entry or not;
when the write-in command is an operation directory entry, judging whether the write-in command is a newly added directory entry;
when the write command is a newly added directory entry, marking the write command as a normal command;
in the above scheme of the present application, in the foregoing scheme, when the command input by the user is an operation data area, processing is performed according to a normal process, and when the command input by the user is not an operation data area, it needs to be determined whether the write command operates a directory entry, and further, whether a directory of the file is newly added, where the newly added directory belongs to a normal command and does not modify the original data, and therefore belongs to a normal command, processing is performed according to a normal command process.
Further, the method for undeletable data, wherein when the write command is an operation directory entry, the step of determining whether the write command is an additional directory entry further includes:
when the write-in command is not the newly added directory entry, judging whether the write-in command has a deletion mark;
and when the write-in command contains a deletion mark, marking the write-in command as a command for modifying or deleting the file position information.
According to the scheme, when the write-in command is a newly added directory entry, normal processing is performed, when the write-in command is not the newly added directory entry, whether the write-in command has a deletion mark or not needs to be judged, the deletion mark is formed, the write-in command is marked to be a command for modifying or deleting the file position information, the connection of equipment is disconnected, and data safety is guaranteed.
Further, the method for undeletable data, wherein when the write command is not a newly added directory entry, the step of determining whether the write command has a deletion flag further includes:
when the write-in command does not contain the deletion mark, judging whether the write-in command only modifies the access time;
and if so, marking the writing command as a normal command, and if not, marking the writing command as a command for modifying or deleting the file position information.
In the above solution of the present application, the foregoing solution mentions that when the write command includes the delete flag, the connection is disconnected, and when the write command does not include the delete flag, the write command needs to be determined again to determine whether the write command modifies only the access time, because the write command does not include the delete flag, it indicates that the write command is a modify command, and therefore it needs to determine whether the modify command modifies the file location information, and when the modify command modifies the access time, the file information is not modified, and therefore, the write command is a normal command, and when the write command does not modify the access time, it indicates that the write command is attempting to modify the file data, and therefore, the connection between the device and the terminal is disconnected.
Further, the method for undeletable data, wherein when the write command is not an operation data area, the step of determining whether the write command operates a directory entry further comprises:
when the write-in command is not an operation directory entry, judging whether the write-in command modifies an old entry of a file table;
when the write-in command is a command for modifying the old table entry of the file table, marking the write-in command as a command for modifying or deleting the file position information;
and when the write-in command does not modify the old table entry of the file table, marking the write-in command as a normal command for newly added data.
In the above solution of the present application, in the foregoing solution, it is mentioned how a write command is determined by an operation directory entry, and when the write command is neither an operation data area nor an operation directory entry, it needs to be determined whether the write command modifies an old entry of a file table, that is, data in an original table is modified, and when the write command is determined to be not an operation data area nor an operation directory entry, the device is disconnected, and when the write command is not a modification of an old entry of a file table, it indicates that a user is adding new data, and the write command is marked as a normal command.
Further, the present application also discloses a mobile terminal, which includes a processor, and a memory connected to the processor, where the memory stores a data non-deletable program, and the data non-deletable program implements the steps of the data non-deletable method as described above when executed by the processor.
Further, the present application also discloses a storage medium, wherein the storage medium stores a data non-deletable implementation program, and when the storage medium is executed by a processor, the storage medium implements the steps of the data non-deletable method.
In summary, the present application discloses a method, a mobile terminal and a storage medium for undeletable data, which relate to the field of data storage, wherein the method comprises the following steps: acquiring the position information of a file in a storage device; receiving a user input command; judging the type of a command input by a user; when the user input command is a normal command, processing according to a normal command processing flow; according to the scheme, the connection between the storage device and the terminal can be judged, and when the command input by the user is a command for modifying or deleting the file position information, the connection between the storage device and the terminal is disconnected, so that the information safety in the storage device is ensured.
Drawings
FIG. 1 is a flow chart of steps of a data undeletable method described herein.
Fig. 2 is a flowchart of step S1 of the data undeletable method described in the present application.
Fig. 3 is a flowchart of step S3 of the data undeletable method described in the present application.
Fig. 4 is a flowchart of step S31 of the data undeletable method described in the present application.
Fig. 5 is a flowchart of step S311 of the data undeletable method according to the present application.
Fig. 6 is a flowchart of step S3111 of the data undeletable method according to the present application.
Fig. 7 is a flowchart of step S31111 of the data undeletable method according to the present application.
Fig. 8 is a flowchart of step S311111 of the data undeletable method described in the present application.
Reference numerals are used.
Detailed Description
The present application is described in further detail below with reference to the attached drawings.
Files stored in the storage device can be modified and deleted. If it is to be ensured that the file is not deleted, the rights of modification and deletion need to be controlled by the software and the app via the software running on the host side or the app on the mobile device side. In addition, once the software or app is cracked, there is also a risk that the file is modified or deleted.
Therefore, in order to solve the above problems, the present application discloses a data undeletable method, which can protect file information in a storage device from being modified or deleted, and can prevent modification operation from being implemented by the previous software or APP (upper layer implementation) and move to the storage device management algorithm (lower layer implementation). The risk of the scheme being cracked is greatly reduced.
The general steps are shown in fig. 1, which is a flow chart of the steps of the data undeletable method, including:
s1, acquiring position information of a file in storage equipment;
s2, receiving a user input command;
s3, judging the type of the command input by the user;
s4, when the user input command is a normal command, processing the flow according to the normal command;
and S5, when the user input command is a command for modifying or deleting the file position information, disconnecting the storage equipment from the terminal.
To implement the above steps, first, the file location information is determined, and if the location information of the original data of the file changes, the file data is modified or deleted, and the present application determines based on the change of this parameter, so, referring to fig. 2, step S1 includes:
s11, reading sector data in the storage device, and analyzing the type of a file system;
s12, analyzing the address information of the file allocation table, and storing the last effective cluster number;
s13, retrieving the data table and storing the position of the last valid directory entry. Corresponding to the last data of the file and the last directory, respectively.
In the preferred embodiment of the present application, taking FAT as an example, when the storage device is powered on, the boot loader module loads a pre-burned management algorithm FTL from the storage chip, and the FTL (Flash Translation Layer) manages the operation (read/write) of the storage device by the host.
In this application, two newly-increased management modules at FTL: the device comprises a file system analysis module and a write command preprocessing module. The functions are respectively as follows:
a file system analysis module: after a boot loader is powered on and executed on the device, a management algorithm FTL is loaded to a RAM (random access memory) and initialization of relevant tables and parameters of the FTL is completed, the FTL will first invoke a file system analysis module, read contents of a file system in advance and analyze key information (FAT Table (file allocation Table), FDT (Function Data Table, etc.) therein), and store the analyzed parameters in the RAM.
A write command preprocessing module: when the host issues a write command, the FTL invokes the write command preprocessing module first, and transmits write command parameters issued by the host to the write command preprocessing module, and the preprocessing module determines whether to write data into the storage device.
Since read commands do not involve changes to the data, no special handling of the read commands is required.
Therefore, referring to fig. 3, after acquiring the command input by the user, step S3 specifically includes:
s31, judging whether the input command is a write-in command;
s32, when the command input by the user is not a writing command, marking the input command as a normal command. For example, a read command, or a retrieve command, does not involve a change to the data, and therefore, is processed according to a normal processing flow;
when the input command is a write command, there are many cases regarding the write command, and different write commands may modify file data or may not modify or delete data, so that the command type needs to be determined again, referring to fig. 4, the step S31 further includes:
s311, when the input command is a write-in command, judging an operation area of the write-in command;
s312, when the write command is an operation data area, marking the write command as a normal command.
The operation area is divided into a data area and other areas, wherein the operation of the data area is a normal command, which means that a user adds data after inputting data, namely the last cluster number, and the original data is not modified or deleted for adding operation, so that the processing is performed according to a normal flow.
When the written command is not the operation data area, it needs to be determined again, referring to fig. 5, the step S311 includes:
s3111, when the write-in command is not an operation data area, judging whether the write-in command operates a directory entry;
s3112, when the write-in command is an operation directory entry, judging whether the write-in command is a newly added directory entry;
s3113, when the write command is a newly added directory entry, marking the write command as a normal command.
There are many cases where the write command is not an operation directory entry, where the addition directory belongs to a normal command, and therefore, it is necessary to determine whether the write command is an addition directory entry, and if so, normal processing is performed.
When the write command is not the new directory entry, it needs to be determined again, referring to fig. 6, the step S3111 includes:
s31111, when the write-in command is not a newly added directory entry, judging whether the write-in command has a deletion mark;
s31112, when the write command includes a delete flag, marking the write command as a command for modifying or deleting the file location information.
And when the writing command has the deletion mark, the writing command is a deletion command, so that the connection between the storage equipment and the terminal is disconnected.
When the write command does not have the delete flag, it indicates that the write command is a modify command, referring to fig. 7, the step S31111 further includes:
s311111, when the write-in command does not include the delete mark, judging whether the write-in command only modifies the access time;
s311112. when yes, marking the write command as a normal command, and when no, marking the write command as a command for modifying or deleting file position information.
And if the modified content is only the access time, the modified content is not related to data modification, so that the processing is carried out according to a normal processing flow, and when the write command is not the access time modification, the modified content required by the write command is data in a file, so that the connection between the storage device and the terminal is disconnected.
As mentioned above, when the write command is not an operation data area, it is determined whether the write command operates a directory entry, and when the write command is not an operation directory entry, it is determined whether the write command modifies an old entry of the file table. Referring to fig. 8, a flowchart of the step S311111 specifically includes:
s3111111, when the write command is not an operation directory entry, determining whether the write command modifies an old entry of a file table;
s3111112, when the write-in command is to modify an old entry of a file table, marking the write-in command as a command to modify or delete file location information;
s3111113, when the write-in command is not to modify the old table entry of the file table, marking the write-in command as a normal command, namely to modify the data in the old table, and when the write-in command is to modify the data in the old table entry, disconnecting the storage device from the terminal.
In summary, the application discloses that accurate determination of the command type is guaranteed after layer-by-layer judgment from the acquisition of the command input by the user, processing is performed according to a normal command processing flow when the write-in command is a normal command, and when the write-in command is a modification or deletion command, the connection between the storage device and the terminal is timely disconnected, so that the security of data in the file is guaranteed.
In the above description of the present application, ftl (Flash Translation layer) translates into a Flash Translation layer, which is a connection relationship between Flash Memory (storage medium) and Device Controller (Device master). In the whole storage system, the FTL functions as a translation officer, and converts a logical address sent from Host (computer, mobile phone, etc.) to Device (eMMC, SSD) into a physical address written in Flash (address mapping management). While address conversion is carried out, the FTL also gives consideration to Flash management, and not only needs to control the erasing times (wear leveling) of each Block on the Flash, but also needs to manage useless data (garbage collection) on the Flash.
These three points are briefly described.
1. Address mapping management concept
Unlike the magnetic head of a mechanical hard disk for directly reading and writing data, the SSD or other hard disks using Flash as a storage medium cannot directly read and write data. The method for solving the problem is that the FTL layer manages several logic mapping tables to perform intermediate conversion, Host gives a logic address, and the FTL establishes a mapping relation on the logic mapping tables according to the logic address and is connected to a physical address on Flash. Generally, after the FTL processes the logical address, the established mapping relationship includes a Block number, a Page number, and the like of Flash, and when data is read, data is found at a position corresponding to Flash according to the information, and is transmitted to Host.
2. Wear leveling concept
Flash is used as a storage medium, and the programmable times of the Flash are important points which must be considered. Taking the current solid state example, mostly using TLC Flash as a storage medium, the programming times of which are between 1000-1500 times, and if the erasing times of some blocks on TLC Flash exceed the time limit, a bad Block will be generated, so the FTL needs to implement wear leveling, coordinate the blocks on the whole Flash, and take out the blocks with less use times to share the pressure of the blocks with more use times. In popular terms, wear leveling is to make the erase times of each Block on Flash as the same as possible by relatively optimal selection, so as to avoid the problem that some blocks become bad blocks due to too many erase times, which results in the decrease of the available capacity of users.
3. Garbage recovery concept
Because of different storage principles, when data on a hard disk taking Flash as a storage medium, such as an SSD, is deleted, only the logical address of the Host end is deleted, and the actual data exists on the physical address of Flash, the space is still occupied (so it is safe without deleting your data, when garbage recovery is not performed, they can still find back), and subsequent data can only be written on other blocks (pages) when written, which may cause that only 2M of 8M data on one Block is valid data, and other "dummy data" from which logical addresses are deleted, and the empty Block is not enough in the long run. The problem is solved by means of Garbage Collection (GC), the function of the method is to find an empty Block (target Block), then move effective data on blocks (source blocks) with more false data, and release and erase the source blocks, so that one target Block can contain data of a plurality of source blocks, the purpose of forcibly changing the number of the source blocks is achieved, and more space is left for a user.
In another embodiment of the present application, a mobile terminal is provided that includes a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the memory stores data information and pictures for logical controls. The processor is used for providing calculation and control capability, and all steps in the foregoing schemes are realized when the processor executes the computer program, so that the details are not described herein.
In another embodiment of the present application, a computer-readable storage medium is provided, which stores a computer program that can be loaded by a processor and execute the logic control dragging display method, and when the computer program is executed by the processor, all steps of the foregoing scheme are implemented, which is not described herein again.
The application discloses a method for undeletable data, a mobile terminal and a storage medium, which relate to the field of data storage, wherein the method comprises the following steps: acquiring the position information of a file in a storage device; receiving a user input command; judging the type of a command input by a user; when the user input command is a normal command, processing according to a normal command processing flow; according to the scheme, the connection between the storage device and the terminal can be judged, and when the command input by the user is a command for modifying or deleting the file position information, the connection between the storage device and the terminal is disconnected, so that the information safety in the storage device is ensured.
The embodiments of the present invention are preferred embodiments of the present application, and the scope of protection of the present application is not limited by the embodiments, so: all equivalent changes made according to the structure, shape and principle of the present application shall be covered by the protection scope of the present application.

Claims (10)

1. A method of non-deletable data, comprising the steps of:
acquiring the position information of a file in a storage device;
receiving a user input command;
judging the type of a command input by a user;
when the user input command is a normal command, processing according to a normal command processing flow;
and when the user input command is a command for modifying or deleting the file position information, disconnecting the storage equipment from the terminal.
2. The data indelible method of claim 1, wherein the step of obtaining location information of the file within the storage device comprises:
reading sector data in the storage device, and analyzing the type of a file system;
analyzing the address information of the file allocation table, and storing the last effective cluster number;
the data table is retrieved and the location of the last active directory entry is stored.
3. The data indelible method of claim 2, wherein the step of determining the type of the command input by the user comprises:
judging whether the command input by the user is a write-in command or not;
when the input command is not a write command, the input command is marked as a normal command.
4. The method of claim 3, wherein the step of determining whether the command input by the user is a write command further comprises:
when the input command is a write command, judging an operation area of the write command;
judging whether the write-in command is an operation data area;
when the write command is an operation data area, marking the write command as a normal command.
5. The method of claim 4, wherein the step of determining whether the write command is an operation data area further comprises:
when the write-in command is not an operation data area, judging whether the write-in command operates a directory entry or not;
when the write-in command is an operation directory entry, judging whether the write-in command is a newly added directory entry;
when the write command is a newly added directory entry, marking the write command as a normal command.
6. The method of claim 5, wherein when the write command is an operation directory entry, the step of determining whether the write command is a new directory entry further comprises:
when the write-in command is not the newly added directory entry, judging whether the write-in command has a deletion mark;
and when the write-in command contains a deletion mark, marking the write-in command as a command for modifying or deleting the file position information.
7. The method of claim 6, wherein when the write command is not a new directory entry, the step of determining whether the write command has a deletion flag further comprises:
when the write-in command does not contain the deletion mark, judging whether the write-in command only modifies the access time;
and if so, marking the writing command as a normal command, and if not, marking the writing command as a command for modifying or deleting the file position information.
8. The method of claim 7, wherein when the write command is not an operation data area, the step of determining whether the write command operates a directory entry further comprises:
when the write-in command is not an operation directory entry, judging whether the write-in command modifies an old entry of a file table;
when the write-in command is a command for modifying the old table entry of the file table, marking the write-in command as a command for modifying or deleting the file position information;
and when the write-in command does not modify the old table entry of the file table, marking the write-in command as a normal command for newly added data.
9. A mobile terminal comprising a processor and a memory coupled to the processor, the memory storing a data indelible program that, when executed by the processor, performs the steps of the data indelible method of claims 1-8.
10. A storage medium storing a data non-deletable implementation program, the storage medium when executed by a processor implementing step 2 of the data non-deletable method according to any one of claims 1-8.
CN202011293647.XA 2020-11-18 2020-11-18 Data undeletable method, mobile terminal and storage medium Pending CN112446061A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011293647.XA CN112446061A (en) 2020-11-18 2020-11-18 Data undeletable method, mobile terminal and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011293647.XA CN112446061A (en) 2020-11-18 2020-11-18 Data undeletable method, mobile terminal and storage medium

Publications (1)

Publication Number Publication Date
CN112446061A true CN112446061A (en) 2021-03-05

Family

ID=74737507

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011293647.XA Pending CN112446061A (en) 2020-11-18 2020-11-18 Data undeletable method, mobile terminal and storage medium

Country Status (1)

Country Link
CN (1) CN112446061A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114691625A (en) * 2022-04-21 2022-07-01 成都理工大学 Data management method for massive dynamic files

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010122606A1 (en) * 2009-04-24 2010-10-28 Hitachi, Ltd. Storage system and data management method of the same
CN106024046A (en) * 2016-05-24 2016-10-12 深圳市硅格半导体股份有限公司 Data storage method and device
CN110321740A (en) * 2019-05-15 2019-10-11 深圳市江波龙电子股份有限公司 A kind of data manipulation method and storage equipment of storage equipment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010122606A1 (en) * 2009-04-24 2010-10-28 Hitachi, Ltd. Storage system and data management method of the same
US20110191302A1 (en) * 2009-04-24 2011-08-04 Hitachi, Ltd. Storage system and data management method of the same
CN106024046A (en) * 2016-05-24 2016-10-12 深圳市硅格半导体股份有限公司 Data storage method and device
CN110321740A (en) * 2019-05-15 2019-10-11 深圳市江波龙电子股份有限公司 A kind of data manipulation method and storage equipment of storage equipment

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114691625A (en) * 2022-04-21 2022-07-01 成都理工大学 Data management method for massive dynamic files

Similar Documents

Publication Publication Date Title
US11513707B2 (en) Memory system and method of controlling nonvolatile memory
US9575682B2 (en) Maintaining versions of data in solid state memory
US8386746B2 (en) Storage unit management methods and systems
US7895394B2 (en) Storage system
US20210342302A1 (en) Host and storage system for securely deleting files and operating method of the host
US9122584B2 (en) File system for maintaining data version in solid state memory
CN108021510A (en) The method for operating the storage device being managed to multiple name space
US9940040B2 (en) Systems, solid-state mass storage devices, and methods for host-assisted garbage collection
CN102567215B (en) Space distribution method and system for simplified supply
CN106874211A (en) The control method of accumulator system and nonvolatile memory
US20120254514A1 (en) Memory system, controller, and method for controlling memory system
CN106874217A (en) Accumulator system and control method
CN106326229B (en) File storage method and device of embedded system
WO2011095516A1 (en) Method and system for mass storage on flash memory
CN108021513A (en) A kind of date storage method and device
CN109671458A (en) The method of management flash memory module and relevant flash controller
TW201520793A (en) Memory system with shared file system
US9430492B1 (en) Efficient scavenging of data and metadata file system blocks
CN108604165A (en) Storage device
US11269783B2 (en) Operating method for data storage device
US20220075523A1 (en) Flash memory local purge
KR20130034450A (en) Storage device and driving method thereof
JP2009518698A (en) Improved host interface
CN109947670A (en) Storage system and its operating method
US9524236B1 (en) Systems and methods for performing memory management based on data access properties

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination