CN111159119A - Log management method, system and related components of SAN storage system - Google Patents
Log management method, system and related components of SAN storage system Download PDFInfo
- Publication number
- CN111159119A CN111159119A CN201911386482.8A CN201911386482A CN111159119A CN 111159119 A CN111159119 A CN 111159119A CN 201911386482 A CN201911386482 A CN 201911386482A CN 111159119 A CN111159119 A CN 111159119A
- Authority
- CN
- China
- Prior art keywords
- log
- volume
- storage system
- block
- management method
- 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.)
- Withdrawn
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/17—Details of further file system functions
- G06F16/1734—Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
-
- 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/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
Abstract
The application discloses a log management method of an SAN storage system, which comprises the following steps: creating a log volume by using a back-end hard disk and a storage pool; recording logs through a log volume; and mapping the log volume to the terminal equipment so as to manage the log volume according to the target protocol through the terminal equipment. According to the method and the device, the log volume created by the rear-end hard disk and the storage pool is used as a log storage medium, the storage space is large, the storage time is not limited, the log storage function with large capacity and high performance can be realized, the log volume is mapped to the terminal equipment, so that the terminal equipment can inquire and analyze the log volume through a protocol and perform management operation, namely, the data of the falling disk is managed through the terminal equipment, and compared with the prior art, the method and the device have the advantages of higher response speed and higher inquiry speed. The application also discloses a log management device, electronic equipment and a computer readable storage medium of the SAN storage system, which have the beneficial effects.
Description
Technical Field
The present application relates to the field of storage systems, and in particular, to a log management method and system for a SAN storage system, and related components.
Background
In an SAN (Storage Area Network) Storage system, in order to analyze host-side IO characteristics and track an IO processing procedure, information of each IO, including a read/write type, a start address, a length, an initiation time, a completion time, and the like, needs to be recorded. The SAN storage system has high IO receiving and processing speed, which is up to hundreds of thousands of iops, needs to record all IO logs in detail for a long time, and needs a large storage space. The existing SAN storage system generally uses a memory to store IO information, because the memory is limited, the amount and duration of the IO information which can be stored are also limited, IO logs can be further inquired and analyzed only by being exported through management software of the system, files need to be encapsulated again for export, the management channel rate of the system is low, generally a hundred megabytes or gigabytes network, and therefore the inquiry efficiency is low.
Therefore, how to provide a solution to the above technical problem is a problem that needs to be solved by those skilled in the art.
Disclosure of Invention
The application aims to provide a log management method, a log management device, an electronic device and a computer-readable storage medium of an SAN storage system, which can realize large-capacity and high-performance log storage and map a log volume to a terminal device so that the terminal device can perform management operations such as query and analysis on the log volume through a protocol, namely, the terminal device manages the data of a dropped disk.
In order to solve the above technical problem, the present application provides a log management method for an SAN storage system, including:
creating a log volume by using a back-end hard disk and a storage pool;
logging by the log volume;
and mapping the log volume to terminal equipment so as to manage the log volume according to a target protocol through the terminal equipment.
Preferably, before creating the journal volume by using the backend hard disk and the storage pool, the journal management method further includes:
calculating the size of a log volume according to the log information of the SAN storage system;
correspondingly, the process of creating the journal volume by using the backend hard disk and the storage pool specifically includes:
and creating a journal volume according to the size of the journal volume by using a back-end hard disk and a storage pool.
Preferably, the process of mapping the log volume to the terminal device specifically includes:
and mapping the log volume as a SCSI LUN to a server host.
Preferably, the log volume includes a superblock and a plurality of log spaces divided by log types, and the log space corresponding to each log type includes a plurality of blocks;
accordingly, the process of creating a log volume includes:
initializing parameters of the super block;
and distributing the log space for each log type, and updating the parameters in the super block.
Preferably, the log management method further includes:
determining a cache region corresponding to the log type in a memory;
the process of recording logs by the log volume specifically includes:
storing the log of the current log type into a corresponding cache region;
when the log in the cache region meets the condition of disk dropping, the log in the cache region is written into the corresponding block in a flashing mode, and the block information of the block is updated.
Preferably, the process of managing the log volume according to the target protocol by the terminal device includes:
receiving an input instruction sent by the terminal equipment, wherein the input instruction comprises a log type mark number;
determining a target block in a target log volume according to the log type mark number;
and reading and analyzing all logs in the target block for management.
Preferably, the target protocol includes an FCP protocol or an iSCSI protocol.
In order to solve the above technical problem, the present application further provides a log management apparatus for an SAN storage system, including:
the creating module is used for creating the log volume by utilizing the back-end hard disk and the storage pool;
the recording module is used for recording the log through the log volume;
and the management module is used for mapping the log volume to the terminal equipment so as to manage the log volume according to a target protocol through the terminal equipment.
In order to solve the above technical problem, the present application further provides an electronic device, including:
a memory for storing a computer program;
a processor for implementing the steps of the log management method of the SAN storage system as described in any of the above when executing the computer program.
To solve the above technical problem, the present application further provides a computer-readable storage medium having a computer program stored thereon, where the computer program is executed by a processor to implement the steps of the log management method of the SAN storage system according to any one of the above.
The application provides a log management method of an SAN storage system, which utilizes a log volume created by a rear-end hard disk and a storage pool as a log storage medium, has large storage space and no limitation of storage duration, can realize a large-capacity and high-performance log storage function, and maps the log volume to a terminal device, so that the terminal device can perform management operations such as query and analysis on the log volume through a protocol, namely manage data of a dropped disk through the terminal device. The application also provides a log management device, electronic equipment and a computer readable storage medium of the SAN storage system, and the log management device, the electronic equipment and the computer readable storage medium have the same beneficial effects as the log management method.
Drawings
In order to more clearly illustrate the embodiments of the present application, the drawings needed for 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 application, and that other drawings can be obtained by those skilled in the art without inventive effort.
FIG. 1 is a flowchart illustrating the steps of a log management method for a SAN storage system according to the present application;
FIG. 2 is a schematic structural diagram of a journal volume provided in the present application;
FIG. 3 is a schematic structural diagram of a journal management apparatus of a SAN storage system according to the present application;
fig. 4 is a schematic structural diagram of an electronic device provided in the present application.
Detailed Description
The core of the application is to provide a log management method, a log management device, an electronic device and a computer-readable storage medium of an SAN storage system, which can realize large-capacity and high-performance log storage and map a log volume to a terminal device so that the terminal device can perform management operations such as query and analysis on the log volume through a protocol, namely, the terminal device manages the data of a dropped disk.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in 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 obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flowchart illustrating steps of a log management method according to the present application, where the log management method includes:
s101: creating a log volume by using a back-end hard disk and a storage pool;
specifically, in the SAN storage system, a backend hard disk and a storage pool are used to create and allocate one or more logical volumes dedicated to log storage by using the backend hard disk and the storage pool, the logical volumes are called log volumes, and the log storage is realized on the backend hard disk and the storage pool, so that the large-capacity and high-performance log storage is realized.
Specifically, before executing this step, an operation of calculating the size of the log volume according to the log information of the SAN storage system may be further included, so that the log volume is created according to the size of the log volume. The log information may include, but is not limited to, the number of log types, log generation frequency for each log type, log size, storage age, and other log information, from which the size of the log volume may be calculated. For example, if the log size of a certain type log LogA is 128 bytes, the generation frequency is 10000 logs per second, and the storage time is 10 days, the number of log pieces required for storing the type log is 10000 × 3600 × 24 × 10 — 8640000000 logs, 2MB is required for each block, the size of a block information block BlockHeader is subtracted from each block (aligned to 512B, for example, 4KB), the rest of the log is stored in 128 byte alignment, each block can store 16352 logs, 8640000000/16352 — 528376 blocks are required for the type log, and 1032GB of log space is occupied.
Specifically, referring to fig. 2, the space of each Log volume includes a SuperBlock and a plurality of Log spaces divided by Log types, such as Log space Logspace for type a, Log space for type B, Log space for type C, and the like in fig. 2. The log space of each log type is divided into a plurality of blocks LogBlock with the same size, and each LogBlock comprises a block information block Block header and a log array.
The size of the SuperBlock is aligned with the size of the block by 512 bytes, the SuperBlock comprises a metadata version number MetaVersion, a feature identifier MagicId, a block size Block size, a super Block content check SuperChecksum and log Info of each log type information array, and each item of the log type information array comprises whether the log type log enables LogTypeUsed, a type name LogTypeName, a type identifier LogTypeId, a log space starting address LogAreaStart and a length LogAreaSize, a length LogEntrySize fixed by each log and an update version number LogTypeVersion of the log. The BlockHeader comprises a metadata version number MetaVersion, a type identification number LogTypeId, an update version number LogTypeVersion of the type log, a sequence number BlockIndex of the block in a log space, a number LogEntryIndex of a first log in the block, a log number LogEntryCount included in the block, and a check value BlockCheckSum.
The LogTypeVersion of the log is used for identifying whether the log of one block is valid or not when the log is read, and the log is considered to be valid only if the LogTypeVersion value in the LogInfo of the information array of the SuperBlock is the same as the LogTypeVersion value in the blockHeader. In the use period of the storage system, LogTypeVersion of the log of the same type should be unique during each registration, for example, each increment is used to accelerate the initialization of metadata, and avoid initializing LogTypeVersion and the like to be invalid for each BlockHeader of LogBlock of the log space of the log when the log type is registered for initialization.
After determining the structure of the log volume, initializing various parameters of SuperBlock of the log volume, including a version number, a feature identifier, a block size, a SuperBlock content check and a log type information array, wherein the version number is used for marking and identifying a metadata layout format of the log volume, the feature identifier is a fixed and unusual byte array, the block size should be larger than the maximum size of a log to be recorded by a system, for example, 2MB, and a value of whether each item in the log type information array is enabled or not is initialized to be disabled.
Registering each log type in the SAN storage system, transmitting a log type name LogTypeName, a log fixed length LogEntrySize and the number of log pieces which can be stored in a log space during registration, calculating the size of the required log space according to the incoming parameters and the format of the log space, searching and allocating a free unused space as the log space of the log of the type according to the log spaces of all the log types which are started in the log type information array in the SuperBlock, and traversing each item in the log type information array, searching the log type information of the unopened item for recording the log of the type, and the combination of the serial number in the log type information array where the item of information is located and the log volume ID is used as the type mark number LogTypeId of the log type, wherein the journal volume ID is a unique number of the journal volume in the system, thereby ensuring that the type-tag numbers of all journal types of all journal volumes within the SAN storage system are unique.
Specifically, taking the log type a as an example, the registration process of each log type is described as follows:
distributing a Log space to be a Log space for type A for the Log type A, and updating related information in an information array LogInfo [0] corresponding to the Log type A in SuperBlock:
s1011: setting LogTypeUused as enabled;
s1012: setting the LogTypeName as a value for registering an incoming parameter LogTypeName, which may be a;
s1013: setting the logTypeId as the combination of the sequence number (namely 0) in the logInfo and the current log volume ID;
the method comprises the steps that a journal volume ID is a unique number of a current journal volume in an SAN storage system, so that the type mark numbers of all journal types of all journal volumes in the SAN storage system are unique;
s1014: setting the starting address and the length of a Log space as the starting address and the length of a Log space for type A;
s1015: setting the fixed length LogEntrySize of each log as the value of an incoming parameter LogEntrySize;
s1016: configuring LogTypeVersion of the log type A;
specifically, it is to be ensured that each registration of the same LogTypeId in the SAN storage system in the usage cycle of the SAN storage system is to update LogTypeVersion to a unique value, for example, the last registered value of LogTypeVersion corresponding to each LogTypeId is recorded, and when re-registration is performed, the last registered value is incremented by 1 to be used as the value of updated version number LogTypeVersion of the type log registered this time.
It is understood that the operations of S201 to S206 are repeated to complete the registration of all log types in the SAN storage system, i.e., to complete the construction of the current log volume.
S102: recording logs through a log volume;
specifically, after each log type is registered, at least one cache region with the same block size as the log type is allocated to each registered log type in the memory according to the LogTypeId, and when the log is recorded, the log content is written into the corresponding cache region and the log is submitted. The log space of each log type is used sequentially from the first block, and the next block is allocated after one block is filled with the log. The blocks in use are allocated in order from the first log space of the log array.
After all logs in a cache area are filled, namely the cache area is full, namely the condition of disk falling is met, the logs in the cache area are written on a log book in a brushing mode, and the content of a Block Header in a corresponding block is updated, wherein the method for updating the content of the Block Header comprises the following steps:
s1021: set MetaVersion to the value of MetaVersion in SuperBlock;
s1022: setting the LogTypeId as the LogTypeId of the log of the type;
s1023: the LogTypeVersion is set to the value of the LogTypeVersion of the corresponding LogInfo in the SuperBlock.
S1024: setting the sequence number Block index of the block in the log space corresponding to the type;
s1025: setting the number LogEntryIndex of the first log in the block, wherein the log number is a globally increasing number of the log;
s1026: setting the number of log entries LogEntryCount included in the block and the number of log entries actually included in the block, which are generally the number of log entries that can be stored in the block;
s1027: setting the check value BlockCheckSum of the block, calculating the check including all log contents and the data in the BlockHeader except BlockCheckSum itself, and selecting the check method, such as CRC 32.
S103: and mapping the log volume to the terminal equipment so as to manage the log volume according to the target protocol through the terminal equipment.
Specifically, the log volume is mapped to the terminal device, and the terminal device can manage the log volume through protocols such as FCP, iSCSI and the like, respond to the speed block and improve the query speed.
Further, the terminal device may refer to a server host or a local terminal device, and when the terminal device is the server host, the log volume is mapped to the server host as an SCSI LUN, and the server host may access the log volume in a block device manner through protocols such as FCP, iSCSI, and the like, thereby implementing high-performance reading of the log volume data at the server host and parsing according to metadata and data format of the log volume. In order to protect the integrity of the log volume and prevent the server host side from writing data to the log volume to destroy the log, the SAN storage system only accepts the SCSI read command of the server host and rejects the SCSI write command for the mapped log volume.
Specifically, the log read query process is explained as follows:
s1031: receiving an input instruction sent by a user through terminal equipment;
the input instruction comprises a target log type identification number LogTypeId and a log type name LogTypeName, and the log of the type is traversed;
s1032: calculating or inquiring a corresponding log volume Id according to the LogTypeId;
s1033: reading a super block of the target log volume according to the log volume Id, and checking whether the parameter of the super block is effective to judge whether the log volume is effective;
the effective judging method comprises the following steps: the MagicId is a preset fixed value, the content structure of the super block is determined according to MetaVersion, the content of the super block is verified according to a preset verification method of the version, and the result is the same as that of SuperChecksum;
s1034: calculating or searching a sequence number of the log type in a corresponding log type information array in the super block according to the LogTypeId, and inquiring related information of a target log type according to the sequence number, wherein the following conditions are met and the method is considered to be effective: the LogTypeUsed value is enabled, the LogTypeName is the same as the LogTypeName in the input instruction, and the LogTypeId is the same as the LogTypeId in the input instruction
S1035: determining a starting address and length of a log space and an address of a first log block according to LogAreaStart and LogAreaSize of log type information, determining the size of the block according to a super block Block Size, and reading the first block;
s1036: checking the validity of block data;
wherein, the following conditions are satisfied, and the judgment can be made as effective: calculating a block data check value to be the same as a Block checksum in a Block Header, a MetaVersion in the Block Header to be the same as a MetaVersion value of a super block, a LogTypeId in the Block Header to be the same as a LogTypeId in an input command, a LogTypeVersion in the Block Header to be the same as a LogTypeVersion value of log information of the type in the super block, a LogIndex in the Block Header to be the same as a sequence number of the block in a log space of the type, a LogEntryIndex in the Block Header to be adjacent to a sequence number of a last log of a last block in an ascending manner, and if the block is a first block currently, the LogEntryIndex should be 0;
s1037: and reading and analyzing all logs in the block for analysis, wherein the number of the logs in the log block is LogEntryCount of a Block Header, the size of the log is LogEntrySize of the type of log information in the super block, the format content of the log is defined by a log recorder and can be determined according to LogTypeId.
The scheme provided by the embodiment is suitable for reading and querying on the SAN storage system, is also suitable for reading and querying from the server host end after the log volume is mapped to the server host through the SAN protocol, and can perform reading and querying of written logs in the log recording process.
In summary, the present application adopts a logical volume created by a back-end hard disk and a storage pool as a log storage medium in an SAN storage system, designs a method for supporting multiple log records, fast initializing logs, and checking log validity in a reasonable log structure, and can map a log volume to a server host, query logs from the server host, and perform fast and efficient log access and analysis by using the computing power of the server host.
As can be seen, in the embodiment, the log volume created by the rear-end hard disk and the storage pool is used as the log storage medium, the storage space is large, and there is no limitation on the storage duration, so that a large-capacity and high-performance log storage function can be realized, and the log volume is mapped to the terminal device, so that the terminal device performs management operations such as query and analysis on the log volume through a protocol, that is, manages the data of a dropped disk through the terminal device.
Referring to fig. 3, fig. 3 is a schematic structural diagram of a log management apparatus of a SAN storage system provided in the present application, including:
the creating module 1 is used for creating a log volume by using a back-end hard disk and a storage pool;
the recording module 2 is used for recording logs through a log volume;
and the management module 3 is used for mapping the log volume to the terminal equipment so as to manage the log volume according to the target protocol through the terminal equipment.
As can be seen, in the embodiment, the log volume created by the rear-end hard disk and the storage pool is used as the log storage medium, the storage space is large, and there is no limitation on the storage duration, so that a large-capacity and high-performance log storage function can be realized, and the log volume is mapped to the terminal device, so that the terminal device performs management operations such as query and analysis on the log volume through a protocol, that is, manages the data of a dropped disk through the terminal device.
As a preferred embodiment, the log management apparatus further includes:
the calculation module is used for calculating the size of the log volume according to the log information of the SAN storage system;
accordingly, the creating module 1 is specifically configured to:
and creating the journal volume according to the size of the journal volume by using the back-end hard disk and the storage pool.
As a preferred embodiment, the management module 3 is specifically configured to:
the log volume is mapped to the server host as a SCSI LUN.
As a preferred embodiment, the log volume includes a super block and a plurality of log spaces divided by log types, and the log space corresponding to each log type includes a plurality of blocks;
accordingly, the process of creating a log volume includes:
initializing parameters of the super block;
and allocating log space for each log type and updating parameters in the superblock.
As a preferred embodiment, the log management apparatus further includes:
the allocation module is used for determining a cache region corresponding to the log type in the memory;
the recording module 2 specifically includes:
the cache unit is used for storing the logs of the current log type into the corresponding cache region;
and the flushing unit is used for flushing the log in the cache area into the corresponding block and updating the block information of the block when the log in the cache area meets the disk-dropping condition.
As a preferred embodiment, the management module 3 specifically includes:
the receiving unit is used for receiving an input instruction sent by the terminal equipment, and the input instruction comprises a log type mark number;
the determining unit is used for determining a target block in the target log volume according to the log type mark number;
and the processing unit is used for reading and analyzing all logs in the target block so as to manage.
In a preferred embodiment, the target protocol comprises the FCP protocol or the iSCSI protocol.
On the other hand, the present application also provides an electronic device, as shown in fig. 4, which shows a schematic structural diagram of an electronic device according to an embodiment of the present application, where the electronic device 2100 according to the embodiment may include: a processor 2101 and a memory 2102.
Optionally, the electronic device may further comprise a communication interface 2103, an input unit 2104 and a display 2105 and a communication bus 2106.
The processor 2101, the memory 2102, the communication interface 2103, the input unit 2104, the display 2105, and the like communicate with each other via the communication bus 2106.
In the embodiment of the present application, the processor 2101 may be a Central Processing Unit (CPU), an application specific integrated circuit (asic), a digital signal processor, an off-the-shelf programmable gate array (fpga) or other programmable logic device (plc).
The processor may call a program stored in the memory 2102. Specifically, the processor may perform operations performed on the electronic device side in the following embodiments of the log management method of the SAN storage system.
The memory 2102 stores one or more programs, which may include program code including computer operating instructions, and in this embodiment, at least one program for implementing the following functions is stored in the memory:
creating a log volume by using a back-end hard disk and a storage pool;
recording logs through a log volume;
and mapping the log volume to the terminal equipment so as to manage the log volume according to the target protocol through the terminal equipment.
As can be seen, in the embodiment, the log volume created by the rear-end hard disk and the storage pool is used as the log storage medium, the storage space is large, and there is no limitation on the storage duration, so that a large-capacity and high-performance log storage function can be realized, and the log volume is mapped to the terminal device, so that the terminal device performs management operations such as query and analysis on the log volume through a protocol, that is, manages the data of a dropped disk through the terminal device.
In one possible implementation, the memory 2102 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a mapping function, etc.), and the like; the storage data area may store data created according to the use of the computer.
Further, the memory 2102 may include high speed random access memory, and may also include non-volatile memory, such as at least one disk storage device or other volatile solid state storage device.
The communication interface 2103 may be an interface of a communication module, such as an interface of a GSM module.
The present application may also include a display 2104 and an input unit 2105, among others.
Of course, the structure of the internet of things device shown in fig. 4 does not constitute a limitation on the internet of things device in the embodiment of the present application, and in practical applications, the electronic device may include more or less components than those shown in fig. 4, or some components in combination.
In another aspect, the present application further provides a computer-readable storage medium having stored thereon a computer program, which when executed by a processor, implements the steps of the log management method of the SAN storage system as described in any one of the above.
For the introduction of a computer-readable storage medium provided in the present application, please refer to the above embodiments, which are not described herein again.
The computer-readable storage medium provided by the application has the same beneficial effects as the log management method.
It is further noted that, in the present 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. Also, 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 an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A log management method of a SAN storage system is characterized by comprising the following steps:
creating a log volume by using a back-end hard disk and a storage pool;
logging by the log volume;
and mapping the log volume to terminal equipment so as to manage the log volume according to a target protocol through the terminal equipment.
2. The SAN storage system journaling management method according to claim 1, wherein before creating the journal volume using the back-end hard disk and the storage pool, the journaling management method further comprises:
calculating the size of a log volume according to the log information of the SAN storage system;
correspondingly, the process of creating the journal volume by using the backend hard disk and the storage pool specifically includes:
and creating a journal volume according to the size of the journal volume by using a back-end hard disk and a storage pool.
3. The method for managing logs of a SAN storage system according to claim 1, wherein the process of mapping the log volume to the terminal device is specifically:
and mapping the log volume as a SCSI LUN to a server host.
4. The SAN storage system log management method of claim 1,
the log volume comprises a super block and a plurality of log spaces divided according to log types, and the log space corresponding to each log type comprises a plurality of blocks;
accordingly, the process of creating a log volume includes:
initializing parameters of the super block;
and distributing the log space for each log type, and updating the parameters in the super block.
5. The SAN storage system log management method of claim 4, further comprising:
determining a cache region corresponding to the log type in a memory;
the process of recording logs by the log volume specifically includes:
storing the log of the current log type into a corresponding cache region;
when the log in the cache region meets the condition of disk dropping, the log in the cache region is written into the corresponding block in a flashing mode, and the block information of the block is updated.
6. The SAN storage system log management method according to claim 5, wherein the managing the log volume by the terminal device in a target protocol includes:
receiving an input instruction sent by the terminal equipment, wherein the input instruction comprises a log type mark number;
determining a target block in a target log volume according to the log type mark number;
and reading and analyzing all logs in the target block for management.
7. The SAN storage system log management method of any one of claims 1 to 6, wherein the target protocol comprises an FCP protocol or an iSCSI protocol.
8. A log management apparatus of a SAN storage system, comprising:
the creating module is used for creating the log volume by utilizing the back-end hard disk and the storage pool;
the recording module is used for recording the log through the log volume;
and the management module is used for mapping the log volume to the terminal equipment so as to manage the log volume according to a target protocol through the terminal equipment.
9. An electronic device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the log management method of the SAN storage system according to any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, having stored thereon a computer program which, when being executed by a processor, carries out the steps of the log management method of the SAN storage system according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911386482.8A CN111159119A (en) | 2019-12-29 | 2019-12-29 | Log management method, system and related components of SAN storage system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911386482.8A CN111159119A (en) | 2019-12-29 | 2019-12-29 | Log management method, system and related components of SAN storage system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111159119A true CN111159119A (en) | 2020-05-15 |
Family
ID=70558868
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911386482.8A Withdrawn CN111159119A (en) | 2019-12-29 | 2019-12-29 | Log management method, system and related components of SAN storage system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111159119A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060218200A1 (en) * | 2005-03-24 | 2006-09-28 | International Business Machines Corporation | Application of log records by storage servers |
| US20070245107A1 (en) * | 2006-04-14 | 2007-10-18 | Hitachi, Ltd. | System and method for processing a plurality kinds of event markers of a continuous data protection |
| US20190057024A1 (en) * | 2017-08-16 | 2019-02-21 | HGST, Inc. | Intelligent Redundant Array Of Independent Disks With High Performance Recompaction |
| CN110188000A (en) * | 2019-05-16 | 2019-08-30 | 上海爱数信息技术股份有限公司 | Application disaster recovery method and system based on virtualization and iSCSI or FC |
-
2019
- 2019-12-29 CN CN201911386482.8A patent/CN111159119A/en not_active Withdrawn
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060218200A1 (en) * | 2005-03-24 | 2006-09-28 | International Business Machines Corporation | Application of log records by storage servers |
| US20070245107A1 (en) * | 2006-04-14 | 2007-10-18 | Hitachi, Ltd. | System and method for processing a plurality kinds of event markers of a continuous data protection |
| US20190057024A1 (en) * | 2017-08-16 | 2019-02-21 | HGST, Inc. | Intelligent Redundant Array Of Independent Disks With High Performance Recompaction |
| CN110188000A (en) * | 2019-05-16 | 2019-08-30 | 上海爱数信息技术股份有限公司 | Application disaster recovery method and system based on virtualization and iSCSI or FC |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11068455B2 (en) | Mapper tree with super leaf nodes | |
| US10996883B2 (en) | Storage system including host device and storage device configured to perform selective purge operation | |
| EP4068070A1 (en) | Data storage method and apparatus, and storage system | |
| TWI668626B (en) | Storage apparatus and method for autonomous space compaction | |
| KR100951107B1 (en) | Method for managing files for optimal performance | |
| US8239648B2 (en) | Reclamation of thin provisioned disk storage | |
| US6732222B1 (en) | Method for performing flash memory file management | |
| US7716445B2 (en) | Method and system for storing a sparse file using fill counts | |
| US7761648B2 (en) | Caching method for NAND flash translation layer | |
| US8996843B2 (en) | Method for distributing random and sequential data in a tiered storage system | |
| US20150242309A1 (en) | Systems and methods for storage compression | |
| JP6443572B1 (en) | Storage control device, storage control method, and storage control program | |
| CN105843753B (en) | Logical block address for hard disk drive maps | |
| US11200159B2 (en) | System and method for facilitating efficient utilization of NAND flash memory | |
| US11042328B2 (en) | Storage apparatus and method for autonomous space compaction | |
| CN109804359A (en) | For the system and method by write back data to storage equipment | |
| US11226778B2 (en) | Method, apparatus and computer program product for managing metadata migration | |
| US8239427B2 (en) | Disk layout method for object-based storage devices | |
| CN114691020A (en) | ZNS standard based data compression storage device and method thereof | |
| CN110554843A (en) | Method and system for storing file data by multiple storage devices | |
| CN111159119A (en) | Log management method, system and related components of SAN storage system | |
| WO2014057518A1 (en) | Storage apparatus and data processing method | |
| US20060107002A1 (en) | Method, system, and program for an adaptor to read and write to system memory | |
| CN104951569A (en) | File system and file management method employing same | |
| CN110515861A (en) | Handle the storage device and method thereof of flash command |
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 | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20200515 |
|
| WW01 | Invention patent application withdrawn after publication |