CN113655961A - Method for realizing uniqueness and accurate positioning of logical volume name based on multi-bit coding - Google Patents
Method for realizing uniqueness and accurate positioning of logical volume name based on multi-bit coding Download PDFInfo
- Publication number
- CN113655961A CN113655961A CN202110947342.4A CN202110947342A CN113655961A CN 113655961 A CN113655961 A CN 113655961A CN 202110947342 A CN202110947342 A CN 202110947342A CN 113655961 A CN113655961 A CN 113655961A
- Authority
- CN
- China
- Prior art keywords
- logical volume
- code
- codes
- bit
- disk
- 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
- 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/0662—Virtualisation aspects
- G06F3/0665—Virtualisation aspects at area level, e.g. provisioning of virtual or logical volumes
-
- 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/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0614—Improving the reliability of storage systems
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)
Abstract
The invention discloses a method for realizing uniqueness and accurate positioning of a logical volume name based on multi-bit coding, which comprises the following steps: s1, acquiring the related information of the disk logical volume in the current required code from the asset database, and taking the related information of the disk logical volume as the input source of the code; s2, performing 16-bit encoding and disassembling on each disk logical volume; s3, combining the codes disassembled in the step S2 and generating a disk logical volume code; and S4, disassembling the 16-bit codes into 6 groups of sub-codes, and reversely positioning the coded disk logical volume codes. Has the advantages that: the invention adopts 16-bit coding, ensures the uniqueness of the disk logical volume and has definite identification degree, and can quickly know the host information, the controller information, the common volume group information, the flash memory volume group information, the equipment file information and the acceleration ratio information from the disk logical volume through the combination and disassembly of the coding.
Description
Technical Field
The invention relates to the technical field of mapping a disk logical volume to a computing end by a storage end under a computing storage separation architecture, in particular to a method for realizing uniqueness and accurate positioning of a logical volume name based on multi-bit coding.
Background
The IT system is international standard IEC60364 which distinguishes three different types of earthing systems, using two letter codes to denote TN, TT and IT. The first letter indicates the relationship of power supply terminal to ground: t represents that one point of a power supply end is directly grounded; i means that all live parts of the power supply terminals are not grounded or a point is grounded via an impedance. The second letter indicates the relationship of the exposed conductive portion of the electrical device to ground: t represents the direct grounding of the exposed conductive portion of the electrical device, which grounding point is electrically independent of the grounding point of the power supply terminal; n indicates that the exposed conductive portion of the electrical device is in direct electrical connection with the power supply terminal ground.
At present, the IT system has higher requirements on data scale and data processing capacity, and the storage separation architecture has the characteristics of high performance and high expansion capacity. However, when the storage side is mapped to the computation side, it is often difficult to distinguish the correspondence between the computation side disk logical volume and the storage side disk logical volume through tool transformation such as multipath, which causes a significant increase in the operation and maintenance cost.
At present, the corresponding relation is usually recorded by using a traditional excel table, but UUID and WWN numbers need to be manually corresponding, and errors may be generated due to manual operation in the process, so that the rigor is not achieved. Meanwhile, when the system fails, manual inquiry and positioning are required in combination with recording, so that the time for fault positioning treatment is prolonged, and the online aging requirement of the online system is difficult to meet.
An effective solution to the problems in the related art has not been proposed yet.
Disclosure of Invention
Aiming at the problems in the related art, the invention provides a method for realizing uniqueness and accurate positioning of a logical volume name based on multi-bit coding, so as to overcome the technical problems in the prior related art.
Therefore, the invention adopts the following specific technical scheme:
the method for realizing the uniqueness and accurate positioning of the logical volume name based on the multi-bit coding comprises the following steps:
s1, acquiring the related information of the disk logical volume in the current required code from the asset database, and taking the related information of the disk logical volume as the input source of the code;
s2, performing 16-bit encoding and disassembling on each disk logical volume;
s3, combining the codes disassembled in the step S2 and generating a disk logical volume code;
and S4, disassembling the 16-bit codes into 6 groups of sub-codes, and reversely positioning the coded disk logical volume codes.
Further, the related information of the disk logical volume includes a host universal unique identification code, a controller universal unique identification code, a flash memory logical volume universal unique identification code, a common logical volume universal unique identification code, and an equipment file universal unique identification code.
Further, the 16-bit encoding and disassembling for each disk logical volume further includes the following steps:
s21, converting the universal unique identification code of the host into a 3-bit 62-system code through an F1 formula, and generating 1-3 bits of a 16-bit code to obtain the host code;
s22, converting the universal unique identification code of the controller into 3-bit 62-system code through an F1 formula, and generating 4-6 bits of 16-bit code to obtain the controller code;
s23, converting the universal unique identification code of the flash memory logical volume into a 3-bit 62-system code through an F1 formula, and generating 7-9 bits of a 16-bit code to obtain the flash memory logical volume code;
s24, loading the flash memory logical volume group onto the common logical volume group, generating the 10 th bit in the 16-bit code, and obtaining the acceleration ratio code;
s25, converting the common unique identification code of the common logical volume group into 3-bit 62-system code through an F1 formula, and generating 11-13 bits of 16-bit code to obtain the common logical volume group code;
and S26, converting the universal unique identification code of the equipment file into 3-bit 62-system code through an F1 formula, and generating 14-16 bits of 16-bit code to obtain the equipment file code.
Furthermore, the formula F1 means that a 3-bit code is generated through a universal unique identification code, and all hardware information can be inquired to obtain the universal unique identification code of the hardware information as a unique identifier;
the universal unique identification code is usually 32-bit characters, and is converted into a 3-bit 62-system code when the following algorithm is written.
Further, the specific algorithm implementation of the F1 formula is as follows:
firstly, removing symbols in the universal unique identification code;
circulating 32-bit characters in the universal unique identification code, and performing hash operation on each bit from the first bit;
converting the result into 62-system number according to the operation result;
and taking the first 3 bits of the obtained numerical value to return, and completing the conversion from the 32-bit universal unique identification code to the 3-bit 62-system code.
Further, the hash operation formula is as follows:
hash＝uint64(c)+(hash<<6)+(hash<<16)–hash。
further, combining the codes disassembled in step S2 to generate a disk logical volume code; further comprising the steps of:
s31, generating host codes, controller codes, flash memory logical volume group codes, acceleration ratio codes, common logical volume group codes and device file codes according to the steps from S21 to S26;
and S32, sequentially adding the host code, the controller code, the flash memory logical volume group code, the acceleration ratio code, the common logical volume group code and the equipment file code to obtain the code of the disk logical volume.
Further, the splitting of the 16-bit code into 6 groups of sub-codes and the reverse positioning of the coded logical volume code of the magnetic disk further include the following steps:
and S41, obtaining host information corresponding to the codes in the asset database according to the 1-3 bits of the codes, checking whether the universal unique identification codes of the host are consistent with the codes through an F1 formula, and positioning the disk logical volume of the host code group.
S42, obtaining controller information corresponding to the codes in the asset database according to the 4-6 bits of the codes, checking whether the universal unique identification codes and the codes of the controllers are consistent through an F1 formula, and positioning the logical volume of the disk of the controller code group;
s43, obtaining flash memory logical volume group information corresponding to the codes in the asset database according to the codes 7-9, verifying whether the flash memory logical universal unique identification codes and the codes are consistent through an F1 formula, and positioning the flash memory logical code groups by the magnetic disk logical volume;
s44, defining the acceleration ratio of the disk logical volume according to the 10 th bit of the code;
s45, obtaining common logical volume group information corresponding to the codes in the asset database according to the codes 11-13, checking whether the common unique identification codes and the codes of the common logical volume groups are consistent through an F1 formula, and positioning the magnetic disc logical volumes of the common logical volume groups;
and S46, obtaining the device file group information corresponding to the codes in the asset database according to the codes 14-16, determining whether the universal unique identification codes and the codes of the device files are consistent through an F1 formula, and positioning the disk logical volume of the device file code group.
The invention has the beneficial effects that:
1. the invention adopts 16-bit coding, ensures the uniqueness of the disk logical volume and has definite identification degree, can quickly know host information, controller information, common volume group information, flash memory volume group information, equipment file information and acceleration proportion information from the disk logical volume through the combination and disassembly of the coding, and can quickly trace the actual position of local storage when a fault occurs after the remote disk logical volume is mounted so as to solve the problem.
2. The code is 16 bits, 6 parts are totally divided, 5 parts acquire an algorithm for generating the code based on UUID, 3-bit 62-system codes are generated, the number of supported codes is as much as 20 to ten thousand, the configuration of a hardware architecture of a current storage end is far exceeded, and the coding requirement of the current industry on the disk logical volume is completely met; after 6 parts are combined, 16 bits are coded, so that the repetition rate is basically zero, and the uniqueness of the coding is ensured.
3. Under the great trend of a storage and computation separation architecture, a common phenomenon of using a remote logical volume exists in the current IT industry construction. A default wwn is used to ensure disk uniqueness but does not have the ability to reverse position. The 16-bit code of the invention ensures the uniqueness of the disk logical volume by the self-defined code and avoids the repeated conflict. Meanwhile, a reverse positioning mode is provided, and the source of the disk logical volume can be quickly positioned by combining the CMDB asset database.
4. In the construction of a data center, no matter the integration scheme planning in the early stage or the online operation and maintenance in the later stage, the convenience brought by the unclear disk logical volume coding cannot be separated. The purpose and the source of the disk logical volume of the IT data center can be traced, and the safety of the data center is ensured.
5. In the current IT storage architecture, SANServer is a mainstream storage providing mode; in the practical process of storage use, an architecture of calculation and storage separation is often adopted, and a disk logical volume provided by a storage layer is supplied to a calculation layer for use, so that the disk logical volume of the storage layer needs to ensure the unique property of the disk logical volume both locally and at a mapping end, the disk logical volume name generated by 16-bit coding ensures the uniqueness, the problem of collision of the disk logical volume at the local and the mapping end is avoided, meanwhile, in the process of mapping the disk logical volume to a remote end, the disk logical volume can be mapped by adopting the standard UUID of the disk, the core algorithm of the 16-bit coding can be adapted to the conversion corresponding logic of the UUID, and the UUID which accords with the UUID standard and has 16-bit coding characteristics can be generated for remote mapping to ensure the uniqueness of the disk logical volume name.
6. The disk logical volume is a storage unit with the minimum granularity used in the storage capacity supply, and is mounted into various file directory types for data storage in a physical environment or a current hot micro-service architecture; in a big data era, a huge amount of disk logical volumes are inevitably needed by mass data, the final attribution of the disk logical volumes is positioned in a plurality of disk logical volumes, the challenge faced by the existing storage architecture is that 16-bit codes generated by a method for realizing the uniqueness and accurate positioning of the logical volume name based on multi-bit codes can directly analyze the codes to generate disk attributes in a local environment according to the characteristic codes generated by a server, a mapping controller, a disk volume group, a disk type, a disk acceleration ratio and a disk equipment number to which the disk logical volumes belong, and accurately position the disk logical volumes according to the disk attributes, and at a far end, a mapped UUID is decompiled through a decompilation algorithm of a UD implanted 16 code, and the attribute information of the disk can also be analyzed to generate the accurate positioning of the disk. The positioning mechanism is provided, the difficulty of using and operating and maintaining the storage layer can be greatly simplified, the troubleshooting efficiency is improved, and the accurate positioning capability of the disk logical volume is ensured.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
FIG. 1 is a flow diagram of a method for implementing logical volume name uniqueness and accurate location based on multi-bit encoding in accordance with an embodiment of the present invention;
fig. 2 is a diagram illustrating correspondence between a logical volume unique code of a disk and a physical layer component location in a method for implementing logical volume name uniqueness and accurate location based on multi-bit coding according to an embodiment of the present invention.
Detailed Description
For further explanation of the various embodiments, the drawings which form a part of the disclosure and which are incorporated in and constitute a part of this specification, illustrate embodiments and, together with the description, serve to explain the principles of operation of the embodiments, and to enable others of ordinary skill in the art to understand the various embodiments and advantages of the invention, and, by reference to these figures, reference is made to the accompanying drawings, which are not to scale and wherein like reference numerals generally refer to like elements.
According to an embodiment of the invention, a method for realizing uniqueness and accurate positioning of a logical volume name based on multi-bit encoding is provided.
Referring now to the drawings and the detailed description, in accordance with an embodiment of the present invention, a method for implementing logical volume name uniqueness and accurate location based on multi-bit encoding, as shown in fig. 1, includes the following steps:
s1, obtaining the relevant information of the disk logical volume (LVtest01) in the current required code from the asset database (CMDB), and taking the relevant information of the disk logical volume as the input source of the code;
in one embodiment, the information related to the disk logical volume includes a host Universally Unique Identifier (UUID), a controller Universally Unique Identifier (UUID), a flash logical volume Universally Unique Identifier (UUID), a normal logical volume Universally Unique Identifier (UUID), and a device file Universally Unique Identifier (UUID).
In specific application, CMDB asset information of the disk logical volume is acquired, and assuming that multi-bit encoding is performed on the disk logical volume LVtest01, the relevant information of the disk logical volume LVtest01 which needs encoding currently is acquired from the asset database CMDB. The system comprises a host UUID, a controller UUID, a flash memory logical volume UUID, a common logical volume UUID and an equipment file UUID; the related asset information is used as an input source of the code in the subsequent coding process, and the code is generated after calculation.
CMDB asset information example:
| categories | Name (R) | UUID |
| Main unit | Host01 | 5ed4cd2c-0000-1000-0000-84139f318cf0 |
| Controller | Crontolle01 | 5d36c63c-0000-1000-0000-84139f318d20 |
| Flash memory logical volume group | Flashvg001 | 5d36d26c-0000-1000-0000-84139f318d60 |
| Common logical volume group | HDDvg001 | 4c4c4544-0030-4310-804d-c3c04f484732 |
| Device files | Tagetfile001 | 4c4c4544-0043-3110-8034-c7c04f444632 |
S2, as shown in FIG. 2, 16-bit encoding and disassembling are carried out on each disk logical volume;
in one embodiment, the performing 16-bit encoding disassembly on each disk logical volume further includes the following steps:
s21, converting the universal unique identification code of the host into a 3-bit 62-system code through an F1 formula, and generating 1-3 bits of a 16-bit code to obtain the host code;
in specific application, under a computing and storage separation architecture, storage usually adopts a Server-San mode, so that storage nodes exist, and the 1 st bit to the 3 rd bit of 16-bit coding encode host information. In step S1, the host information of the disk logical volume LVtest01 is obtained, and the UUID of the host is 5ed4cd2 c-0000-. An example of encoding is: B7Y.
S22, converting the universal unique identification code of the controller into 3-bit 62-system code through an F1 formula, and generating 4-6 bits of 16-bit code to obtain the controller code;
in a specific application, a plurality of controllers exist on each storage node, and each controller can manage disks on a group of storage nodes, so that the controllers are coded. 4 th bit to 6 th bit in the 16-bit code correspond to the code of the controller; in step S1, the controller information of the disk logical volume LVtest01 is obtained, and the UUID of the controller is 5d36c63 c-0000-. An example of encoding is: nYY
And (4) carrying out the binary coding of 62, wherein the maximum number of the supported controllers is 238 and 328.
S23, converting the universal unique identification code of the flash memory logical volume into a 3-bit 62-system code through an F1 formula, and generating 7-9 bits of a 16-bit code to obtain the flash memory logical volume code;
in specific applications, under the current situation of high performance applications, a flash memory device is generally configured on a storage node to speed up the performance of a magnetic disk, so as to meet the requirements of the applications on high bandwidth. In consideration of the situation, the flash memory logical volume group code is established; the 7 th bit to the 9 th bit in the 16-bit code correspond to the flash memory logical volume group code; in step S1, the flash memory logical volume group information of the disk logical volume LVtest01 is obtained, and the UUID of the flash memory logical volume group is 5d36d26 c-0000-. An example of encoding is: ZrT62, representing 238,328 most supported flash memory logical volume groups
S24, loading the flash memory logical volume group onto the common logical volume group, generating the 10 th bit in the 16-bit code, and obtaining the acceleration ratio code;
in a specific application, the storage acceleration technology is to use a flash memory logical volume group to load the flash memory logical volume group onto a common logical volume group, so that the speed of an IO can be increased by the flash memory logical volume group before reaching the common logical volume group, the speed increase ratio can be set, and the higher the ratio is, the stronger the speed increase effect is. The 10 th bit in the 16-bit code corresponds to the acceleration ratio code; the code adopts a 16-system, 0 represents no acceleration, 1 represents acceleration and 5 percent of the column bit, and so on. Acceleration scale coding such as 3;
s25, converting the common unique identification code of the common logical volume group into 3-bit 62-system code through an F1 formula, and generating 11-13 bits of 16-bit code to obtain the common logical volume group code;
in a specific application, the common logical volume group is a space for actually storing data on the storage node, and is associated with the flash memory logical volume group and the acceleration rate generation. The 11 th bit to the 13 th bit in the 16-bit code correspond to the common logical volume group code; in step S1, the normal logical volume group information of the disk logical volume LVtest01 is obtained, and the UUID of the normal logical volume group is 4c4c 4544-0030-. An example of encoding is: tk 4;
s26, converting the universal unique identification code of the equipment file into a 3-bit 62-system code through an F1 formula, and generating 14-16 bits of a 16-bit code to obtain an equipment file code;
in specific application, the device file refers to an alias of a device file that needs to be associated before the disk logical volume is mapped remotely, and is used for ensuring a mapping relationship between a computing side and a storage side. The 14 th bit to the 16 th bit in the 16-bit code correspond to the device file code; the device file information of the disk logical volume LVtest01 is obtained in step S1, and the UUID of the device file is 4c4c4544-0043-3110-8034-c7c04f 444632. An example of encoding is: unY are provided.
In one embodiment, the formula F1 refers to that a 3-bit code is generated by using a universal unique identifier, and all hardware information can query its own universal unique identifier as a unique identifier;
the universal unique identification code is usually a 32-bit character, and is converted into a 3-bit 62-system code when the following algorithm is written;
in one embodiment, the specific algorithm implementation of the F1 formula is as follows:
firstly, removing symbols in the universal unique identification code;
circulating 32-bit characters in the universal unique identification code, and performing hash (hash algorithm) operation on each bit from the first bit;
converting the result into 62-system number according to the operation result;
returning the first 3 bits of the obtained numerical value, and completing the conversion from the 32-bit universal unique identification code to the 3-bit 62-system code;
in one embodiment, the hash operation is as follows:
hash＝uint64(c)+(hash<<6)+(hash<<16)–hash；
s3, combining the codes disassembled in the step S2 and generating a disk logical volume code;
in one embodiment, the combining the codes disassembled in step S2 and generating the disk logical volume code; further comprising the steps of:
s31, generating host codes, controller codes, flash memory logical volume group codes, acceleration ratio codes, common logical volume group codes and device file codes according to the steps from S21 to S26;
and S32, sequentially adding the host code, the controller code, the flash memory logical volume group code, the acceleration ratio code, the common logical volume group code and the equipment file code to obtain the code of the disk logical volume.
In specific application, the code is formed by overlapping 6 parts, each part is formed by hundreds of combination modes, the final 16-bit code is consistent in superposition possibility and basically zero, and the uniqueness of the disk logical volume code is ensured.
Such as B7 YnYZrT 5Tk4 unY.
S4, the 16-bit code seen above is decomposed into 6 groups of sub-codes as B7 YnYZrT 5Tk4unY, and the reverse orientation code is the disk logical volume code of B7 YnYZrT 5Tk4 unY.
In specific application, at a computing end, checking 16-bit codes mapped to local disk logical volume groups, dividing the codes into 6 groups of codes, and quickly positioning host information, controller information, flash memory logical volume groups and common logical volume groups from the disk logical volumes;
in one embodiment, the splitting of the seen 16-bit code, such as B7YnYYZrT5Tk4 unry, into 6 sets of sub-codes, and the reverse positioning of the disk logical volume code encoded as B7YnYYZrT5Tk4 unry, further comprises the steps of:
s41, the 1-3 bit of the code is B7Y, the host information corresponding to the code in the asset database is obtained according to the code, whether the universal unique identification code of the host is consistent with the code is checked through an F1 formula, and the disk logical volume positioning is carried out on the host code group;
| categories | Name (R) | Encoding | UUID |
| Main unit | Host01 | B7Y | 5ed4cd2c-0000-1000-0000-84139f318cf0 |
S42, the 4-6 bits of the code are nYY, the controller information corresponding to the code in the asset database is obtained according to the code, whether the universal unique identification code of the controller is consistent with the code is verified through an F1 formula, and the disk logical volume positioning is carried out on the controller code group;
| categories | Name (R) | Encoding | UUID |
| Controller | Crontoller01 | nYY | 5d36c63c-0000-1000-0000-84139f318d20 |
S43, the number of the coded 7-9 is ZrT, the flash memory logical volume group information corresponding to the codes in the asset database is obtained according to the codes, whether the flash memory logical universal unique identification codes and the codes are consistent or not can be verified through an F1 formula, and the magnetic disk logical volume positioning is carried out on the flash memory logical code group;
s44, the 10 th bit of the code is 5, and according to the coding rule, the acceleration ratio of the B7 YnYZrT 5Tk4unY disk logical volume can be positioned and coded to be 25%;
s45, the 11-13 coded bits are Tk4, common logical volume group information corresponding to the codes in the asset database is obtained according to the codes, whether the common unique identification codes and the codes of the common logical volume groups are consistent or not is verified through an F1 formula, and the magnetic disk logical volume positioning is carried out on the common logical volume groups;
and S46, wherein the 14-16 bits of the code are unY, the information of the device file group corresponding to the code in the asset database is obtained according to the code, whether the universal unique identification code and the code of the device file are consistent or not is determined through an F1 formula, and the positioning of the disk logical volume is carried out on the device file code group.
In summary, by means of the above technical solution of the present invention, the present invention adopts 16-bit codes, so that there is a clear degree of identification while ensuring the uniqueness of the disk logical volume, and through the combined disassembly of the codes, host information, controller information, common volume group information, flash volume group information, device file information, and acceleration ratio information from the disk logical volume can be quickly known. When a fault occurs after the remote disk logical volume is mounted, the actual position of local storage can be quickly traced back so as to solve the problem, 16 bits are coded, 6 parts are totally divided, 5 parts acquire a coding algorithm based on UUID generation, 3-bit 62-system codes are generated, the number of each code support is up to 20 to ten thousands, the hardware architecture configuration of the current storage end is far exceeded, and the coding requirements of the current industry on the disk logical volume are completely met; after the 6 parts are combined, 16-bit coding ensures that the repetition rate is basically zero, ensures the uniqueness of the coding, and has a common phenomenon of using a remote logical volume in the current IT industry construction under the large trend of a storage and calculation separation architecture. The default WWN is used to guarantee disk uniqueness, but does not have the ability to reverse locate. The 16-bit code of the invention ensures the uniqueness of the disk logical volume by the self-defined code and avoids the repeated conflict. Meanwhile, a reverse positioning mode is provided, the source of the disk logical volume can be quickly positioned by combining the CMDB asset database, and the convenience brought by the clear disk logical volume coding cannot be separated in the data center construction no matter the integration scheme planning in the early stage or the online operation and maintenance in the later stage. The purpose and the source of a disk logical volume of an IT data center can be traced, so that the safety of the data center is ensured in the current IT storage architecture, and the SANServer provides a mainstream storage mode; in the practical process of storage use, an architecture of calculation and storage separation is often adopted, and a disk logical volume provided by a storage layer is supplied to a calculation layer for use, so that the disk logical volume of the storage layer needs to ensure the unique property of the disk logical volume both locally and at a mapping end, the disk logical volume name generated by 16-bit coding ensures the uniqueness, the conflict problem of the disk logical volume at the local and the mapping end is avoided, meanwhile, in the process of mapping the disk logical volume to a far end, the disk logical volume can be mapped by adopting a standard UUID possessed by a disk, a core algorithm of 16-bit coding can be adapted to the conversion corresponding logic of the UUID, and the UUID which accords with the UUID standard and has 16-bit coding characteristics can be generated for remote mapping to ensure the uniqueness of the disk logical volume name; the disk logical volume is a storage unit with the minimum granularity used in the storage capacity supply, and is mounted into various file directory types for data storage in a physical environment or a current hot micro-service architecture; in the big data era, a great amount of disk logical volumes are necessary for mass data, the ultimate attribution of the disk logical volumes is positioned in a plurality of disk logical volumes, the challenge of the existing storage architecture is faced, and a 16-bit code generated by a method for realizing the uniqueness and accurate positioning of the logical volume name based on multi-bit codes is generated according to a server to which the disk logical volumes belong, a mapping controller, a disk volume group, a disk type, a disk acceleration ratio and a disk equipment number. In a local environment, the encoding can be directly analyzed to generate the disk attribute, the disk logical volume can be accurately positioned according to the disk attribute, the mapped UUID is decompiled through a decompiling algorithm of embedding 16 encoding into the UDEV at a far end, the attribute information of the disk can also be analyzed and generated, and the disk can be accurately positioned.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (8)
1. The method for realizing the uniqueness and accurate positioning of the logical volume name based on the multi-bit coding is characterized by comprising the following steps of:
s1, acquiring the related information of the disk logical volume in the current required code from the asset database, and taking the related information of the disk logical volume as the input source of the code;
s2, performing 16-bit encoding and disassembling on each disk logical volume;
s3, combining the codes disassembled in the step S2 and generating a disk logical volume code;
and S4, disassembling the 16-bit codes into 6 groups of sub-codes, and reversely positioning the coded disk logical volume codes.
2. The method for realizing uniqueness and accurate positioning of logical volume names based on multi-bit coding according to claim 1, wherein the related information of the disk logical volume comprises a host universal unique identification code, a controller universal unique identification code, a flash memory logical volume universal unique identification code, a common logical volume universal unique identification code and a device file universal unique identification code.
3. The method for realizing uniqueness and accurate positioning of logical volume names based on multi-bit encoding according to claim 1, wherein the 16-bit encoding disassembly of each disk logical volume further comprises the following steps:
s21, converting the universal unique identification code of the host into a 3-bit 62-system code through an F1 formula, and generating 1-3 bits of a 16-bit code to obtain the host code;
s22, converting the universal unique identification code of the controller into 3-bit 62-system code through an F1 formula, and generating 4-6 bits of 16-bit code to obtain the controller code;
s23, converting the universal unique identification code of the flash memory logical volume into a 3-bit 62-system code through an F1 formula, and generating 7-9 bits of a 16-bit code to obtain the flash memory logical volume code;
s24, loading the flash memory logical volume group onto the common logical volume group, generating the 10 th bit in the 16-bit code, and obtaining the acceleration ratio code;
s25, converting the common unique identification code of the common logical volume group into 3-bit 62-system code through an F1 formula, and generating 11-13 bits of 16-bit code to obtain the common logical volume group code;
and S26, converting the universal unique identification code of the equipment file into 3-bit 62-system code through an F1 formula, and generating 14-16 bits of 16-bit code to obtain the equipment file code.
4. The method for realizing uniqueness and accurate positioning of the name of the logical volume based on the multi-bit code according to claim 1, wherein the formula F1 refers to that 3-bit codes are generated through universal unique identification codes, and all hardware information can query own universal unique identification codes as unique identifiers;
the universal unique identification code is usually 32-bit characters, and is converted into a 3-bit 62-system code when the following algorithm is written.
5. The method for realizing uniqueness and accurate positioning of the logical volume name based on the multi-bit code according to claim 4, wherein the specific algorithm implementation manner of the F1 formula is as follows:
firstly, removing symbols in the universal unique identification code;
circulating 32-bit characters in the universal unique identification code, and performing hash operation on each bit from the first bit;
converting the result into 62-system number according to the operation result;
and taking the first 3 bits of the obtained numerical value to return, and completing the conversion from the 32-bit universal unique identification code to the 3-bit 62-system code.
6. The method for implementing logical volume name uniqueness and accurate positioning based on multi-bit encoding as claimed in claim 5, wherein the hash operation formula is as follows:
hash＝uint64(c)+(hash<<6)+(hash<<16)–hash。
7. the method for implementing logical volume name uniqueness and accurate location based on multi-bit encoding according to claim 1, wherein the codes disassembled in step S2 are combined to generate a disk logical volume code; further comprising the steps of:
s31, generating host codes, controller codes, flash memory logical volume group codes, acceleration ratio codes, common logical volume group codes and device file codes according to the steps from S21 to S26;
and S32, sequentially adding the host code, the controller code, the flash memory logical volume group code, the acceleration ratio code, the common logical volume group code and the equipment file code to obtain the code of the disk logical volume.
8. The method for realizing uniqueness and accurate positioning of a logical volume name based on multi-bit codes according to claim 1, wherein the step of splitting the 16-bit codes into 6 groups of sub-codes and reversely positioning the coded disk logical volume codes further comprises the following steps:
and S41, obtaining host information corresponding to the codes in the asset database according to the 1-3 bits of the codes, checking whether the universal unique identification codes of the host are consistent with the codes through an F1 formula, and positioning the disk logical volume of the host code group.
S42, obtaining controller information corresponding to the codes in the asset database according to the 4-6 bits of the codes, checking whether the universal unique identification codes and the codes of the controllers are consistent through an F1 formula, and positioning the logical volume of the disk of the controller code group;
s43, obtaining flash memory logical volume group information corresponding to the codes in the asset database according to the 7-9 bits of the codes, verifying whether the flash memory logical universal unique identification codes and the codes are consistent through an F1 formula, and positioning the flash memory logical code groups by the magnetic disk logical volume;
s44, defining the acceleration ratio of the disk logical volume according to the 10 th bit of the code;
s45, obtaining common logical volume group information corresponding to the codes in the asset database according to the 11-13 bits of the codes, checking whether the common unique identification codes and the codes of the common logical volume groups are consistent through an F1 formula, and positioning the common logical volume groups on the magnetic disk logical volume;
and S46, obtaining the device file group information corresponding to the codes in the asset database according to the codes 14-16, determining whether the universal unique identification codes and the codes of the device files are consistent through an F1 formula, and positioning the disk logical volume of the device file code group.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110947342.4A CN113655961B (en) | 2021-08-18 | 2021-08-18 | Method for realizing uniqueness and accurate positioning of logical volume name based on multi-bit coding |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110947342.4A CN113655961B (en) | 2021-08-18 | 2021-08-18 | Method for realizing uniqueness and accurate positioning of logical volume name based on multi-bit coding |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113655961A true CN113655961A (en) | 2021-11-16 |
| CN113655961B CN113655961B (en) | 2022-09-09 |
Family
ID=78480823
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110947342.4A Active CN113655961B (en) | 2021-08-18 | 2021-08-18 | Method for realizing uniqueness and accurate positioning of logical volume name based on multi-bit coding |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113655961B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6457139B1 (en) * | 1998-12-30 | 2002-09-24 | Emc Corporation | Method and apparatus for providing a host computer with information relating to the mapping of logical volumes within an intelligent storage system |
| CN101097501A (en) * | 2006-06-29 | 2008-01-02 | 国际商业机器公司 | Method and system for repositioning logical volume |
| CN102968422A (en) * | 2011-08-31 | 2013-03-13 | 中国航天科工集团第二研究院七○六所 | System and method for controlling streaming data storage |
| WO2015020636A1 (en) * | 2013-08-06 | 2015-02-12 | Hitachi, Ltd. | Method and apparatus of storage system which stores information for relationship between logical volumes and operations |
| CN106168884A (en) * | 2011-08-26 | 2016-11-30 | 威睿公司 | Access the computer system of object storage system |
-
2021
- 2021-08-18 CN CN202110947342.4A patent/CN113655961B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6457139B1 (en) * | 1998-12-30 | 2002-09-24 | Emc Corporation | Method and apparatus for providing a host computer with information relating to the mapping of logical volumes within an intelligent storage system |
| CN101097501A (en) * | 2006-06-29 | 2008-01-02 | 国际商业机器公司 | Method and system for repositioning logical volume |
| CN106168884A (en) * | 2011-08-26 | 2016-11-30 | 威睿公司 | Access the computer system of object storage system |
| CN102968422A (en) * | 2011-08-31 | 2013-03-13 | 中国航天科工集团第二研究院七○六所 | System and method for controlling streaming data storage |
| WO2015020636A1 (en) * | 2013-08-06 | 2015-02-12 | Hitachi, Ltd. | Method and apparatus of storage system which stores information for relationship between logical volumes and operations |
Non-Patent Citations (1)
| Title |
|---|
| 雷军程等: "数据库主键生成策略研究", 《计算机时代》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113655961B (en) | 2022-09-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10291265B2 (en) | Accelerated Galois field coding for storage systems | |
| US10505671B2 (en) | Polar code encoding method and device | |
| CN105378676B (en) | The simple correcting and eleting codes locally generated | |
| RU2501072C2 (en) | Distributed storage of recoverable data | |
| Duminuco et al. | A practical study of regenerating codes for peer-to-peer backup systems | |
| CA1284228C (en) | Byte write error code method and apparatus | |
| CN111149093A (en) | Data coding, decoding and repairing method of distributed storage system | |
| CN105426413A (en) | Coding method and device | |
| CN106874140B (en) | Data storage method and device | |
| CN105808170B (en) | A kind of RAID6 coding methods that can repair single disk error | |
| CN104866601A (en) | Serial number generating method and device | |
| Hollmann | Storage codes—Coding rate and repair locality | |
| CN109661665B (en) | Standard and non-standard decentralized storage network data access | |
| Esmaili et al. | The core storage primitive: Cross-object redundancy for efficient data repair & access in erasure coded storage | |
| CN113655961B (en) | Method for realizing uniqueness and accurate positioning of logical volume name based on multi-bit coding | |
| CN105117303B (en) | A kind of method and apparatus that data are restored | |
| CN114510368A (en) | Coding and decoding acceleration method and system based on RS erasure codes | |
| US20180246784A1 (en) | Data integrity detection and correction | |
| CN110704232B (en) | Method, device and equipment for repairing failed node in distributed system | |
| CN107665152B (en) | Decoding method of erasure code | |
| Chen et al. | A new Zigzag MDS code with optimal encoding and efficient decoding | |
| US10506045B2 (en) | Memory access using deterministic function and secure seed | |
| US10334045B2 (en) | Indicating multiple encoding schemes in a dispersed storage network | |
| CN110287716B (en) | Data storage method and device | |
| Zhang et al. | SA-RSR: A read-optimal data recovery strategy for XOR-coded distributed storage systems |
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 |