CN107704205A

CN107704205A - RAID management methods, device and computer-readable recording medium

Info

Publication number: CN107704205A
Application number: CN201710927668.4A
Authority: CN
Inventors: 杜伟; 周伟明; 张少龙
Original assignee: SHENZHEN HUADEAN TECHNOLOGY Co Ltd
Current assignee: SHENZHEN HUADEAN TECHNOLOGY Co Ltd
Priority date: 2017-09-30
Filing date: 2017-09-30
Publication date: 2018-02-16
Also published as: WO2019062107A1

Abstract

The invention discloses a kind of RAID management methods, including：When receiving disk array RAID5 of the user based on the configuration interface input currently shown configuration information, based on the first RAID information corresponding to configuration information generation；When number of disks corresponding to disc information is more than or equal to 3, display includes creating the Creating interface of option corresponding to the first RAID information and the first RAID information；Receive based in Creating interface create option triggering RAID5 create instruction when, based on the first RAID information and pass through corresponding RAID5 interfaces create RAID5.The invention also discloses a kind of RAID managing devices and computer-readable recording medium.The present invention can create RAID5 according to user's request by corresponding RAID5 interfaces, can realize that RAID5 manages by the terminal of android system, improve the convenience of RAID5 management.

Description

RAID management method, device and computer readable storage medium

Technical Field

The present invention relates to the field of disk array technologies, and in particular, to a RAID management method, apparatus, and computer-readable storage medium.

Background

With the continuous development of internet technology, users of internet application are increasing, information data generated every day in the world are more and more, and the data increase speed is faster and faster. In such an environment, various storage technologies and storage schemes are in force. The RAID (Redundant Array of Independent Disks, disk Array for short) technology is widely applied to data reading in a large server by virtue of its advantages of high reliability, large data capacity, strong adaptability, high bandwidth, and the like.

Currently, in the data reading process of a large server, multiple RAIDs 5 are often applied simultaneously, and therefore, it is necessary to reasonably and effectively manage multiple RAIDs 5 to improve the efficiency of RAID5. However, at present, RAID5 management is mainly implemented in terminals such as large servers based on windows systems and linux systems, and RAID5 management cannot be performed in terminals based on Android systems.

The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.

Disclosure of Invention

The invention mainly aims to provide a RAID management method, a device and a computer readable storage medium, and aims to solve the technical problem that RAID5 management cannot be realized at a terminal of an Android system at present.

In order to achieve the above object, the present invention provides a RAID management method applied to a terminal installed with an Android system, where the RAID management method includes the following steps:

when configuration information of a disk array RAID5 input by a user based on a currently displayed configuration interface is received, generating corresponding first RAID information based on the configuration information, wherein the first RAID information comprises RAID5 levels and disk information;

when the number of the disks corresponding to the disk information is greater than or equal to 3, displaying an array creation interface comprising the first RAID information and creation options corresponding to the first RAID information;

and when a RAID5 creation instruction triggered based on a creation option in the array creation interface is received, creating RAID5 based on the first RAID information and through a corresponding RAID5 interface.

In one embodiment, the RAID management method further comprises:

when the current failure disk exists, acquiring second RAID information corresponding to the failure disk;

deleting the failed disk in the RAID5 corresponding to the second RAID information through a RAID5 interface corresponding to the second RAID information;

and reconstructing the RAID5 after the failed disk is deleted through a RAID5 interface corresponding to the second RAID information based on the RAID5 format disk in the idle state at present.

In one embodiment, the RAID management method further comprises:

when the abnormal RAID5 exists in the RAID5, acquiring abnormal information corresponding to the abnormal RAID5 and third RAID information;

and displaying prompt information comprising the abnormal information and the third RAID information.

In one embodiment, before the step of generating corresponding first RAID information based on the configuration information when receiving configuration information of the RAID5 of the disk array input by a user based on a currently displayed configuration interface, the RAID management method further includes:

when a login request triggered by a user based on a login interface is received, a login account and a login password corresponding to the login request are obtained;

when the login account number and the login password pass verification, displaying a RAID5 management main interface;

and when a configuration interface display request triggered by a management main interface based on RAID5 is received, displaying a configuration interface corresponding to the configuration interface display request.

In one embodiment, after the step of displaying the RAID5 management host interface, the RAID management method further comprises:

when an operation interface display request triggered by a management main interface based on RAID5 is received, displaying an operation interface corresponding to the operation interface display request;

when a start/stop instruction triggered based on the operation interface is received, acquiring fourth RAID information corresponding to the start/stop instruction;

and starting/stopping the RAID5 corresponding to the acquired fourth RAID information through a RAID5 interface corresponding to the fourth RAID information.

In one embodiment, after the step of displaying the RAID management host interface, the RAID management method further comprises:

when a formatting instruction triggered based on the operation interface is received, acquiring fifth RAID information corresponding to the formatting instruction;

and formatting the RAID5 corresponding to the fifth RAID information through a RAID5 interface corresponding to the fifth RAID information.

In one embodiment, the formatting the RAID5 corresponding to the fifth RAID information through the RAID5 interface corresponding to the fifth RAID information includes:

acquiring partition information of each disk in RAID5 corresponding to the fifth RAID information;

sequentially deleting the partitions corresponding to the disks based on the partition information through RAID5 interfaces corresponding to the fifth RAID information;

and formatting each disk subjected to partition deletion into a disk with a RAID5 format through a RAID5 interface corresponding to the fifth RAID information.

when an expansion instruction triggered based on the operation interface is received, based on a disk to be added with a RAID5 format corresponding to the expansion instruction, performing expansion operation on a RAID5 corresponding to the expansion instruction through a RAID5 interface corresponding to the expansion instruction; or,

when a disk deleting instruction triggered based on the operation interface is received, deleting a RAID 5-format disk corresponding to the disk deleting instruction in a RAID5 corresponding to the disk deleting instruction through a RAID5 interface corresponding to the disk deleting instruction, and reconstructing a RAID5 after deleting the disk; in the alternative to this, either,

when an adding/deleting instruction of the hot spare disk triggered based on the operation interface is received, adding/deleting the RAID5 format hot spare disk corresponding to the adding/deleting instruction in the RAID5 corresponding to the adding/deleting instruction through a RAID5 interface corresponding to the adding/deleting instruction.

In addition, to achieve the above object, the present invention further provides a RAID management apparatus applied to a terminal installed with an Android system, where the RAID management apparatus includes: the RAID management program is used for realizing the steps of any one of the RAID management methods when being executed by the processor.

In order to achieve the above object, the present invention further provides a computer-readable storage medium, in which a RAID management program is stored, and the RAID management program implements the steps of any one of the RAID management methods when executed by a processor.

According to the method and the device, when configuration information of the RAID5 input by a user based on a currently displayed configuration interface is received, corresponding first RAID information is generated based on the configuration information, then when the number of disks corresponding to the disk information is larger than or equal to 3, an array creation interface comprising the first RAID information and creation options corresponding to the first RAID information is displayed, and then when a RAID creation instruction triggered based on the creation options in the array creation interface is received, RAID5 is created based on the first RAID information and through a corresponding RAID5 interface, RAID5 can be created through a corresponding RAID5 interface according to user requirements, RAID5 management can be achieved through a terminal of an Android system, and convenience of RAID5 management is improved.

Drawings

Fig. 1 is a schematic structural diagram of a terminal to which a RAID management apparatus belongs in a hardware operating environment according to an embodiment of the present invention;

FIG. 2 is a flowchart illustrating a RAID management method according to a first embodiment of the present invention;

FIG. 3 is a block stripe distribution diagram of RAID5 according to the present invention;

FIG. 4 is a schematic diagram of a storage method of RAID5 according to the present invention;

FIG. 5 is a schematic diagram of the RAID5 architecture of the present invention;

FIG. 6 is a flowchart illustrating a RAID management method according to a second embodiment of the present invention;

FIG. 7 is a flowchart illustrating a RAID management method according to a third embodiment of the present invention;

FIG. 8 is a flowchart illustrating a fourth embodiment of a RAID management method according to the present invention;

FIG. 9 is a flowchart illustrating a fifth embodiment of a RAID management method according to the present invention;

FIG. 10 is a flowchart illustrating a sixth embodiment of a RAID management method according to the present invention;

fig. 11 is a detailed flowchart of the step of formatting the RAID5 corresponding to the fifth RAID information through the RAID5 interface corresponding to the fifth RAID information in the seventh embodiment of the RAID management method according to the present invention.

The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.

Detailed Description

It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

As shown in fig. 1, fig. 1 is a schematic structural diagram of a terminal belonging to a RAID management apparatus in a hardware operating environment according to an embodiment of the present invention.

The terminal of the embodiment of the invention can be a PC. As shown in fig. 1, the terminal may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, a communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001.

Optionally, the terminal may further include a camera, a Radio Frequency (RF) circuit, a sensor, an audio circuit, a WiFi module, and the like. Such as light sensors, motion sensors, and other sensors. Specifically, the light sensor may include an ambient light sensor that may adjust the brightness of the display screen according to the brightness of ambient light, and a proximity sensor that may turn off the display screen and/or the backlight when the mobile terminal is moved to the ear. As one of the motion sensors, the gravity acceleration sensor can detect the magnitude of acceleration in each direction (generally, three axes), detect the magnitude and direction of gravity when the mobile terminal is stationary, and can be used for applications (such as horizontal and vertical screen switching, related games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer and tapping) and the like for recognizing the attitude of the mobile terminal; of course, the mobile terminal may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which are not described herein again.

Those skilled in the art will appreciate that the terminal structure shown in fig. 1 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

As shown in fig. 1, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a RAID management program.

In the terminal shown in fig. 1, the network interface 1004 is mainly used for connecting to a backend server and performing data communication with the backend server; the user interface 1003 is mainly used for connecting a client (user side) and performing data communication with the client; and the processor 1001 may be used to invoke a RAID management program stored in the memory 1005.

In this embodiment, the RAID management apparatus includes: a memory 1005, a processor 1001, and a RAID management program stored in the memory 1005 and operable on the processor 1001, wherein when the processor 1001 calls the RAID management program stored in the memory 1005, the following operations are performed:

Further, the processor 1001 may call a RAID management program stored in the memory 1005, and also perform the following operations:

Referring to fig. 2, fig. 2 is a flowchart illustrating a RAID management method according to a first embodiment of the RAID management method of the present invention.

In this embodiment, the RAID management method is applied to a terminal equipped with an Android system, and the terminal equipped with the Android system may be a mobile terminal such as a mobile phone, an IPAD, and a smart wearable device.

The RAID management method comprises the following steps:

step S110, when configuration information of a disk array RAID5 input by a user based on a currently displayed configuration interface is received, generating corresponding first RAID information based on the configuration information, wherein the first RAID information comprises RAID5 levels and disk information;

the RAID technology is a core processing technology of a storage disk array, and aims to improve the efficiency and fault-tolerant capability of data processing. The storage system generally adopts necessary means to ensure the performance of the system in terms of implementation, and a common method is to set a cache system. A cache system is a virtualized system whose principle is to improve performance by efficiently handling I/O requests. RAID5 is a storage solution that addresses storage performance, data security, and storage cost. RAID5 may be understood to be a compromise between RAID0 and RAID 1. RAID5 is a new storage solution made based on system performance, data reliability, and economic applicability.

Further, in an embodiment, the step S130 includes: and creating the RAID5 based on the RAID5 format disk corresponding to the disk information and the RAID5 format hot spare disk corresponding to the hot spare disk information through the first RAID information and a corresponding RAID5 interface.

Referring to fig. 3 and 4, fig. 3 is a schematic diagram of a block stripe distribution of RAID5, and fig. 4 is a schematic diagram of a storage manner of RAID5.

The data is divided into blocks (chunks) in different physical member disks, Striping is a meaning of division, and several meanings need to be distinguished, namely stripe, strip and P, when data access is carried out, stripe distribution is carried out by taking the stripe as a basic unit, and stripe distribution of RAID5 is shown in FIG. 3. when the data is stored, the data is divided into blocks (chunks), D1, D2, D3, P8 are called as blocks in the drawings, and the blocks are regarded as a stripe, the data is distributed to each block (chunk) in the drawings, D358, D2, D3, P8 are called as blocks, the blocks are regarded as a stripe, and the data is processed as a block from one stripe to another by taking the distribution to each block (chunk) in the drawings, namely, D2, a jump unit is used for processing data in a Disk reading system, namely, D4642, the jump unit is used for processing data on a Disk, and the data processing system is shown as a jump unit 354642, namely, a jump unit is a jump unit 4642, which is a jump unit, namely a jump unit used for processing data on a Disk, namely a jump unit 3648, a jump unit is used for processing a jump.

static sbb_u32_t make_request(struct request_queue*q,struct bio*bi)

{

mddev_t*mddev＝q->queuedata；

raid5_conf_t*conf＝mddev->private；

sbb_u32_t dd_idx；

sector_t new_sector；

sector_t logical_sector,last_sector；

struct stripe_head*sh；

const sbb_u32_t rw＝bio_data_dir(bi)；

sbb_u32_t cpu,remaining；

if(unlikely(bio_rw_flagged(bi,BIO_RW_BARRIER))){

/*Drain all pending wts.We only really need

*to ensure they have been submitted,but this is easier.

*/

mddev->pers->quiesce(mddev,1)；

mddev->pers->quiesce(mddev,0)；

md_barrier_request(mddev,bi)；

return 0；

}

The make _ request function realizes a plurality of functions, and the rd5_ Sector function acquires a stripe and a device dev through dev _ Sector and rd _ idx, wherein the stripe refers to a storage stripe of RAID5. According to the information provided by the dev _ sector, a tape header, namely sh, is called to complete the primary processing of the read request, and the operation is realized by a get _ stripe function. And then calling a striped queue function add _ stripe _ bio according to rd _ idx information to store bio into sh- > rd _ idx. Therefore, the complicated processing process is omitted, the reading request operation of the stripe is simply processed, and a round of simple processing is completed. When a linked list reading operation request of a device is processed, dev has several states, wherein an empty linked list state represents an empty linked list state, no data is stored in the linked list, an rdy state represents that data is stored in the linked list and is ready to execute related operations, and a req state represents that the linked list operation is awakened. When the bio _ wr in req is marked as read, the bio _ end _ io function is switched back to the unset state. During the above operations, some data may be involved, such as resync,

pre-read rdy _ rd, bitmap bit _ map, etc. Taking RAID5 as an example, after the RAID is newly built, the check data is not ready at this time, and at this time, the check data is crucial, and the check data needs to be processed before formal writing of data in the device. After the process is completed, if the obtained check data is erroneous, the subsequent operation is resynchronized, and a resync request is required to complete the subsequent operation.

resync is the recovery of data on a member disk by the anti-parity of the data on the member disk and the parity disk. In the processing process, a struct r5dev structure body is arranged in each strip to manage the buffer blocks:

struct r5dev{

struct bio req；

struct bio_vec vec；

struct page*page；

struct bio*tord,*rd,*towt,*written；

sector_t sector；/*sector of this page*/

unsigned long flags；

dev [1 ]; v. distributing storage space based on RAID characteristics

struct bio req；/*Turn into the bio for the bottom of the device*/

struct bio_vec vec；/*The bi_io_vec corresponds to the req*/

struct page; v. buffer memory page

struct bio*rdy_io_rd,*rd_io_wt,*end_io_wt；

V. 3 memory linked lists to mark read and write operations on the buffer and end operations, respectively

sector_t sector；/*The strip of the sector in the whole RAID 5equipment

location*/

unsigned long flags；/*The buffer status flag*/

flag is divided into several states, whereby the buffer status is identified:

rd5_ current _ data/' data in memory page

rd5 latched/data latched, then underlying processing transfers

rd5_ rdy _ wt/' data to be written covers the entire buffer memory +

rd5_ Insync/. Normal State ` based on disk `

rd5_ rdy _ rd/' preparing read data

rd5_ rdy _ wt/' prepare write data

Overlap flag ^ greater than rd5_ stacked/. bIOs

rd5_ error _ rd/' read operation has an error

rd5_ end _ wt/' writing data to disk

rd5_ current _ data and rd5_ latched are used to represent the data state in the data buffer: empty, ready to write, dirty disk, clear data, and therefore critical to the buffer. The four states respectively mean: the data clearing is a state after the data in the buffer area is copied to the disk, and the data in the buffer area and the data in the disk are the same at the moment; the Dirty state indicates that there is data in the buffer and has passed through the CPU

And sending a back-brushing instruction to the bottom layer, and starting to back-brush data in the member disk. The back-flushing here refers to flushing data from the buffer memory back to the system disk. When in a write-ready state, the lower bottom layer of the cache sends an instruction for reading out data in the cache by the lower layer and marking the state; the empty state indicates that no data occupies the cache, and the memory space is large and is the original specified size. The four states are often required to be mutually converted along with the storage and use states of data, and the raid.h file in the kernel carries out complete, accurate and detailed code implementation and relevant explanation on the four states, and details are not repeated here. And calling rd5_ end _ rd when the bottom layer read request operation is successful, emptying the memory, marking the equipment state as empty, awakening the daemon thread at the moment, calling do _ stripe to perform second request processing, copying data in the buffer memory to a data storage page corresponding to the bio, and sending an instruction to the upper layer until the whole bio is full of data to complete a series of operations. Thus, a simple read request is processed.

The writing process is relatively complex compared to reading, since in addition to normal data check data are calculated and written. The processing procedures of acquiring the stripe and adding the stripe into the bio are almost the same in the follow-up reading operation, and the difference is that dev is put into a linked list rdy _ wr in raid5.h, and then do _ stripe processing is carried out. In handling write operations, we assume that only a certain bio covering the entire dev buffer page is handled. What do _ stripe first needs to do is to read modify write or detect the structure of the write data. Assuming that the probability of read-modify-write is greater, if the dev state bits of the dev and parity bits in ray _ wt are empty, then do _ stripe will set it to rdy state, facilitating the following write operation. Then the dev state will change, and the empty bit will be converted into rdy state, which is that the sh state is qualified and suitable for write operation, and will be transmitted to the bottom layer device by the instruction of read request to complete the write operation of the disk. After the bottom layer processing is finished, the state bit of dev is cleared, rd5 is arranged to perform data writing processing again on sh, at this time, it is especially important that the function performs data verification, the bio data page is copied to the buffer memory, the data of the verification page is updated in real time, and the bio linked list is linked from rdy _ wt to do _ wt. And setting the data check bit and the memory page as dirty pages, and sending a write request to the bottom layer for write processing. After the above steps are completed, the rd5_ wt _ request function is called back, and the state of dev will be changed to a dirty page state. The subsequent RAID5 would perform three simple passes of the sh. Once the data dev and check bit states are converted to clear states, an instruction is sent to the upper layer to inform that the write request processing is completed. Error handling during a write operation is performed in view of the bio _ current _ data state of the bio. If its state is cleared, it is considered an error in the read operation. The first thing to do at this point is to remove the rd5_ current _ data flag of the dev to ensure that its state is Empty. And performing early-stage work inspection after completion. If the RAID is in a degraded state, there is no ability to recover dev data because the state degradation can result in incomplete data and loss of data. In addition, dev in the reading operation process exceeds the total number of the strip heads, so that reading errors are inevitable, and the BSR operation cannot be carried out at the moment. This operation cannot be done and md _ error is called to do the first five processes. When the BSR operation is guaranteed to be performed, dev marks the error of the read operation and then calls do _ stripe again for processing. For an erroneous read operation flag bit, do _ stripe is invalidated. There is a provision for a number of failures, and if there is only one failure, then error recovery can also be performed. And (4) equipment inspection is carried out, if the equipment is not complete, an instruction is sent to the lower layer to carry out data perfection, and then data completion is carried out through reverse verification. If the dev data is complete, data update is performed directly, the data is marked as rdy _ wt state, and the write request is sent to only the lower layer device. If multiple failures occur, unfortunately, the data cannot be complemented, and the anti-verification operation cannot be performed, and then the md _ error function is called to perform error handling. And (4) the dev is removed in the process of copying the data, and after the do _ stripe processing is successfully carried out, the operation processing of the round is completed.

In this embodiment, a terminal installed with an Android system is installed with a RAID management application APP, a holder (user) of the terminal has a login password corresponding to a login account of the APP, and after the user logs in, a RAID5 management main interface corresponding to the APP can be displayed on a display interface of the terminal, where the RAID5 management main interface includes array creation information, currently logged in user information, current disk array information, capacity information of disks corresponding to respective disk arrays, spare disk information, navigation information of secondary interfaces such as a configuration interface and an operation interface, and the like. A user can manage navigation information corresponding to a configuration interface in a main interface to enter the configuration interface through the RAID5, and then the level of a disk array required to be created, a disk required to be used and a hot spare disk are set in the configuration interface, or a configuration file is generated and imported, and the like, and when the setting is completed, the configuration information can be submitted through options (buttons) of the current interface, so that the configuration information of the RAID5 can be input.

In this embodiment, when the configuration interface is set up, a user may submit configuration information of RAID5 in a manner of an option (button) of the current interface, and when receiving configuration information of RAID5 input by the user based on the currently displayed configuration interface, generate corresponding first RAID information based on the configuration information, that is, package all the configuration information according to a preset format to generate the first RAID information.

The configuration information includes RAID5 level information, disk information, and/or hot spare information.

Step S120, when the number of the disks corresponding to the disk information is greater than or equal to 3, displaying an array creation interface including the first RAID information and creation options corresponding to the first RAID information;

in this embodiment, when the first RAID information is generated and the number of disks corresponding to the disk information is greater than or equal to 3, a display screen of the terminal pops up or switches to an array creation interface, where the array creation interface is used to display the first RAID information and creation options corresponding to the first RAID information, and a user may confirm again whether a relevant configuration corresponding to a RAID to be created is correct through the displayed first RAID information, and when the relevant configuration is correct, a RAID5 creation instruction may be triggered through the creation options (buttons) displayed on the current array creation interface, and the like.

The first RAID information comprises RAID5 grade information, disk information and/or hot spare information required by the RAID5 to be created, RAID5 interface information and the like.

And step S130, when a RAID5 creation instruction triggered based on a creation option in the array creation interface is received, creating a RAID5 through a corresponding RAID5 interface based on the first RAID information.

In this embodiment, when the user clicks (selects) a creation option in the array creation interface, a RAID5 creation instruction is triggered, and when a RAID5 creation instruction triggered based on the creation option in the array creation interface is received, the terminal creates a RAID5 based on the first RAID information through a RAID5 interface corresponding to the first RAID information.

Referring to FIG. 5, FIG. 5 is a schematic diagram of an architecture of RAID5.

When RAID5 is created, the disk devices need 3 or more disks, that is, the number of RAID5 hard disks in the MCU hardware layer is 3 or more.

A Linux kernel layer: the kernel driver is mainly modified, the Linux kernel version at present needs more than 2.6 versions to support the RAID device, the environment tested in this document is Linux3.4.39 only needs to open the function of the RAID device in the MD device, and the specific configuration process is as follows: a. entering a Device Driver; b. selecting a multiple devices driver (RAID and LVM); c. two RAID-5 related options are selected.

Android system layer: RAID implementations are primarily deployed to the system. Such as migrating mdadm, Btrfs, raidtools, etc. tools to the system process directory/system/bin. The following steps are taken as mdadm for example: A. mddm transplanting, namely outputting an mddm target file through a cross compiling tool, and putting the target file into a system/bin; B. permission configuration, namely opening all required permissions of mdadm so that the upper-layer app can execute the script; C. recompile the packaging system.

Android APP layer: the user can execute the corresponding program through Android Rumtime in the app. For example, an array disk is created, and mdadm-create-merge/dev/md 0 level-5-RAID-devices-2 xxxxxx xxx and the like, and the corresponding information is output by out to manage the RAID5 array.

In this embodiment, a configuration module, an array creation module, and other modules may be provided in the terminal of the Android system, where the configuration module receives disk array configuration information input by a user and generates corresponding disk array information, and the array creation module creates a corresponding RAID5 interface according to the disk array information generated by the configuration module.

According to the RAID management method provided by the embodiment, when configuration information of a disk array RAID5 input by a user based on a currently displayed configuration interface is received, corresponding first RAID information is generated based on the configuration information, then when the number of disks corresponding to the disk information is greater than or equal to 3, an array creation interface comprising the first RAID information and creation options corresponding to the first RAID information is displayed, and then when a RAID5 creation instruction triggered based on the creation options in the array creation interface is received, a RAID5 is created based on the first RAID information and through a corresponding RAID5 interface, a 5 can be created through a corresponding RAID5 interface according to user requirements, RAID5 management can be achieved through a terminal of an Android RAID system, and convenience of RAID5 management is improved.

Based on the first embodiment, a second embodiment of the method of the present invention is provided, and referring to fig. 6, in this embodiment, the RAID management method further includes:

step S140, when the current existence of the failed disk is monitored, second RAID information corresponding to the failed disk is obtained;

in this embodiment, the terminal equipped with the Android system may monitor the status of each currently existing disk in real time to obtain corresponding status information, and when determining that a currently existing failed disk exists according to the status information, obtain second RAID information corresponding to the failed disk, that is, determine RAID5 to which the failed disk belongs, where the second RAID information may be information such as a serial number and a name of RAID5.

Step S150, deleting the failed disk in the RAID5 corresponding to the second RAID information through the RAID5 interface corresponding to the second RAID information;

in this embodiment, when the second RAID information is acquired, the failed disk is deleted in the RAID5 corresponding to the second RAID information, and specifically, the failed disk may be deleted in the RAID5 corresponding to the second RAID information by or by calling a RAID5 interface corresponding to the second RAID information.

And step S160, reconstructing the RAID5 after the failed disk is deleted through the RAID5 interface corresponding to the second RAID information based on the RAID5 format disk in the idle state at present.

In this embodiment, to avoid suspending the RAID5 after deleting the disk, first, a RAID5 format disk in an idle state is obtained, where the RAID5 format disk in the idle state refers to a RAID5 format disk which does not belong to any RAID5 at present, the number of RAID5 format disks in the idle state is consistent with the number of deleted failed disks, and then, based on the obtained RAID5 format disk, the RAID5 after deleting the failed disks through the RAID5 interface corresponding to the second RAID information is rebuilt, that is, the rebuilt RAID5 includes the remaining disks and hot spare disks in the RAID5 after deleting the failed disks, and the RAID5 format disk in the idle state.

In other embodiments, when RAID5 after deleting the failed disk meets the requirement corresponding to the level of RAID5, that is, the number of disks in RAID5 after deleting the failed disk is greater than or equal to 3, RAID5 may be directly rebuilt.

In other embodiments, if the failed disk does not belong to RAID5, the disk is deleted directly.

According to the RAID management method provided by the embodiment, when the current failed disk exists is monitored, second RAID information corresponding to the failed disk is obtained, the failed disk is deleted in RAID5 corresponding to the second RAID information, then based on the RAID5 format disk in the idle state, RAID5 after the failed disk is deleted is rebuilt through a RAID5 interface corresponding to the second RAID information, and therefore the deletion of the failed disk in RAID5 and the reconstruction of RAID5 can be achieved through a terminal of an Android system, and the convenience of RAID5 management is further improved.

Based on the first embodiment, a third embodiment of the method of the present invention is provided, and referring to fig. 7, in this embodiment, the RAID management method further includes:

step S170, when it is monitored that an abnormal RAID5 exists in RAID5, acquiring abnormal information corresponding to the abnormal RAID5 and third RAID information;

in this embodiment, the terminal equipped with the Android system may monitor the states of all the RAIDs 5 in real time, and determine whether an abnormal RAID5 exists at present according to the monitoring result, where the abnormal RAID5 includes a case where the RAID5 is suddenly powered off or a case where a disk in the RAID5 is suddenly powered off, the RAID5 is being reconstructed, the disk sequence of the RAID5 is disordered, the RAID5 is deleted by mistake, formatted by mistake or partitioned by mistake, a disk of the RAID5 is damaged or a disk of the RAID5 is pulled out, and the like. When it is monitored that an abnormal RAID5 exists in the RAID, the terminal acquires abnormal information corresponding to the abnormal RAID5 and third RAID information, where the third RAID information may be information such as a serial number and a name of RAID5.

And step S180, displaying prompt information comprising the abnormal information and the third RAID information.

In this embodiment, when the abnormal information and the third RAID information corresponding to the abnormal RAID5 are obtained, the obtained abnormal information and the third RAID information are displayed on a display screen of the terminal, so that a user can know that the abnormal RAID5 currently exists in time, and of course, voice alarm information and the like can be output while the abnormal information and the third RAID information corresponding to the abnormal RAID5 are displayed.

According to the RAID management method provided by the embodiment, when the abnormal RAID5 exists in the RAID5, the abnormal information corresponding to the abnormal RAID and the third RAID information are obtained, and then prompt information comprising the abnormal information and the third RAID information is displayed, the abnormal information can be displayed when the abnormal RAID5 is checked, so that a user can timely know the abnormal RAID5 existing currently, and the convenience of RAID5 management is further improved.

Based on the foregoing embodiments, a fourth embodiment of the method of the present invention is provided, and referring to fig. 8, in this embodiment, before step S110, the RAID management method further includes:

step S190, when a login request triggered by a user based on a login interface is received, a login account and a login password corresponding to the login request are obtained;

in this embodiment, a RAID management application APP is installed in a terminal in which an Android system is installed, and a holder (user) of the terminal owns a login password corresponding to a login account of the APP. When the user starts the APP, a login interface corresponding to the APP is displayed, so that the user can input a corresponding login account and a login password based on the login interface, and a login request is triggered by clicking a login option and the like. When a login request triggered by a user based on a login interface is received, the terminal acquires a login account and a login password corresponding to the login request.

Step S200, when the login account and the login password pass verification, displaying a RAID5 management main interface;

in this embodiment, when the login account and the login password are acquired, the login account and the login password are verified, and when the login account and the login password pass the verification, a RAID5 management main interface is displayed on a display screen of the terminal. The RAID5 management main interface includes array creation information, currently logged-in user information, current disk array information, capacity information of a disk corresponding to each disk array, free disk information, navigation information of a secondary interface such as a configuration interface and an operation interface, and the like.

Step S210, when a configuration interface display request triggered by a management main interface based on RAID5 is received, displaying a configuration interface corresponding to the configuration interface display request.

In this embodiment, a user may enter a configuration interface through navigation information corresponding to a configuration interface in the RAID5 management main interface, specifically, when receiving a configuration interface display request triggered based on the RAID5 management main interface, display the configuration interface corresponding to the configuration interface display request, and then the user may set, on the configuration interface, a level of a disk array that needs to be created, a disk that needs to be used, a hot spare disk, or generate and import a configuration file, and when the setting is completed, submit through an option (button) of the current interface, so as to implement input of configuration information of RAID5.

Further, in an embodiment, after step S200, the RAID management method further includes:

In this embodiment, the RAID5 may be expanded through an operation interface, that is, operations such as adding disks to RAID5, deleting disks to RAID5, and adding/deleting hot spare disks to RAID5.

Specifically, when a capacity expansion instruction triggered based on the operation interface is received, RAID5 corresponding to the capacity expansion instruction and a disk to be added in RAID5 format are obtained, and the disk to be added in RAID5 format is added to RAID5 through a RAID5 interface corresponding to the capacity expansion instruction, so that capacity expansion of RAID5 is achieved.

When a disk deleting instruction triggered based on the operation interface is received, determining a RAID5 format disk to be deleted corresponding to the disk deleting instruction, deleting the RAID5 format disk to be deleted in the RAID5 corresponding to the disk deleting instruction through a RAID5 interface corresponding to the disk deleting instruction, and rebuilding RAID5 after deleting the disk to be deleted after deleting the RAID5 format disk. Preferably, when the RAID5 after deleting the disk meets the requirement corresponding to the level of the RAID5, that is, the number of disks in the RAID5 after deleting the disk of the RAID5 format to be deleted is greater than or equal to 3, the RAID may be directly reconstructed, or another RAID5 format disk the same as the number of disks of the RAID5 format to be deleted may be selected to reconstruct the RAID5 after deleting the disk, so as to ensure that the capacity of the RAID5 after deleting the disk is not changed; and when the RAID5 after the disk deletion does not meet the requirement corresponding to the RAID level, selecting other RAID 5-format disks with the same number as that of the RAID 5-format disks to be deleted to reconstruct the RAID5 after the disk deletion.

When an adding/deleting instruction of the hot spare disk triggered based on the operation interface is received, the hot spare disk corresponding to the adding/deleting instruction is determined, and the hot spare disk is deleted in the RAID5 corresponding to the adding/deleting instruction through the RAID5 interface corresponding to the adding/deleting instruction.

According to the RAID management method provided by the embodiment, when a login request triggered by a user based on a login interface is received, a login account and a login password corresponding to the login request are obtained; then, when the login account number and the login password pass verification, displaying a RAID5 management main interface; and then when a configuration interface display request triggered by the RAID 5-based management main interface is received, displaying a configuration interface corresponding to the configuration interface display request, and displaying a RAID5 management main interface on the Android terminal, so that a user can conveniently manage the RAID5 according to the content displayed by the RAID5 management main interface, and the convenience of RAID5 management is further improved.

Based on the fourth embodiment, a fifth embodiment of the method of the present invention is proposed, and referring to fig. 9, in this embodiment, after step S200, the RAID management method further includes:

step S220, when an operation interface display request triggered by a management main interface based on RAID5 is received, displaying an operation interface corresponding to the operation interface display request;

in this embodiment, a user may enter an operation interface through navigation information corresponding to a configuration interface in the RAID5 management main interface, and specifically, when receiving an operation interface display request triggered based on the RAID5 management main interface, display an operation interface corresponding to the configuration interface display request, where the operation interface includes RAID5 operation options such as start/stop, formatting, and the like.

Step S230, when a start/stop instruction triggered based on the operation interface is received, acquiring fourth RAID information corresponding to the start/stop instruction;

in this embodiment, a user may click a start/stop option of an operation interface to trigger a start/stop instruction, and when receiving the start/stop instruction triggered based on the operation interface, the terminal acquires fourth RAID information corresponding to the start/stop instruction, where the fourth RAID information may be information such as a serial number and a name of RAID5.

Step S240, starting/stopping the RAID5 corresponding to the acquired fourth RAID information through the RAID5 interface corresponding to the fourth RAID information.

In this embodiment, when the fourth RAID information is acquired, the terminal starts/stops the RAID5 corresponding to the acquired fourth RAID information through the RAID5 interface corresponding to the fourth RAID information.

According to the RAID management method provided by the embodiment, when an operation interface display request triggered based on a RAID management main interface is received, an operation interface corresponding to the operation interface display request is displayed, then when a start/stop instruction triggered based on the operation interface is received, fourth RAID information corresponding to the start/stop instruction is acquired, then the acquired RAID5 corresponding to the fourth RAID information is started/stopped through a RAID5 interface corresponding to the fourth RAID information, the start/stop control of RAID5 can be achieved through an Android terminal, and the convenience in RAID5 management is further improved.

Based on the fourth embodiment, a sixth embodiment of the method of the present invention is provided, and referring to fig. 10, in this embodiment, after step S220, the RAID management method further includes:

step S250, when a formatting instruction triggered based on the operation interface is received, acquiring fifth RAID information corresponding to the formatting instruction;

in this embodiment, a user may click a formatting option of an operation interface to trigger a formatting instruction, and when receiving the formatting instruction triggered based on the operation interface, the terminal obtains fifth RAID information corresponding to the formatting instruction, where the fifth RAID information may be information such as a serial number and a name of RAID5.

Step S260, formatting the RAID5 corresponding to the fifth RAID information through the RAID5 interface corresponding to the fifth RAID information.

In this embodiment, when the fifth RAID information is acquired, the terminal formats RAID5 corresponding to the fifth RAID information through a RAID5 interface corresponding to the fifth RAID information, specifically, a disk to be formatted may be determined first, then a partition of the determined disk is deleted, and finally each disk in RAID5 corresponding to the fifth RAID information is formatted into a disk in RAID5 format.

According to the RAID management method provided by the embodiment, when a formatting instruction triggered based on the operation interface is received, fifth RAID information corresponding to the formatting instruction is obtained, and then RAID5 corresponding to the fifth RAID information is formatted through a RAID5 interface corresponding to the fifth RAID information, so that formatting of RAID5 can be realized by adopting an Android terminal, and convenience in RAID5 management is further improved.

Based on the fifth embodiment, a seventh embodiment of the method of the present invention is proposed, and referring to fig. 11, in this embodiment, step S260 includes:

step S261, obtaining partition information of each disk in RAID5 corresponding to the fifth RAID information;

in this embodiment, when acquiring the fifth RAID information, the terminal acquires partition information of each disk in RAID5 corresponding to the fifth RAID information.

Step S262, sequentially deleting the partitions corresponding to the respective disks based on the partition information through the RAID5 interface corresponding to the fifth RAID information;

in this embodiment, when acquiring the partition information, the terminal sequentially deletes, through the RAID5 interface corresponding to the fifth RAID information, the partitions corresponding to the disks based on the partition information, so as to format the disks.

Step S263, formatting each disk after the partition is deleted into a disk in RAID5 format through a RAID5 interface corresponding to the fifth RAID information.

In this embodiment, after deleting the partition corresponding to each disk, the terminal formats each disk after deleting the partition into a RAID5 format disk through a RAID5 interface corresponding to the fifth RAID information, thereby implementing the formatting of the RAID5.

According to the RAID management method provided by the embodiment, the partition information of each disk in the RAID5 corresponding to the fifth RAID information is obtained, then the partition corresponding to each disk is sequentially deleted based on the partition information through the RAID5 interface corresponding to the fifth RAID information, then each disk after the partition is deleted is formatted into a disk with a RAID5 format through the RAID5 interface corresponding to the fifth RAID information, then the partition of each disk of the RAID5 can be deleted through an Android terminal, and then formatting of the RAID5 is performed, so that convenience of RAID5 management is further improved.

In addition, an embodiment of the present invention further provides a computer-readable storage medium, where a RAID management program is stored on the computer-readable storage medium, and when executed by a processor, the RAID management program implements the following operations:

Further, the RAID management program when executed by the processor further performs the following operations:

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system 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 system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims

1. A RAID management method is applied to a terminal for installing an Android system, and is characterized by comprising the following steps:

2. The RAID management method of claim 1, wherein the RAID management method further comprises:

3. The RAID management method of claim 1, wherein the RAID management method further comprises:

4. The RAID management method of any one of claims 1 to 3, wherein prior to the step of generating corresponding first RAID information based on the configuration information when receiving configuration information of the disk array RAID5 input by a user based on a currently displayed configuration interface, the RAID management method further comprises:

5. The RAID management method of claim 4, wherein after the step of displaying the RAID5 management host interface, the RAID management method further comprises:

6. The RAID management method of claim 4, wherein after the step of displaying the RAID5 management host interface, the RAID management method further comprises:

7. The RAID management method of claim 6, wherein the formatting the RAID5 corresponding to the fifth RAID information via a RAID5 interface corresponding to the fifth RAID information comprises:

8. The RAID management method of claim 4, wherein after the step of displaying the RAID5 management host interface, the RAID management method further comprises:

9. A RAID management device is applied to a terminal for installing an Android system, and is characterized by comprising: memory, a processor and a RAID management program stored on the memory and executable on the processor, the RAID management program when executed by the processor implementing the steps of the RAID management method of any one of claims 1 to 8.

10. A computer-readable storage medium, having a RAID management program stored thereon, which when executed by a processor, performs the steps of the RAID management method of any one of claims 1 to 8.