CN110795043B - Distributed storage block zeroing method and device, electronic equipment and storage medium - Google Patents

Distributed storage block zeroing method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN110795043B
CN110795043B CN201911039171.4A CN201911039171A CN110795043B CN 110795043 B CN110795043 B CN 110795043B CN 201911039171 A CN201911039171 A CN 201911039171A CN 110795043 B CN110795043 B CN 110795043B
Authority
CN
China
Prior art keywords
write
block
command
written
data
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.)
Active
Application number
CN201911039171.4A
Other languages
Chinese (zh)
Other versions
CN110795043A (en
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.)
Beijing Inspur Data Technology Co Ltd
Original Assignee
Beijing Inspur Data Technology 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 Beijing Inspur Data Technology Co Ltd filed Critical Beijing Inspur Data Technology Co Ltd
Priority to CN201911039171.4A priority Critical patent/CN110795043B/en
Publication of CN110795043A publication Critical patent/CN110795043A/en
Application granted granted Critical
Publication of CN110795043B publication Critical patent/CN110795043B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/0638—Organizing or formatting or addressing of data
    • G06F3/064—Management of blocks
    • 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/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0652—Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
    • 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
    • G06F3/0659—Command handling arrangements, e.g. command buffers, queues, command scheduling
    • 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/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
    • 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)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Storage Device Security (AREA)

Abstract

The application discloses a distributed storage block zeroing method, different from the mode of realizing the block zeroing effect by calling a dbs_wite interface in the prior art, when the received WRITE_SAME command is determined to be a block zeroing command for realizing the block zeroing effect, the dbs_wite interface which is another functional interface provided by a distributed storage library libdbs is replaced, the block zeroing effect is also realized from one angle through operations such as deleting/cutting/punching, and the like, the operations such as deleting and the like have more convenient and higher efficiency than the writing operation used by the dbs_wite interface in most scenes, and the replacement operation is simpler and more convenient, so that the time consumption is shorter and the load applied to storage equipment is smaller. The application also discloses a distributed storage block zeroing device, electronic equipment and a readable storage medium, which have the beneficial effects.

Description

Distributed storage block zeroing method and device, electronic equipment and storage medium
Technical Field
The present disclosure relates to the field of distributed storage technologies, and in particular, to a method and apparatus for zeroing a distributed storage block, an electronic device, and a readable storage medium.
Background
In a distributed storage system, a zero-out operation must be performed before all disks are initially written to clear all possible previously left-over data by writing zeros in all data blocks of the disk.
The existing instruction operation for the distributed storage block is implemented by calling a dbs_wtire interface (one of the function interfaces of the block storage library libdbs provided by the distributed storage, where dbs is an english abbreviation of Distributed block service and chinese name is the distributed block service) in response to the issued write_same command. Because the dbs_wtire interface is a block zeroing effect realized by copying N copies of data to be written and then writing each target storage block respectively, mass copying and writing respectively can cause low execution efficiency and apply a larger load to the storage device.
Therefore, in view of the above technical drawbacks of the prior art, how to provide a distributed storage block zeroing method with higher execution efficiency and smaller load application is a problem to be solved by those skilled in the art.
Disclosure of Invention
The application provides a distributed storage block zeroing method, a distributed storage block zeroing device, electronic equipment and a readable storage medium, and aims to improve execution efficiency of distributed storage block zeroing and reduce load applied to storage equipment.
In order to achieve the above object, the present application provides a method for zeroing a distributed storage block, including:
receiving a write_same command;
judging whether the WRITE_SAME command is a block zero command or not;
and if the WRITE_SAME command is the block zeroing command, calling a dbs_discard interface to zeroe the target storage block.
Optionally, determining whether the write_same command is a block zero command includes:
judging whether the WRITE_SAME command is added with an UNMAP identifier or not;
and if the WRITE_SAME command is added with the UNMAP identifier, determining that the WRITE_SAME command is the block zero setting command.
Optionally, when the write_same command is not attached with the UNMAP identifier, the method further includes:
extracting data to be written from the WRITE_SAME command;
judging whether the data to be written is all 0;
and if the data to be written is all 0, determining that the WRITE_SAME command is the block zero setting command.
Optionally, when the write_same command is not the block zero command, the method further includes:
copying the data to be written to obtain each data to be written, wherein the number of the data to be written is consistent with that of the target storage blocks;
and calling a dbs_write interface to write the data to be written into each target storage block respectively.
In order to achieve the above object, the present application further provides a distributed storage block zeroing apparatus, which includes:
a command receiving unit for receiving a write_same command;
the block zero setting command judging unit is used for judging whether the WRITE_SAME command is a block zero setting command or not;
and the dbs_discard interface calls a zeroing unit, which is used for calling the dbs_discard interface to zeroe the target storage block when the WRITE_SAME command is the block zeroing command.
Optionally, the block zero-setting command determining unit includes:
the UNMAP identifier judging subunit is used for judging whether the WRITE_SAME command is added with a UNMAP identifier or not;
and the first determining subunit is used for determining the WRITE_SAME command as the block zero command when the WRITE_SAME command is added with the UNMAP identifier.
Optionally, the block zero-setting command determining unit further includes:
the data to be written extracting subunit is configured to extract, when the write_same command is not attached with the UNMAP identifier, to obtain data to be written from the write_same command;
a 0 judging subunit, configured to judge whether the data to be written is 0;
and the second determining subunit is used for determining the WRITE_SAME command as the block zeroing command when the data to be written is all 0.
Optionally, the distributed storage block zeroing device further includes:
the data to be written copying unit is used for copying the data to be written when the WRITE_SAME command is not the block zero setting command, so as to obtain each data to be written, the number of which is consistent with that of the target storage blocks;
and the dbs_write interface call is a write unit and is used for calling the dbs_write interface to write the data to be written into each target storage block respectively.
To achieve the above object, the present application further provides an electronic device, including:
a memory for storing a computer program;
a processor for implementing the distributed storage block zeroing method as described above when executing the computer program.
To achieve the above object, the present application further provides a readable storage medium having stored thereon a computer program which, when executed by a processor, implements a distributed storage block zeroing method as described in the above.
The method for zeroing the distributed storage block comprises the following steps: receiving a write_same command; judging whether the WRITE_SAME command is a block zero command or not; and if the WRITE_SAME command is the block zeroing command, calling a dbs_discard interface to zeroe the target storage block.
Obviously, unlike the mode of realizing the block zeroing effect by calling the dbs_wite interface in the prior art, when the received WRITE_SAME command is determined to be a block zeroing command for realizing the block zeroing effect, the dbs_wite interface, which is another functional interface provided by the distributed block storage library libdbs, also realizes the block zeroing effect from one angle through operations such as deleting/cutting/punching, and the like, and operations such as deleting, and the like, have more convenient and higher efficiency than the writing operation used by the dbs_wite interface in most scenes, and the simpler and more convenient operation is used for realizing shorter time consumption and smaller load applied to the storage device.
The application also provides a distributed storage block zeroing device, electronic equipment and a readable storage medium, which have the beneficial effects and are not repeated here.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings may be obtained according to the provided drawings without inventive effort to a person skilled in the art.
Fig. 1 is a flowchart of a method for zeroing a distributed storage block according to an embodiment of the present application;
FIG. 2 is a flowchart of another method for zeroing a distributed storage block according to an embodiment of the present application;
FIG. 3 is a flowchart of another method for zeroing a distributed storage block according to an embodiment of the present application;
fig. 4 is a structural block diagram of a distributed storage block zeroing device according to an embodiment of the present application.
Detailed Description
The application provides a distributed storage block zeroing method, a distributed storage block zeroing device, electronic equipment and a readable storage medium, and aims to improve execution efficiency of distributed storage block zeroing and reduce load applied to storage equipment.
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
Example 1
Referring to fig. 1, fig. 1 is a flowchart of a distributed storage block zeroing method according to an embodiment of the present application, which includes the following steps:
s101: receiving a write_same command;
the write_same command is used to achieve the SAME WRITE, i.e., WRITE the SAME data in each target memory block. However, the block zeroing effect can be achieved only when 0 is written in each target storage block. That is, the write_same command is not limited to achieving the block zero purpose.
S102: judging whether the WRITE_SAME command is a block zero command, if so, executing S103, otherwise, executing S104;
based on S101, this step is intended to determine, based on the information contained in the write_same command, whether the write_same command is a block zero command that implements a block zero effect.
S103: calling a dbs_discard interface to set a target storage block to zero;
the step is based on the judgment result of S102 that the write_same command is a block zeroing command, and is different from the prior art that 0 is respectively written into each target storage block by calling a dbs_write interface according to the SAME operation of original writing, the target storage block is zeroed by calling another function interface-dbs_discard interface provided by a distributed block storage library libdbs. The dbs_write interface copies the data 0 to be written contained in the write_same command for multiple copies (consistent with the number of target memory blocks), and then WRITEs 0 into each target memory block according to offset (offset) and size (size), and the dbs_discard interface achieves the SAME block zeroing effect from another angle through operations such as deleting/cutting/punching. Compared with the mode that the dbs_write interface realizes the block zero setting effect by writing 0 one by one, the method can greatly introduce operation steps through 'advanced' operations such as deleting/cutting/punching and the like, obviously reduce time consumption, and take the deleting operation as an example, the deleting operation is directly carried out on the target storage block, so that data in the target storage block can be directly emptied, and the empty storage block has the same effect as the full-write 0 when being read.
Therefore, the execution efficiency can be significantly improved, and the load applied to the storage device can be reduced.
S104: the same operation as the native write is performed.
This step is based on the judgment result in S102 that the write_same command is not a block zero command, and therefore the native WRITE SAME operation will be performed: and calling a dbs_write interface to WRITE the data to be written contained in the WRITE_SAME command into each target storage block respectively.
A specific implementation, including but not limited to, may be:
copying the data to be written to obtain each data to be written, wherein the number of the data to be written is consistent with that of the target storage blocks;
and calling a dbs_write interface to write the data to be written into each target storage block respectively.
Specifically, this process also requires parsing the write_same command to obtain an offset (offset) and a size (size), and calling the (size/WRITE-once-maximum-WRITE-data) dbs_write interface to perform the native WRITE-SAME command operation based on the size and WRITE-once-maximum-WRITE-data.
Unlike the manner of implementing the block zeroing effect by calling the dbs_wite interface in the prior art, when the received write_same command is determined to be a block zeroing command for implementing the block zeroing effect, the embodiment replaces another functional interface provided by the distributed block storage library libdbs, namely the dbs_wite interface, to implement the block zeroing effect from one angle through operations such as deletion/truncation/punching, and the like, and operations such as deletion and the like have more convenient and higher efficiency than the WRITE operation used by the dbs_wite interface in most scenes, and the replacement operation with simpler and more convenient operations also has shorter time consumption and smaller load applied to the storage device.
Example two
On the basis of the first embodiment, this embodiment provides an implementation manner of judging whether the write_same command is a block zero-setting command by judging whether the UNMAP identifier is attached to the scene that the UNMAP identifier can be attached to the write_same command.
Referring to fig. 2, fig. 2 is a flowchart of another method for zeroing a distributed storage block according to an embodiment of the present application, including the following steps:
s201: receiving a write_same command;
s202: judging whether the WRITE_SAME command is added with an UNMAP identifier, if so, executing S203, otherwise, executing S204;
the special flag bit on the UNMAP identifier essentially indicates that the SAME data to be written is 0 when the special flag bit is in an activated or recognizable state, so that if the UNMAP identifier can be recognized in an application scenario where the UNMAP identifier can be added to the WRITE_SAME command, the WRITE_SAME command can be rapidly determined to be a block zero-setting command according to the meaning represented by the UNMAP.
S203: calling a dbs_discard interface to set a target storage block to zero;
s204: the same operation as the native write is performed.
The other steps of the first embodiment are the same, and the description and explanation of the same parts are referred to the corresponding parts of the first embodiment, and are not repeated here.
Example III
On the basis of the second embodiment, considering the situations that the version or the UNMAP identification function is not used in some scenes, even if the UNMAP identification cannot be identified, the possibility that the write_same command is not a block zero command cannot be directly excluded. Therefore, on the basis of the second embodiment, the present embodiment further adds a determination to determine whether the data to be written is 0 to further determine whether the write_same command is a block zero command, so as to prevent erroneous determination that the user is not considered to be around.
Referring to fig. 3, fig. 3 is a flowchart of another method for zeroing a distributed storage block according to an embodiment of the present application, including the following steps:
s301: receiving a write_same command;
s302: judging whether the WRITE_SAME command is added with an UNMAP identifier, if so, executing S206, otherwise, executing S303;
s303: extracting data to be written from the WRITE_SAME command;
specifically, the data to be written is usually stored in a buffer (register), so that the data to be written can be extracted from a preset field in the buffer. It is not excluded, however, that the data to be written is present in a special coded form, as long as it can be identified.
S304: judging whether the data to be written is 0, if so, executing S306, otherwise, executing S305;
s305: performing a native write same operation;
s306: the dbs_discard interface is called to zero the target memory block.
Compared with the scheme of the second embodiment, the method increases the judgment based on whether the data to be written is 0 or not under the condition that the UNMAP identifier cannot be identified, considers the more comprehensive condition, and reduces the probability of erroneous judgment as much as possible.
Because of the complexity and cannot be illustrated by one, those skilled in the art will recognize that many examples exist in accordance with the basic method principles provided herein in combination with actual situations, which are within the scope of the present application without significant inventive effort.
Referring to fig. 4, fig. 4 is a block diagram of a distributed storage block zeroing apparatus according to an embodiment of the present application, where the apparatus may include:
a command receiving unit 100 for receiving a write_same command;
a block zero command determining unit 200, configured to determine whether the write_same command is a block zero command;
the dbs_discard interface calls a zeroing unit 300, which is configured to call the dbs_discard interface to zero the target storage block when the write_same command is a block zeroing command.
The block zeroing order judgment unit 200 may include:
the UNMAP identifier judging subunit is used for judging whether the WRITE_SAME command is added with a UNMAP identifier or not;
and the first determining subunit is used for determining the WRITE_SAME command as the block zeroing command when the WRITE_SAME command is attached with the UNMAP identifier.
Further, the block zeroing order judgment unit 200 may further include:
the data to be written extracting subunit is used for extracting the data to be written from the WRITE_SAME command when the WRITE_SAME command is not attached with the UNMAP identifier;
all 0 judging subunit, configured to judge whether the data to be written is all 0;
and the second determining subunit is used for determining the write_same command as the block zeroing command when the data to be written is all 0.
Further, the distributed storage block zeroing apparatus may further include:
the data to be written copying unit is used for copying the data to be written when the WRITE_SAME command is not a block zero setting command, so as to obtain each data to be written, the number of which is consistent with that of the target storage blocks;
the dbs_write interface call is a write unit, and is used for calling the dbs_write interface to write each data to be written into each target storage block respectively.
The present embodiment exists as an embodiment of the apparatus corresponding to the above embodiment of the method, and has all the beneficial effects of the method embodiment, which are not described herein in detail.
Based on the above embodiment, the present application further provides an electronic device, where the electronic device may include a memory and a processor, where the memory stores a computer program, and when the processor invokes the computer program in the memory, the steps of the distributed storage block zeroing method provided in the above embodiment may be implemented. Of course, the electronic device may also include various necessary network interfaces, power supplies, and other components, etc.
The present application also provides a readable storage medium, on which a computer program is stored, where the computer program can implement the steps of the distributed storage block zeroing method provided in the foregoing embodiments when executed by an execution terminal or a processor. The storage medium may include: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In the description, each embodiment is described in a progressive manner, and each embodiment is mainly described by the differences from other embodiments, so that the same similar parts among the embodiments are mutually referred. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
Specific examples are set forth herein to illustrate the principles and embodiments of the present application, and the description of the examples above is only intended to assist in understanding the methods of the present application and their core ideas. It will be apparent to those skilled in the art that various changes and modifications can be made herein without departing from the principles of the application, which are intended to be covered by the appended claims.
It should also be noted that in this specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.

Claims (6)

1. A method for zeroing a distributed storage block, comprising:
receiving a write_same command;
judging whether the WRITE_SAME command is a block zero command or not;
if the WRITE_SAME command is the block zeroing command, invoking a dbs_discard interface to zeroe a target storage block;
the invoking the dbs_discard interface to zero the target memory block includes:
calling a dbs_discard interface provided by a distributed block storage library libdbs, and realizing block zero setting through deleting or cutting or punching operation;
judging whether the WRITE_SAME command is a block zero command or not, comprising:
judging whether the WRITE_SAME command is added with an UNMAP identifier or not;
if the WRITE_SAME command is added with the UNMAP identifier, determining that the WRITE_SAME command is the block zero setting command;
when the write_same command is not attached with the UNMAP identifier, the method further includes:
extracting data to be written from the WRITE_SAME command;
judging whether the data to be written is all 0;
and if the data to be written is all 0, determining that the WRITE_SAME command is the block zero setting command.
2. The distributed storage block zeroing method of claim 1, wherein when the write_same command is not the block zeroing command, further comprising:
copying the data to be written to obtain each data to be written, wherein the number of the data to be written is consistent with that of the target storage blocks;
and calling a dbs_write interface to write the data to be written into each target storage block respectively.
3. A distributed storage block zeroing apparatus, comprising:
a command receiving unit for receiving a write_same command;
the block zero setting command judging unit is used for judging whether the WRITE_SAME command is a block zero setting command or not;
the dbs_discard interface calls a zeroing unit, which is used for calling the dbs_discard interface to zeroe a target storage block when the WRITE_SAME command is the block zeroing command;
the dbs_discard interface call zero setting unit is used for:
calling a dbs_discard interface provided by a distributed block storage library libdbs, and realizing block zero setting through deleting or cutting or punching operation;
the block zeroing command judging unit includes:
the UNMAP identifier judging subunit is used for judging whether the WRITE_SAME command is added with a UNMAP identifier or not;
a first determining subunit of a block zero setting command, configured to determine that the write_same command is the block zero setting command when the write_same command is attached with the UNMAP identifier;
the block zeroing command judgment unit further includes:
the data to be written extracting subunit is configured to extract, when the write_same command is not attached with the UNMAP identifier, to obtain data to be written from the write_same command;
a 0 judging subunit, configured to judge whether the data to be written is 0;
and the second determining subunit is used for determining the WRITE_SAME command as the block zeroing command when the data to be written is all 0.
4. The distributed storage block zeroing apparatus of claim 3, further comprising:
the data to be written copying unit is used for copying the data to be written when the WRITE_SAME command is not the block zero setting command, so as to obtain each data to be written, the number of which is consistent with that of the target storage blocks;
and the dbs_write interface call is a write unit and is used for calling the dbs_write interface to write the data to be written into each target storage block respectively.
5. An electronic device, comprising:
a memory for storing a computer program;
a processor for implementing the distributed storage block zeroing method according to any of the claims 1 to 2 when executing the computer program.
6. A readable storage medium, characterized in that a computer program is stored in the readable storage medium, which, when being executed by a processor, implements the distributed storage block zeroing method according to any of the claims 1 to 2.
CN201911039171.4A 2019-10-29 2019-10-29 Distributed storage block zeroing method and device, electronic equipment and storage medium Active CN110795043B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911039171.4A CN110795043B (en) 2019-10-29 2019-10-29 Distributed storage block zeroing method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911039171.4A CN110795043B (en) 2019-10-29 2019-10-29 Distributed storage block zeroing method and device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN110795043A CN110795043A (en) 2020-02-14
CN110795043B true CN110795043B (en) 2023-06-06

Family

ID=69442053

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911039171.4A Active CN110795043B (en) 2019-10-29 2019-10-29 Distributed storage block zeroing method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN110795043B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114281239A (en) * 2020-09-28 2022-04-05 华为云计算技术有限公司 Mirror image file writing method and device

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110245004A (en) * 2019-06-13 2019-09-17 深圳前海微众银行股份有限公司 Command executing method, device, equipment and computer readable storage medium

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8745336B2 (en) * 2008-05-29 2014-06-03 Vmware, Inc. Offloading storage operations to storage hardware
CN103631537B (en) * 2013-11-29 2016-09-14 华为技术有限公司 The management method of a kind of virtual disk and device
US10140035B2 (en) * 2014-06-25 2018-11-27 Hitachi, Ltd. Method for appropriately controlling duplicated volumes in virtual volume subsystems
CN107179929B (en) * 2017-05-15 2020-02-07 苏州浪潮智能科技有限公司 WRITE _ SAME function optimization implementation method and device
US11461027B2 (en) * 2017-07-18 2022-10-04 Vmware, Inc. Deduplication-aware load balancing in distributed storage systems

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110245004A (en) * 2019-06-13 2019-09-17 深圳前海微众银行股份有限公司 Command executing method, device, equipment and computer readable storage medium

Also Published As

Publication number Publication date
CN110795043A (en) 2020-02-14

Similar Documents

Publication Publication Date Title
CN107643880B (en) File data migration method and device based on distributed file system
US5931935A (en) File system primitive allowing reprocessing of I/O requests by multiple drivers in a layered driver I/O system
CN109614377A (en) File delet method, device, equipment and the storage medium of distributed file system
CN107608820B (en) Erasure code based file writing method and related device
CN109739933A (en) Memory space method for releasing, device, terminal and computer readable storage medium
CN109614045B (en) Metadata dropping method and device and related equipment
CN111382011B (en) File data access method and device and computer readable storage medium
CN110597779A (en) Data reading and writing method in distributed file system and related device
CN110795043B (en) Distributed storage block zeroing method and device, electronic equipment and storage medium
CN104965835A (en) Method and apparatus for reading and writing files of a distributed file system
CN110879764B (en) Bitmap setting method, device and equipment and readable storage medium
CN117492661A (en) Data writing method, medium, device and computing equipment
CN110427157B (en) Formatting method and related device
CN108052294B (en) Modification writing method and modification writing system of distributed storage system
CN110658993A (en) Snapshot rollback method, device, equipment and storage medium
CN110781101A (en) One-to-many mapping relation storage method and device, electronic equipment and medium
CN110795388B (en) Binary file processing method, system, equipment and readable storage medium
CN204463134U (en) SATA hard disc Write-protect system
CN110019086A (en) More copy read methods, equipment and storage medium based on distributed file system
CN110007875B (en) Method, device and equipment for migrating effective data
CN111061429B (en) Data access method, device, equipment and medium
CN107705089B (en) Service processing method, device and equipment
CN103500092A (en) Judgment method for WORM appending writing and storage device
CN112394876A (en) Large file storage/reading method, storage/reading device and computer equipment
CN117369731B (en) Data reduction processing method, device, equipment and medium

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