CN110825712A - Method for recovering disk cluster data managed by logical volume - Google Patents
Method for recovering disk cluster data managed by logical volume Download PDFInfo
- Publication number
- CN110825712A CN110825712A CN201911050168.2A CN201911050168A CN110825712A CN 110825712 A CN110825712 A CN 110825712A CN 201911050168 A CN201911050168 A CN 201911050168A CN 110825712 A CN110825712 A CN 110825712A
- Authority
- CN
- China
- Prior art keywords
- logical volume
- volume
- data
- configuration area
- physical
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1847—File system types specifically adapted to static storage, e.g. adapted to flash memory or SSD
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/172—Caching, prefetching or hoarding of files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input 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/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input 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/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0673—Single storage device
- G06F3/0674—Disk device
- G06F3/0676—Magnetic disk device
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method for recovering disk cluster data managed by a logical volume, which is characterized by comprising the following steps: s100: loading each disk, wherein a disk cluster managed by the logical volume is composed of one or more disks, and each logical volume is allocated to one or more disks; s200: acquiring each physical volume, and acquiring a UUID of each physical volume, a configuration area offset address of each physical volume and the maximum byte length of the configuration area of each physical volume; s300: addressing and analyzing a configuration area of logical volume management of each physical volume to obtain a volume group, wherein the configuration area comprises description information of the configuration area and data of the configuration area; s400: and performing data recovery according to the type of the logical volume managed by the logical volume, the sequence of the sections managed by the logical volume and the number of the sections.
Description
Technical Field
The invention belongs to the field of electronic data recovery and forensics, and relates to a disk cluster data recovery method, in particular to a logical volume management disk cluster data recovery method.
Background
lvm is a shorthand of Logical Volume Manager, which is a mechanism for managing disk partitions in a Linux environment, and is a perfect solution that the size of a file system can be freely adjusted on the premise of realizing zero shutdown in the Linux, and the file system spans different disks and partitions, so that the lvm device management technology is widely used in a large-capacity storage system.
In the prior art, data recovery and extraction under the lvm are based on an operating system on which the data recovery and extraction depend, and if the operating system carrying the lvm is damaged, the data of a disk cluster of the logical volume management lvm cannot be recovered.
Disclosure of Invention
Aiming at the defects Of the prior art, the invention provides a method for recovering disk cluster data which is not dependent on logical volume management Of an operating system where lvm is located by analyzing configuration information in the lvm and combining a structure Of data organization Of a disk cluster (JBOD): and analyzing the data of the lvm configuration area, acquiring the type of the logical volume managed by the logical volume, the sequence of the sections managed by the logical volume and the number of the sections, and recovering the data, so as to achieve the purpose of recovering the data of the disk cluster managed by the logical volume.
For ease of description, the present invention may include the following terms:
pe: physical Extent physical Block
pv: physical volume;
pvs: physical volumes physical volume
vg: volume group
vgs: volume groups volume group
lv: local volume logical volume
lvs: logical volumes logical volume
segment: segment of
JBOD: disk cluster (Just a Bunch Of Disks)
The invention comprises the following steps:
s100: loading each disk, wherein a disk cluster managed by the logical volume is composed of one or more disks, and each logical volume is allocated to one or more disks;
s200: acquiring each physical volume, and acquiring a UUID of each physical volume, a configuration area offset address of each physical volume and the maximum byte length of the configuration area of each physical volume;
s300: addressing and analyzing a configuration area of logical volume management of each physical volume to obtain a volume group, where the configuration area includes description information of the configuration area and data of the configuration area, and the step S300 includes the following steps:
s301: addressing and analyzing the description information of the configuration area of each physical volume according to the offset address of the configuration area of each physical volume, and acquiring the offset address of the data of the configuration area and the byte length of the data of the configuration area;
s302: addressing the offset address of the data of the configuration area, and acquiring the data of the configuration area according to the byte length of the data of the configuration area;
s303: analyzing the data of the configuration area, and acquiring the type of the logical volume managed by the logical volume, the size of the physical block, the starting address of the physical block, the sequence of the sections managed by the logical volume and the number of the sections;
s400: and performing data recovery according to the type of the logical volume managed by the logical volume, the sequence of the sections managed by the logical volume and the number of the sections.
Preferably, the step S200 includes the steps of:
s201: the number of sectors addressed is given an initial value of 0;
s202: judging whether the number of the addressed sectors is less than or equal to 8, if so, executing the step S203, otherwise, ending the flow;
s203: reading a currently addressed sector, wherein the number of the addressed sectors is equal to the number of the addressed sectors + 1;
s204: judging whether each value of the current sector is matched with the structural body of the physical volume, if so, representing that the current sector is the metadata information of raid, and executing the step S205, otherwise, executing the step S202;
s205: the UUID of the current physical volume is recorded.
Preferably, the structure of the physical volume has a data structure as shown in the following table one:
data structure of table-physical volume
Wherein, signature: the physical volume signature managed by the logical volume is fixed to a character string label, and the corresponding value is 0x454E4F4C4542414C and is used as an identifier for judging whether the current sector is the physical volume;
sector number: an offset position of a structure sector of a current physical volume;
checksum: a checksum, a CRC32 checksum starting from 0x14 bytes to the currently identified sector end address;
type indicator: name and version information of logical volume management;
UUID: a unique identification of the physical volume represented in an ASCII string;
physical volume size: the logical volume byte length is in bytes;
lvm config area offset: the logical volume manages the offset address of the configuration area, which takes the initial address of the disk as the first address and the unit as byte;
lvm config area size: the logical volume manages the byte length of the configuration area in bytes.
Preferably, the description information of the configuration area has a data structure as shown in the following table two:
data structure of description information of table two configuration area
Wherein, checksum: a CRC32 checksum of the configuration region, which is updated with the update of the data of the configuration region;
signature: configuring regular character strings of the area identifiers: "\ x20lvm2\ x20x [ 5A% r0N ]"
version: version information
lvm config area offset: the logical volume manages the offset address of the configuration area, which takes the initial address of the disk as the first address and the unit as byte;
lvm config area size: the logical volume manages the byte length of the configuration area, and the unit is byte;
current lvm config offset: the offset address of the data of the current logical volume management configuration area takes the initial address of the logical volume management configuration area as a first address, and the unit is byte;
current lvm config size: the current logical volume manages the byte length of the configuration area, and the unit is byte.
Preferably, the step S400 includes the steps of:
s401: acquiring and judging whether the type of the logical volume is striped, if so, executing a step S402, otherwise, ending the process;
s402: judging whether the current number of the sections is equal to the acquired number of the sections, if so, ending the process, otherwise, executing the step S403;
s403: analyzing the current section, comprising the following steps:
s4031: acquiring the size of the current section according to the acquired number of the sections, wherein the unit is a physical block;
s4032: reading information of the strips domain, acquiring a physical volume to which the current section belongs, and acquiring a disk to which the current section belongs according to the UUID;
s4033: reading information of the strips domain, obtaining an offset address of the current section in the physical volume, and calculating the offset address of the current section in the disk by adopting the following formula:
the offset address of the current sector in the disk is the offset address of the current sector in the physical volume, the physical block size and the physical block starting address;
s404: and reading the data of each section according to the offset address of each section in the disk and the size of each section, and combining the data in sequence to obtain the disk cluster data managed by the logical volume so as to complete the recovery of the disk cluster data.
The invention has the following beneficial effects: the technical problem that the disk cluster data managed by the logical volume cannot be recovered after an operating system is damaged in the prior art is solved.
Drawings
FIG. 1 is a general flow diagram of a method provided by the present invention;
fig. 2 is a specific flowchart for acquiring the UUID, the offset address of the configuration area, and the maximum byte length of the configuration area according to an embodiment of the present invention.
Detailed Description
For ease of description, the present invention may include the following terms:
pe: physical Extent physical Block
pv: physical volume;
pvs: physical volumes physical volume
vg: volume group
vgs: volume groups volume group
lv: local volume logical volume
lvs: logical volumes logical volume
segment: segment of
Wherein, a plurality of pes exist in one pv; 1 or more pv make up vg; there is more than one lv in vg; lv allocates space from vg; except for the specific data format (such as ASCII code and regular character string), data related to offset addresses and the like are stored in a small-end format.
Fig. 1 shows a general flow chart of the method provided by the present invention. As shown in fig. 1, the present invention comprises the steps of:
s100: loading each disk, wherein a disk cluster managed by the logical volume is composed of one or more disks, and each logical volume is allocated to one or more disks;
s200: acquiring each physical volume, and acquiring a UUID of each physical volume, a configuration area offset address of each physical volume and the maximum byte length of the configuration area of each physical volume;
specifically, pvs are obtained, and the UUID of each pvs is obtained. The disk used by lvm would first be formatted to pv, if not, then the disk is not the disk used by lvm. The UUID is a unique ID generated by the lvm for each pv, is an important basis for the connection between the lv and the pv, and needs to be stored after the UUID is acquired. Step S200 includes the steps of:
s201: the number of sectors addressed is given an initial value of 0;
s202: judging whether the number of the addressed sectors is less than or equal to 8, if so, executing the step S203, otherwise, ending the flow;
s203: reading a currently addressed sector, wherein the number of the addressed sectors is equal to the number of the addressed sectors + 1;
s204: judging whether each value of the current sector is matched with the structural body of the physical volume, if so, representing that the current sector is the metadata information of raid, and executing the step S205, otherwise, executing the step S202; the structure of the physical volume is parsed to have a data structure as shown in the following table:
data structure of table-physical volume
Wherein, signature: the physical volume signature managed by the logical volume is fixed to a character string label, and the corresponding value is 0x454E4F4C4542414C and is used as an identifier for judging whether the current sector is the physical volume;
sector number: an offset position of a structure sector of a current physical volume;
checksum: a checksum, a CRC32 checksum starting from 0x14 bytes to the currently identified sector end address;
type indicator: name and version information of logical volume management;
UUID: a unique identification of the physical volume represented in an ASCII string;
physical volume size: the logical volume byte length is in bytes;
lvm config area offset: the logical volume manages the offset address of the configuration area, which takes the initial address of the disk as the first address and the unit as byte;
lvm config area size: the logical volume manages the byte length of the configuration area in bytes.
S205: the UUID of the current physical volume is recorded.
S300: addressing and analyzing the configuration area of the logical volume management of each physical volume to obtain volume groups, wherein the configuration area comprises the description information of the configuration area and the data of the configuration area, and the description information of the configuration area has a data structure shown in the following table two after analysis,
data structure of description information of table two configuration area
Wherein, checksum: a CRC32 checksum of the configuration region, which is updated with the update of the data of the configuration region;
signature: configuring regular character strings of the area identifiers: "\ x20LVM2\ x20x [ 5A% r0N ]"
version information
lvm config area offset: the logical volume manages the offset address of the configuration area, which takes the initial address of the disk as the first address and the unit as byte;
lvm config area size: the logical volume manages the byte length of the configuration area, and the unit is byte;
current lvm config offset: the offset address of the data of the current logical volume management configuration area takes the initial address of the logical volume management configuration area as a first address, and the unit is byte;
current lvm config size: the current logical volume manages the byte length of the configuration area, and the unit is byte.
Step S300 includes the steps of:
s301: addressing and analyzing the description information of the configuration area of each physical volume according to the offset address of the configuration area of each physical volume, namely, the lvm config area offset, and acquiring the offset address of the data of the configuration area and the byte length of the data of the configuration area, namely, current lvm config offset and current lvm config size;
s302: addressing the offset address of the data of the configuration area, and acquiring the data of the configuration area according to the byte length of the data of the configuration area;
specifically, the data in the lvm configuration area is recorded and stored in ASCII characters, the offset address (i.e., current lvm config offset) of the data in the current logical volume management configuration area is the first address of the start address of the logical volume management configuration area, and the byte length is current lvm config size.
The following is data of the configuration area in one embodiment of the present invention. The storage is in an ASCII mode, and the storage can be directly opened in a text mode. Furthermore, if pv belongs to the same vg, then this part of the data is the same.
S303: analyzing data of the configuration area, and acquiring the type of a logical volume managed by the logical volume, the size of a physical block, the starting address of the physical block, the sequence of sections managed by the logical volume and the number of the sections;
specifically, in the embodiment described above, the current vg is named "vg 0" and is composed of three pvs, i.e., pv0, pv1, and pv 2. The following is exemplified by pv 0:
id (8 qrhoG-8 SVw-7RVr-pWkk-tdjp-E2zR-dZCk5z) is the UUID of vg, pe is the extent _ size, and the value is 8192 sectors;
the starting position of pv0 is pe _ start, the value is 2048 sectors, the number of pes is pe _ count, therefore, the size of pv is 511 × 8192 sectors, and id (9fwFXd-yQpq-lroH-B29Z-Wpu2-i60F-ephug7) is the UUID of pv;
the vg0 comprises an lv, entitled "lv 0", of size: (511+1) pes;
lv0 has two segments (segments) that occupy two pvs, pv0 and pv1, the occupancy being summarized in the following data allocation table:
data allocation table of lv0 in pv:
| pv | pe start | pe end | UUID |
| pv0 | 0 | 511 | 9fwFXd-yQpq-lroH-B29Z-Wpu2-i60F-ephug7 |
| pv1 | 0 | 1 | plAiNk-4eHP-FnwE-0Kk7-Zn31-nABx-glXrlE |
id in lv0 (i.e., fS8qE1-qi56-0Tu2-fZVL-WlZ0-pmmy-r87kcG) is the UUID of lv;
the creation time is the time created by lv in the format of a Unix timestamp with a value of 1556186399, i.e., 2019/4/2517: 59: 59;
segment _ count, which is the number of segments, has a value of 2, indicating that 2 segments are included; the sequence of the segments is the sequence of segment1 and segment 2;
the following description will be made by taking segment1 as an example:
start _ extend, which is the starting position of the current section lv, and has the unit pe, i.e., the physical block;
the extension _ count, i.e., the size of the current section lv, is expressed in pe, i.e., a physical block;
type is logical volume type of logical volume management, and its value is striped, and is expressed as data of logical volume managed disk cluster (JBOD) type;
the second term value (i.e., 0) of the strings field, which represents the offset position of the current segment in pv, is denoted as pv _ off, and has the unit of pe, i.e., physical block;
s400: and performing data recovery according to the type of the logical volume managed by the logical volume, the sequence of the sections managed by the logical volume and the number of the sections.
Specifically, step S400 includes the steps of:
s401: acquiring and judging whether the type of the logical volume is striped, if so, executing a step S402, otherwise, ending the process;
in this embodiment, since the type of lvm is striped, which means that the type of lvm is data of a logical volume managed just Bunch of disks (JBOD), and also means that the data of the bunch of disks is arranged and composed according to the segment sequence, the process goes to step S402;
s402: judging whether the current number of the sections is equal to the acquired number of the sections, if so, ending the process, otherwise, executing the step S403; in this embodiment, the segment number (segment _ count) is 2.
S403: analyzing the current section, comprising the following steps:
s4031: acquiring the size of the current section according to the acquired section number (segment _ count) being 2, wherein the unit is a physical block;
s4032: the information of the reading strips field is as follows:
as can be known from the first value "pv0" of the pointers field, the physical volume to which the current extent belongs is pv0, and the UUID of pv0 can be obtained according to the aforementioned "data allocation table of lv0 in pv", and corresponds to the UUID obtained in step S200, that is, the disk to which the current extent belongs can be known;
s4033: the information of the reading strips field is as follows:
as can be seen from the second term value "0" in the pointers field, the offset address of the current extent in the physical volume is 0, which may be denoted as pv _ off, and the offset address of the current extent in the disk is calculated by using the following formula:
the offset address of the current sector in the disk is the offset address of the current sector in the physical volume, the physical block size and the physical block starting address; i.e., pv _ off _ extension _ size + pe _ start
S404: and reading the data of each section according to the offset address of each section in the disk and the size of each section, and combining the data in sequence to obtain the disk cluster data managed by the logical volume so as to complete the recovery of the disk cluster data.
The method solves the technical problem that no method for recovering the disk cluster data managed by the logical volume exists in the prior art.
It is to be understood that the invention is not limited to the examples described above, but that modifications and variations are possible to those skilled in the art in light of the above teachings, and that all such modifications and variations are intended to be included within the scope of the invention as defined in the appended claims.
Claims (5)
1. A method for recovering disk cluster data managed by a logical volume is characterized by comprising the following steps:
s100: loading each disk, wherein a disk cluster managed by the logical volume is composed of one or more disks, and each logical volume is allocated to one or more disks;
s200: acquiring each physical volume, and acquiring a UUID of each physical volume, a configuration area offset address of each physical volume and the maximum byte length of the configuration area of each physical volume;
s300: addressing and analyzing a configuration area of logical volume management of each physical volume to obtain a volume group, where the configuration area includes description information of the configuration area and data of the configuration area, and the step S300 includes the following steps:
s301: addressing and analyzing the description information of the configuration area of each physical volume according to the offset address of the configuration area of each physical volume, and acquiring the offset address of the data of the configuration area and the byte length of the data of the configuration area;
s302: addressing the offset address of the data of the configuration area, and acquiring the data of the configuration area according to the byte length of the data of the configuration area;
s303: analyzing the data of the configuration area, and acquiring the type of the logical volume managed by the logical volume, the size of the physical block, the starting address of the physical block, the sequence of the sections managed by the logical volume and the number of the sections;
s400: and performing data recovery according to the type of the logical volume managed by the logical volume, the sequence of the sections managed by the logical volume and the number of the sections.
2. The method for recovering data of a logical volume managed disk cluster according to claim 1, wherein the step S200 comprises the steps of:
s201: the number of sectors addressed is given an initial value of 0;
s202: judging whether the number of the addressed sectors is less than or equal to 8, if so, executing the step S203, otherwise, ending the flow;
s203: reading a currently addressed sector, wherein the number of the addressed sectors is equal to the number of the addressed sectors + 1;
s204: judging whether each value of the current sector is matched with the structural body of the physical volume, if so, representing that the current sector is the metadata information of raid, and executing the step S205, otherwise, executing the step S202;
s205: the UUID of the current physical volume is recorded.
3. The method of claim 2, wherein the physical volume structure has a data structure as shown in the following table:
data structure of table-physical volume
Wherein, signature: the physical volume signature managed by the logical volume is fixed to a character string label, and the corresponding value is 0x454E4F4C4542414C and is used as an identifier for judging whether the current sector is the physical volume;
sector number: an offset position of a structure sector of a current physical volume;
checksum: a checksum, a CRC32 checksum starting from 0x14 bytes to the currently identified sector end address;
type indicator: name and version information of logical volume management;
UUID: a unique identification of the physical volume represented in an ASCII string;
physical volume size: the logical volume byte length is in bytes;
lvm config area offset: the logical volume manages the offset address of the configuration area, which takes the initial address of the disk as the first address and the unit as byte;
lvm config area size: the logical volume manages the byte length of the configuration area in bytes.
4. The method for recovering data of a logical volume managed disk cluster according to claim 1, wherein the description information of the configuration area has a data structure as shown in table two below:
data structure of description information of table two configuration area
Wherein, checksum: a CRC32 checksum of the configuration region, which is updated with the update of the data of the configuration region;
signature: configuring regular character strings of the area identifiers: "\ x20LVM2\ x20x [ 5A% r0N ]"
version information
lvm config area offset: the logical volume manages the offset address of the configuration area, which takes the initial address of the disk as the first address and the unit as byte;
lvm config area size: the logical volume manages the byte length of the configuration area, and the unit is byte;
current lvm config offset: the offset address of the data of the current logical volume management configuration area takes the initial address of the logical volume management configuration area as a first address, and the unit is byte;
current lvm config size: the current logical volume manages the byte length of the configuration area, and the unit is byte.
5. The method for recovering data of a logical volume managed disk cluster according to claim 1, wherein said step S400 comprises the steps of:
s401: acquiring and judging whether the type of the logical volume is striped, if so, executing a step S402, otherwise, ending the process;
s402: judging whether the current number of the sections is equal to the acquired number of the sections, if so, ending the process, otherwise, executing the step S403;
s403: analyzing the current section, comprising the following steps:
s4031: acquiring the size of the current section according to the acquired number of the sections, wherein the unit is a physical block;
s4032: reading information of the strips domain, acquiring a physical volume to which the current section belongs, and acquiring a disk to which the current section belongs according to the UUID;
s4033: reading information of the strips domain, obtaining an offset address of the current section in the physical volume, and calculating the offset address of the current section in the disk by adopting the following formula:
the offset address of the current sector in the disk is the offset address of the current sector in the physical volume, the physical block size and the physical block starting address;
s404: and reading the data of each section according to the offset address of each section in the disk and the size of each section, and combining the data in sequence to obtain the disk cluster data managed by the logical volume so as to complete the recovery of the disk cluster data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911050168.2A CN110825712B (en) | 2019-10-31 | 2019-10-31 | Method for recovering disk cluster data managed by logical volume |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911050168.2A CN110825712B (en) | 2019-10-31 | 2019-10-31 | Method for recovering disk cluster data managed by logical volume |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110825712A true CN110825712A (en) | 2020-02-21 |
| CN110825712B CN110825712B (en) | 2023-08-01 |
Family
ID=69551518
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911050168.2A Active CN110825712B (en) | 2019-10-31 | 2019-10-31 | Method for recovering disk cluster data managed by logical volume |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110825712B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113253945A (en) * | 2021-07-08 | 2021-08-13 | 成都易我科技开发有限责任公司 | Disk coiling clustering method and device and electronic equipment |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0911827B1 (en) * | 1997-10-21 | 2011-11-30 | Sony Corporation | Recording and/or reproduction apparatus, file management method and providing medium |
| CN102508724A (en) * | 2011-10-25 | 2012-06-20 | 北京同有飞骥科技股份有限公司 | Disk bad block processing method based on soft RAID (redundant array of independent disks) |
| EP2704011A1 (en) * | 2012-08-31 | 2014-03-05 | Hitachi Ltd. | Management method of virtual storage system and remote copy system |
| US8713356B1 (en) * | 2011-09-02 | 2014-04-29 | Emc Corporation | Error detection and recovery tool for logical volume management in a data storage system |
| CN104090829A (en) * | 2014-08-06 | 2014-10-08 | 浪潮电子信息产业股份有限公司 | Method for realizing logical volume metadata backup storage |
| US9003227B1 (en) * | 2012-06-29 | 2015-04-07 | Emc Corporation | Recovering file system blocks of file systems |
| CN104793904A (en) * | 2015-05-07 | 2015-07-22 | 北京银信长远科技股份有限公司 | Method for setting hard disk forbidden zone of logical volume and backing up configuration information through hard disk forbidden zone |
| CN105487984A (en) * | 2014-09-17 | 2016-04-13 | 中兴通讯股份有限公司 | Dynamic compression method and apparatus for virtual machine disk data by host system |
| CN105718217A (en) * | 2016-01-18 | 2016-06-29 | 浪潮(北京)电子信息产业有限公司 | Method and device for maintaining data consistency of thin provisioning database |
| CN106648474A (en) * | 2017-01-01 | 2017-05-10 | 国云科技股份有限公司 | Virtual machine disk recovery method based on logical volume |
-
2019
- 2019-10-31 CN CN201911050168.2A patent/CN110825712B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0911827B1 (en) * | 1997-10-21 | 2011-11-30 | Sony Corporation | Recording and/or reproduction apparatus, file management method and providing medium |
| US8713356B1 (en) * | 2011-09-02 | 2014-04-29 | Emc Corporation | Error detection and recovery tool for logical volume management in a data storage system |
| CN102508724A (en) * | 2011-10-25 | 2012-06-20 | 北京同有飞骥科技股份有限公司 | Disk bad block processing method based on soft RAID (redundant array of independent disks) |
| US9003227B1 (en) * | 2012-06-29 | 2015-04-07 | Emc Corporation | Recovering file system blocks of file systems |
| EP2704011A1 (en) * | 2012-08-31 | 2014-03-05 | Hitachi Ltd. | Management method of virtual storage system and remote copy system |
| CN104090829A (en) * | 2014-08-06 | 2014-10-08 | 浪潮电子信息产业股份有限公司 | Method for realizing logical volume metadata backup storage |
| CN105487984A (en) * | 2014-09-17 | 2016-04-13 | 中兴通讯股份有限公司 | Dynamic compression method and apparatus for virtual machine disk data by host system |
| CN104793904A (en) * | 2015-05-07 | 2015-07-22 | 北京银信长远科技股份有限公司 | Method for setting hard disk forbidden zone of logical volume and backing up configuration information through hard disk forbidden zone |
| CN105718217A (en) * | 2016-01-18 | 2016-06-29 | 浪潮(北京)电子信息产业有限公司 | Method and device for maintaining data consistency of thin provisioning database |
| CN106648474A (en) * | 2017-01-01 | 2017-05-10 | 国云科技股份有限公司 | Virtual machine disk recovery method based on logical volume |
Non-Patent Citations (2)
| Title |
|---|
| 倪晟;陈启祥;: "***数据恢复技术" * |
| 倪晟;陈启祥;: "***数据恢复技术", 软件导刊, no. 21 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113253945A (en) * | 2021-07-08 | 2021-08-13 | 成都易我科技开发有限责任公司 | Disk coiling clustering method and device and electronic equipment |
| CN113253945B (en) * | 2021-07-08 | 2021-09-28 | 成都易我科技开发有限责任公司 | Disk coiling clustering method and device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110825712B (en) | 2023-08-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10620846B2 (en) | Enhancing flash translation layer to improve performance of databases and filesystems | |
| US9817581B2 (en) | Maintaining versions of data in solid state memory | |
| US20140173226A1 (en) | Logical object deletion | |
| US9122582B2 (en) | File system for maintaining data versions in solid state memory | |
| US20160004642A1 (en) | Storage device and method for controlling storage device | |
| US20100042802A1 (en) | Management of recycling bin for thinly-provisioned logical volumes | |
| CN109918352B (en) | Memory system and method of storing data | |
| KR20170023734A (en) | Methods and systems for improving flash memory flushing | |
| US9135162B2 (en) | Data versioning in solid state memory | |
| US9229852B2 (en) | Flash translation layer system for maintaining data versions in solid state memory | |
| CN103092673A (en) | Snapshot processing method and device for virtual machine | |
| US20180341561A1 (en) | Determining modified portions of a raid storage array | |
| CN110825712B (en) | Method for recovering disk cluster data managed by logical volume | |
| US20190026033A1 (en) | Method and system for hardware accelerated cache flush | |
| CN104657471B (en) | Method and system for establishing pre-allocated file of FAT file system | |
| CN111143110B (en) | Metadata-based raid data recovery method in logical volume management | |
| CN114327292B (en) | File management method, system, electronic device and storage medium | |
| CN111124311B (en) | Method for recovering raid data based on configuration information under logical volume management | |
| EP3182267A1 (en) | Method and device for isolating disk regions | |
| CN105760313A (en) | Data processing method and device for SPI-Flash-based (Serial Peripheral Interface-Flash-based) file system | |
| CN110543434A (en) | NAND flash device, memory table management method, device and storage medium | |
| US20210216208A1 (en) | Method for storage management, electronic device and computer program product | |
| US10613973B1 (en) | Garbage collection in solid state drives | |
| CN111831224A (en) | Method, system and equipment for erasing exFAT partition file residual space |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |