A storage management method and device

Abstract

The application provides a storage management method and device. The method comprises: obtaining configuration information, the configuration information comprising at least quantity information and size information of at least one target partition; obtaining the capacity of at least one extended storage device of a baseboard management controller and current partition information, the current partition information being related to at least one current partition of the extended storage device; determining target partition information based on at least the configuration information and the capacity of the extended storage device; and adjusting the current partition of the extended storage device based on the target partition information in the case that the target partition information and the current partition information are determined to be mismatched.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a storage management method and apparatus. Background Technology

[0002] Currently, the Baseboard Management Controller (BMC) in a server typically requires the use of extended storage devices to obtain larger storage space. The BMC generally partitions the extended storage device based on the startup script in the Baseboard Management System (BMS). However, when the extended storage device is updated, the BMC needs to modify its startup script to adapt to the updated extended storage device and partition it accordingly.

[0003] However, the above methods suffer from low partitioning efficiency and high partitioning costs. Summary of the Invention

[0004] This application provides the following technical solution:

[0005] This application provides a storage management method applied to a baseboard management controller, the method comprising:

[0006] Obtain configuration information, which includes at least the number and size information of at least one target partition;

[0007] The capacity and current partition information of at least one extended storage device of the baseboard management controller are obtained, wherein the current partition information is related to at least one current partition of the extended storage device;

[0008] The target partition information is determined based at least on the configuration information and the capacity of the extended storage device;

[0009] If it is determined that the target partition information and the current partition information do not match, the current partition of the extended storage device is adjusted based on the target partition information.

[0010] Based at least on the configuration information and the capacity of the extended storage device, the target partition information is determined, including:

[0011] Based on the size information of the target partition, determine the proportion of the capacity of the target partition in the total capacity of the at least one target partition;

[0012] Based on the capacity and proportion of the extended storage device, the size information of at least one target partition in the configuration information is adjusted to obtain the adjusted size information of at least one target partition;

[0013] The target partition information consists of at least one number of target partitions and its adjusted size.

[0014] The capacity of the extended storage device includes: the theoretical capacity and the actual capacity of the extended storage device;

[0015] The step of adjusting the size information of at least one target partition in the configuration information based on the capacity and proportion of the extended storage device to obtain the adjusted size information of at least one target partition includes:

[0016] Based on the stated proportion and the theoretical capacity of the extended storage device, the initial size information of the at least one target partition is generated;

[0017] Based on the actual capacity of the extended storage device, the initial size information of the at least one target partition is adjusted to obtain the target size information of the at least one target partition;

[0018] Based on the target size information of the at least one target partition, determine the address information of the at least one target partition;

[0019] The target partition information consists of the quantity information and address information of the at least one target partition.

[0020] Determining the address information of the at least one target partition based on the target size information of the at least one target partition includes:

[0021] Determine the starting address of the first target partition among the at least one target partition;

[0022] Based on the target size information of the at least one target partition and the starting address of the first target partition, the ending address of each target partition except the last target partition is determined. The starting address of each target partition is divisible by a set constant value, and the starting address of each target partition is different.

[0023] Based on the start address and end address of each of the at least one target partitions except the last target partition, a capacity loss value of the at least one target partition is determined, wherein the capacity loss value is related to the fact that the start address is divisible by a set constant value;

[0024] Based on the target size information of the last target partition, determine the capacity of the last target partition;

[0025] Based on the capacity loss value of the at least one target partition and the capacity of the last target partition, determine the available capacity of the last target partition;

[0026] Based on the available capacity of the last target partition, determine the start address and end address of the last target partition.

[0027] Based on the actual capacity of the extended storage device, the initial size information of the at least one target partition is adjusted to obtain the target size information of the at least one target partition, including:

[0028] According to the stated proportion, the actual capacity of the extended storage device is divided, and the initial size information of the at least one target partition is replaced with the partition size information corresponding to the actual capacity obtained from the division, so as to obtain the target size information of the at least one target partition.

[0029] Alternatively, determine the difference between the theoretical capacity and the actual capacity of the extended storage device, replace the initial size information of the last target partition in the at least one target partition with the partition size information corresponding to the difference, and obtain the target size information of the at least one target partition.

[0030] The configuration information also includes: target file system type information of the at least one target partition;

[0031] The step of determining the target partition information based at least on the configuration information and the capacity of the extended storage device further includes:

[0032] The target file system type information of the at least one target partition is determined as the file system type information of the at least one target partition;

[0033] The target partition information consists of at least one file system type information, quantity information, and adjusted size information of the target partition.

[0034] The current partition information includes: the number of the at least one current partition, its address information, and its file system type information;

[0035] The mismatch between the target partition information and the current partition information includes:

[0036] Any one or more of the following are mismatched: the number of the at least one target partition and the number of the at least one current partition; the address information of the at least one target partition and the address information of the at least one current partition; and the file system type information of the at least one target partition and the file system type information of the at least one current partition.

[0037] The method further includes:

[0038] If the file system of the at least one target partition is determined to be the target file system, and if an abnormal file node is determined to exist in the at least one target partition, the abnormal file node is repaired.

[0039] If the abnormal file node recovers to a normal file node, a read / write test is performed on the at least one target partition;

[0040] If the abnormal file node is not restored to a normal file node, and it is determined that the number of times the at least one target partition is formatted based on the target file system has not reached the file system verification limit, the at least one target partition is formatted based on the target file system, and read / write tests are performed on the at least one target partition.

[0041] If it is determined that the file system of the at least one target partition is not the target file system, and if it is determined that the number of times the at least one target partition is formatted based on the target file system has not reached the file system verification limit, the at least one target partition is formatted based on the target file system, and read / write tests are performed on the at least one target partition.

[0042] The method further includes:

[0043] Obtain the kernel report of the baseboard management controller and identify the corrupted file nodes from the kernel report;

[0044] If the number of damaged file nodes is determined to reach a first upper limit threshold, a first alarm message is recorded.

[0045] If it is determined that the baseboard management controller needs to be restarted, restart the baseboard management controller;

[0046] If the number of damaged file nodes does not reach the first upper limit threshold but reaches the second upper limit threshold, a second alarm message is recorded, wherein the second upper limit threshold is less than the first upper limit threshold.

[0047] If the number of corrupted file nodes does not reach the first upper limit threshold, does not reach the second upper limit threshold, and does not reach the third upper limit threshold, return to the step of obtaining the kernel report of the baseboard management controller, where the third upper limit threshold is less than the second upper limit threshold;

[0048] If the number of damaged file nodes does not reach the first upper limit threshold, does not reach the second upper limit threshold, but reaches the third upper limit threshold, a third alarm message is recorded.

[0049] Another aspect of this application provides a storage management device, including:

[0050] The first acquisition module is used to acquire configuration information, which includes at least the quantity and size information of at least one target partition;

[0051] The second acquisition module is used to acquire the capacity and current partition information of at least one extended storage device of the baseboard management controller, wherein the current partition information is related to at least one current partition of the extended storage device;

[0052] The determination module is used to determine target partition information based at least on the configuration information and the capacity of the extended storage device;

[0053] An adjustment module is used to adjust the current partition of the extended storage device based on the target partition information when it is determined that the target partition information and the current partition information do not match.

[0054] In this application, by obtaining configuration information and the capacity and current partition information of at least one extended storage device of the baseboard management controller, the target partition information is determined based at least on the configuration information and the capacity of the extended storage device. If it is determined that the target partition information and the current partition information do not match, the current partition of the extended storage device is adjusted based on the target partition information. This ensures that for extended storage devices that have been updated, the current partition of the extended storage device can be adjusted without modifying the startup script, thereby improving partitioning efficiency and partitioning cost. Attached Figure Description

[0055] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0056] Figure 1 This is a flowchart illustrating a storage management method provided in Embodiment 1 of this application;

[0057] Figure 2 This is a flowchart illustrating a storage management method provided in Embodiment 2 of this application;

[0058] Figure 3 This is a flowchart illustrating a storage management method provided in Embodiment 3 of this application;

[0059] Figure 4 This is a flowchart illustrating a storage management method provided in Embodiment 4 of this application;

[0060] Figure 5 This is a flowchart illustrating a storage management method provided in Embodiment 5 of this application;

[0061] Figure 6 This is a flowchart illustrating a storage management method provided in Embodiment 6 of this application;

[0062] Figure 7 This is a schematic diagram of the structure of a storage management device provided in this application. Detailed Implementation

[0063] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0064] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0065] Reference Figure 1 This is a flowchart illustrating a storage management method provided in Embodiment 1 of this application. This method can be applied to a baseboard management controller, such as... Figure 1 As shown, the method may include, but is not limited to, the following steps:

[0066] Step S101: Obtain configuration information. The configuration information includes at least the number and size information of at least one target partition.

[0067] In this embodiment, the configuration information can be defined by the user based on their usage needs. The configuration information can be pre-stored in the setting storage area of ​​the baseboard management controller, and can be retrieved from the setting storage area of ​​the baseboard management controller when needed.

[0068] The quantity information of at least one target partition represents the total number of at least one target partition. The size information of at least one target partition can be understood as the size information of each target partition within the at least one target partition. For example, if six target partitions are defined, and the six target partitions are 512MiB, 256MiB, 256MiB, 256MiB, 512MiB, and 256MiB respectively, the configuration information includes the quantity information of at least six target partitions, and the size information of each target partition represents the capacity of the target partitions as: 512MiB, 256MiB, 256MiB, 256MiB, 512MiB, and 256MiB respectively.

[0069] In this embodiment, if the user does not specify the file system type of the target partition, the target partition can be formatted as the set file system type (e.g., EXT4).

[0070] Step S102: Obtain the capacity and current partition information of at least one extended storage device of the baseboard management controller, wherein the current partition information is related to at least one current partition of the extended storage device.

[0071] In this embodiment, the baseboard management controller may include one or more extended storage devices, and each extended storage device may include at least one current partition.

[0072] The kernel data of the baseboard management controller contains at least the number of extended storage devices, the capacity of each extended storage device, and the current partition information. Accordingly, the capacity and current partition information of each extended storage device can be obtained from the kernel data of the baseboard management controller.

[0073] Step S103: Determine the target partition information based at least on the configuration information and the capacity of the extended storage device.

[0074] This step may include, but is not limited to: determining the adjusted quantity and / or size information of at least one target partition as target partition information based on the quantity and / or size information of at least one target partition in the capacity adjustment configuration information of the extended storage device.

[0075] Step S104: If it is determined that the target partition information and the current partition information do not match, adjust the current partition of the extended storage device based on the target partition information.

[0076] The corresponding target partition information can be an implementation of adjusted quantity and / or size information of at least one target partition. The current partition information may include: quantity and / or size information of at least one current partition. If it is determined that the target partition information and the current partition information do not match, the current partition of the extended storage device is adjusted based on the target partition information, which may include, but is not limited to:

[0077] If it is determined that the quantity information of at least one target partition and the quantity information of at least one current partition are mismatched, and / or the size information of at least one target partition and the size information of at least one current partition are mismatched, the quantity and / or capacity of the current partition of the extended storage device shall be adjusted based on the adjusted quantity information and / or size information of at least one target partition.

[0078] In this embodiment, by obtaining configuration information and the capacity and current partition information of at least one extended storage device of the baseboard management controller, the target partition information is determined based at least on the configuration information and the capacity of the extended storage device. If it is determined that the target partition information and the current partition information do not match, the current partition of the extended storage device is adjusted based on the target partition information. This ensures that for extended storage devices that have been updated, the current partition of the extended storage device can be adjusted without modifying the startup script, thereby improving partitioning efficiency and partitioning cost.

[0079] As another optional embodiment of this application, refer to Figure 2 This is a flowchart illustrating a storage management method provided in Embodiment 2 of this application. This embodiment is mainly a refinement of the storage management method described in Embodiment 1 above. The method may include, but is not limited to, the following steps:

[0080] Step S201: Obtain configuration information. The configuration information includes at least the number and size information of at least one target partition.

[0081] Step S202: Obtain the capacity and current partition information of at least one extended storage device of the baseboard management controller, wherein the current partition information is related to at least one current partition of the extended storage device.

[0082] For a detailed description of steps S201-S202, please refer to the relevant description of steps S101-S102 in Example 1, which will not be repeated here.

[0083] Step S203: Based on the size information of the target partition, determine the proportion of the capacity of the target partition in the total capacity of at least one target partition.

[0084] Based on the size information of the target partition, the capacity of the target partition can be determined. Based on the capacity of each target partition, the total capacity of at least one target partition can be determined.

[0085] Given a determined total capacity of at least one target partition, determine the percentage of each target partition's capacity within the total capacity of the at least one target partition. For example, if there are at least six target partitions with capacities of 512 MiB, 256 MiB, 256 MiB, 256 MiB, 512 MiB, and 256 MiB respectively, and the total capacity of the six target partitions is 2048 MiB, then the percentage of each target partition's capacity within the total capacity of the at least one target partition is as follows: Right now,

[0086] If the user defines only one target partition, the configuration information will contain at least one target partition, and the capacity of the target partition will be equal to the total capacity. Therefore, the capacity of the target partition will account for 1% of the total capacity.

[0087] Step S204: Based on the capacity and proportion of the extended storage device, adjust the size information of at least one target partition in the configuration information to obtain the adjusted size information of at least one target partition.

[0088] This step may include, but is not limited to: allocating capacity from the extended storage device that corresponds to the proportion of the target partition as the unused capacity of the target partition, and adjusting the size information of the target partition in the configuration information based on the unused capacity. For example, if the capacity of the extended storage device is 3776 MiB, and the proportions of target partitions 1 to 6 are respectively... The unused capacities of target partitions 1 to 6 are respectively The size information of the target partition is adjusted based on the available capacity, and the adjusted size information of the target partition represents the available capacity of the target partition.

[0089] The target partition information consists of at least the number of target partitions and their adjusted size information.

[0090] Steps S203-S204 are a specific implementation of step S103 in Example 1.

[0091] Step S205: If it is determined that the target partition information and the current partition information do not match, adjust the current partition of the extended storage device based on the target partition information.

[0092] Adjusting the current partition of the extended storage device based on the target partition information can include:

[0093] Based on the number of at least one target partition and the adjusted size information, adjust the capacity of the current partition of the extended storage device.

[0094] In this embodiment, by acquiring configuration information and the capacity and current partition information of at least one extended storage device of the baseboard management controller, the proportion of the target partition's capacity in the total capacity of at least one target partition is determined based on the target partition's size information. Based on the capacity and proportion of the extended storage device, the size information of at least one target partition in the configuration information is adjusted to obtain the adjusted size information of at least one target partition. The quantity information of at least one target partition and the adjusted size information constitute the target partition information. If it is determined that the target partition information and the current partition information do not match, the current partition of the extended storage device is adjusted based on the target partition information. This ensures that for extended storage devices that have been updated, the current partition of the extended storage device can be adjusted without modifying the startup script, thereby improving partitioning efficiency and partitioning cost.

[0095] As another optional embodiment of this application, refer to Figure 3 This is a flowchart illustrating a storage management method provided in Embodiment 3 of this application. This embodiment is mainly a refinement of the storage management method described in Embodiment 2 above. The method may include, but is not limited to, the following steps:

[0096] Step S301: Obtain configuration information. The configuration information includes at least the number and size information of at least one target partition.

[0097] Step S302: Obtain the theoretical capacity, actual capacity, and current partition information of at least one extended storage device of the baseboard management controller. The current partition information is related to at least one current partition of the extended storage device.

[0098] Step S302 is a specific implementation of step S202 in Example 2.

[0099] Step S303: Based on the size information of the target partition, determine the proportion of the capacity of the target partition in the total capacity of at least one target partition.

[0100] For a detailed description of steps S301-S303, please refer to the relevant description of steps S201-S203 in Example 2, which will not be repeated here.

[0101] Step S304: Based on the percentage and the theoretical capacity of the extended storage device, generate initial size information for at least one target partition.

[0102] This step may include, but is not limited to:

[0103] S3041. Allocate capacity from the theoretical capacity of the extended storage device corresponding to the proportion of the target partition, as the theoretical capacity of the target partition, and generate the initial size information of the target partition based on the theoretical capacity of the target partition. For example, if the theoretical capacity of the extended storage device is 4 GiB, and the proportions of target partitions 1 to 6 are respectively... The theoretical capacities of target partitions 1 to 6 are respectively (That is, 1024 MiB), (That is, 512MiB), (That is, 512MiB), (That is, 512MiB), (That is, 1024 MiB), (i.e., 512MiB), the initial size information of the target partition is generated based on the theoretical capacity of the target partition. The initial size information of target partitions 1 to 6 respectively represent the theoretical capacity of the target partition as 1024MiB, 512MiB, 512MiB, 512MiB, 1024MiB, and 512MiB.

[0104] Step S305: Based on the actual capacity of the extended storage device, adjust the initial size information of at least one target partition to obtain the target size information of at least one target partition.

[0105] This step may include, but is not limited to:

[0106] S3051. Divide the actual capacity of the extended storage device according to the proportion, and replace the initial size information of the at least one target partition with the partition size information corresponding to the actual capacity obtained by the division, so as to obtain the target size information of the at least one target partition.

[0107] For example, corresponding to the example described in step S3041, if the actual capacity of the extended storage device is 3776 MiB, according to the proportion of target partitions 1 to 6... The 3776 MiB is divided into four partitions, resulting in actual capacities of 944 MiB, 472 MiB, 472 MiB, 472 MiB, 944 MiB, and 472 MiB, respectively. The initial size information of each target partition is replaced with the partition size information corresponding to 944 MiB, 472 MiB, 472 MiB, 944 MiB, and 472 MiB, respectively, to obtain the target size information of each target partition. The target size information of each target partition represents the capacity of each target partition as 944 MiB, 472 MiB, 472 MiB, 944 MiB, and 472 MiB, respectively.

[0108] Of course, this step may include, but is not limited to:

[0109] S3052. Determine the difference between the theoretical capacity and the actual capacity of the extended storage device, and replace the initial size information of the last target partition in at least one target partition with the partition size information corresponding to the difference to obtain the target size information of at least one target partition.

[0110] Replacing the initial size information of the last target partition in at least one target partition with the partition size information corresponding to the difference may include: subtracting the difference from the capacity represented by the initial size information of the last target partition in at least one target partition to obtain the adjusted capacity of the last target partition, and replacing the initial size information of the last target partition with the partition size information corresponding to the adjusted capacity of the last target partition.

[0111] For example, corresponding to the example described in step S3041, if the actual capacity of the extended storage device is 3776 MiB, and the difference between the theoretical capacity and the actual capacity of the extended storage device is 320 MiB, the initial size information of target partitions 1 to 6 respectively represents the theoretical capacity of the target partitions as 1024 MiB, 512 MiB, 512 MiB, 512 MiB, 1024 MiB, and 512 MiB, respectively. Subtracting 320 MiB from the theoretical capacity of target partition 6 yields the adjusted capacity of the target partition as 192 MiB. The initial size information representing target partition 6 is replaced with the partition size information corresponding to 192 MiB. The adjusted target size information of target partitions 1 to 6 respectively represents the capacity of target partitions 1 to 6 as 1024 MiB, 512 MiB, 512 MiB, 512 MiB, 1024 MiB, and 192 MiB.

[0112] Step S306: Determine the address information of at least one target partition based on the target size information of at least one target partition.

[0113] Among them, the number information and address information of at least one target partition constitute the target partition information.

[0114] This step may include, but is not limited to:

[0115] S3061. Determine the starting address of the first target partition in at least one target partition.

[0116] In this embodiment, the starting address of the first target partition in at least one target partition can be determined, but is not limited to, based on a 16-sector alignment method.

[0117] With the 16-sector alignment method, the starting address of the first target partition is divisible by 1048576.

[0118] S3062. Based on the target size information of at least one target partition and the starting address of the first target partition, determine the ending address of the last target partition in at least one target partition.

[0119] S3063. Based on the starting address of the first target partition and the target size information of each of the other target partitions except the last target partition, determine the starting address and / or ending address of each of the other target partitions.

[0120] At least one target partition has a starting address that is divisible by a set constant value, and the starting address of each target partition is different.

[0121] It should be noted that, for the implementation method that determines the starting address based on 16-sector alignment, the constant value can be set to 1048576.

[0122] In this embodiment, the starting address of each target partition in at least one target partition is divisible by a set constant value, which can guarantee the read and write performance of the target partition.

[0123] This step may also include, but is not limited to:

[0124] S3064. Determine the starting address of the first target partition in at least one target partition.

[0125] This step can be found in the relevant description of step S3061, and will not be repeated here.

[0126] S3065. Based on the target size information of at least one target partition and the starting address of the first target partition, determine the ending address of each target partition except the last target partition in the at least one target partition. The starting address of each target partition is divisible by a set constant value, and the starting address of each target partition is different.

[0127] The difference between the end address and the start address of at least one target partition (excluding the last target partition) is consistent with the capacity represented by the target size information of that target partition.

[0128] The following explanation uses the target size information of the target partition in step S3052 as an example. Specifically, for the implementation method of determining the starting address based on 16-sector alignment, the starting address of the first target partition can be 1048576 bytes. Based on the target size information of at least one target partition and the starting address of the first target partition, the ending address of each target partition except the last target partition is determined as shown in Table 1. As shown in Table 1, mmcblk0p1 to 3 are primary partitions (i.e., of type primary), and mmcblk0p4 is an extended logical partition. The logical partitions, mmcblk0p5 and mmcblk0p6, belong to mmcblk0p4 (i.e., of type logical). The starting addresses of mmcblk0p1 (i.e., the first target partition), mmcblk0p2, mmcblk0p3, mmcblk0p5, and mmcblk0p6 are all divisible by 1048576. The capacity determined by the starting and ending addresses of mmcblk0p1, mmcblk0p2, mmcblk0p3, mmcblk0p5, and mmcblk0p6 is equal to the capacity represented by their target size information.

[0129] Table 1

[0130]

[0131] S3066. Based on the start address and end address of each target partition except the last target partition, determine the capacity loss value of at least one target partition. The capacity loss value is related to the start address being divisible by a set constant value.

[0132] In this embodiment, the capacity loss value of the target partitions other than the last target partition can be determined based on the difference between the starting address of each target partition other than the last target partition and the ending address of its adjacent previous target partition.

[0133] Furthermore, based on the end address of the previous target partition adjacent to the last target partition, the starting address of the last target partition that is divisible by the set constant value is determined, and based on the starting address of the last target partition that is divisible by the set constant value, the capacity consumption value of the last target partition is determined.

[0134] For example, as shown in Table 1, the capacity consumption values ​​represented by mmcblk0p1, mmcblk0p5, and mmcblk0p6 all represent a capacity consumption of 1048576 bytes. Based on the last address of mmcblk0p6, the starting address of the last target partition (i.e., mmcblk0p7) can be determined to be 3762290688. Based on the starting address of mmcblk0p7 (3762290688) and the last address of mmcblk0p6 (3761242111), the capacity consumption value of mmcblk0p7 also represents a capacity consumption of 1048576 bytes.

[0135] The capacity consumption value represents the capacity consumed by the target partition because its starting address is divisible by the set constant value.

[0136] S3067. Determine the capacity of the last target partition based on the target size information of the last target partition.

[0137] S3068. Based on the capacity loss value of at least one target partition and the capacity of the last target partition, determine the available capacity of the last target partition.

[0138] In the example corresponding to step S3065, the capacity of the last target partition is 192 MiB, and the capacity loss value of at least one target partition represents the lost capacity as 1048576Byte + 1048576Byte + 1048576Byte + 1048576Byte = 4 MiB. The difference between the capacity of the last target partition (192 MiB) and the capacity loss value of at least one target partition (4 MiB) is determined as the usable capacity of the last target partition as 188 MiB.

[0139] S3069. Based on the available capacity of the last target partition, determine the start address and end address of the last target partition.

[0140] In this embodiment, the end address of the last target partition is determined based on the available capacity of the last target partition and the start address of the last target partition determined in step S3066. Corresponding to Table 1, given that the start and end addresses of the last target partition are determined, the start and end addresses and capacities of each target partition can be found in Table 2. As shown in Table 2, the start addresses of mmcblk0p1, mmcblk0p2, mmcblk0p3, mmcblk0p5, mmcblk0p6, and mmcblk0p7 are all divisible by 1048576. The capacities determined based on the start and end addresses of mmcblk0p1, mmcblk0p2, mmcblk0p3, mmcblk0p5, and mmcblk0p6 are equal to the capacities represented by their target size information. The capacity of mmcblk0p7 is 188 MiB.

[0141] Table 2

[0142]

[0143]

[0144] Steps S304-S306 are a specific implementation of step S204 in Example 2.

[0145] Step S307: If it is determined that the target partition information and the current partition information do not match, adjust the current partition of the extended storage device based on the target partition information.

[0146] In this embodiment, the current partition information may include, but is not limited to, at least one current partition quantity and address information. This step may include, but is not limited to, the following:

[0147] If the quantity information of at least one target partition and the quantity information of at least one current partition are determined, and / or, the address information of at least one target partition and the address information of at least one current partition do not match, the current partition of the extended storage device is modified to a number consistent with the quantity information of at least one target partition, and / or, based on the address information of at least one target partition, the address of the current partition of the extended storage device is adjusted.

[0148] In this embodiment, by acquiring configuration information and the capacity and current partition information of at least one extended storage device of the baseboard management controller, the proportion of the target partition's capacity in the total capacity of at least one target partition is determined based on the target partition's size information. Based on the proportion and the theoretical capacity of the extended storage device, the initial size information of at least one target partition is generated. Based on the actual capacity of the extended storage device, the initial size information of at least one target partition is adjusted to obtain the target size information of at least one target partition. Based on the target size information of at least one target partition, the address information of at least one target partition is determined. The quantity information and address information of at least one target partition constitute the target partition information. If it is determined that the target partition information and the current partition information do not match, the current partition of the extended storage device is adjusted based on the target partition information. This ensures that for extended storage devices that have been updated, the current partition of the extended storage device can be adjusted without modifying the startup script, thereby improving partitioning efficiency and partitioning cost.

[0149] Furthermore, by determining the capacity loss value of at least one target partition, the capacity of the last target partition is determined based on the target size information of the last target partition. Based on the capacity loss value of at least one target partition and the capacity of the last target partition, the available capacity of the last target partition is determined. Based on the available capacity of the last target partition, the start address and end address of the last target partition are determined, ensuring the accuracy of the start address and end address of each target partition, thereby ensuring the accuracy of adjusting the current partition of the extended storage device.

[0150] As another optional embodiment of this application, refer to Figure 4 This is a flowchart illustrating a storage management method provided in Embodiment 4 of this application. This embodiment is mainly an extension of the storage management method described in Embodiment 2 above. The method may include, but is not limited to, the following steps:

[0151] Step S401: Obtain configuration information. The configuration information includes at least the number and size information of at least one target partition and the target file system type information of at least one target partition.

[0152] At least one target file system type information for the target partition, which may include, but is not limited to: FAT32 type information, NTFS type information, EXT2 type information, EXT3 type information, or EXT4 type information.

[0153] Step S402: Obtain the capacity and current partition information of at least one extended storage device of the baseboard management controller, wherein the current partition information is related to at least one current partition of the extended storage device.

[0154] Step S403: Based on the size information of the target partition, determine the proportion of the capacity of the target partition in the total capacity of at least one target partition.

[0155] Step S404: Based on the capacity and proportion of the extended storage device, adjust the size information of at least one target partition in the configuration information to obtain the adjusted size information of at least one target partition.

[0156] For a detailed description of steps S401-S404, please refer to the relevant description of steps S201-S204 in Example 2, which will not be repeated here.

[0157] Step S405: Determine the target file system type information of at least one target partition as the file system type information of at least one target partition.

[0158] The target partition information consists of at least one file system type information, quantity information, and adjusted size information of the target partition.

[0159] Step S406: If any one or more of the following are mismatched: the number of at least one target partition and the number of at least one current partition, the address information of at least one target partition and the address information of at least one current partition, and the file system type information of at least one target partition and the file system type information of at least one current partition, adjust the current partition of the extended storage device based on the target partition information.

[0160] This step may include, but is not limited to:

[0161] If the quantity information of at least one target partition does not match the quantity information of at least one current partition, adjust the quantity of at least one current partition to match the quantity information of at least one target partition.

[0162] If the quantity information of at least one target partition matches the quantity information of at least one current partition, and if the address information of at least one target partition does not match the address information of at least one current partition, the address information of at least one current partition is adjusted to be consistent with the address information of at least one target partition.

[0163] If the quantity information of at least one target partition matches the quantity information of at least one current partition, and the address information of at least one target partition matches the address information of at least one current partition, the file system type information of at least one current partition is adjusted to be consistent with the file system type information of at least one target partition.

[0164] At least one set of information about the number, address, and file system type of the current partition is a specific implementation of the current partition information.

[0165] In this embodiment, by acquiring configuration information and the capacity and current partition information of at least one extended storage device of the baseboard management controller, the proportion of the target partition's capacity in the total capacity of at least one target partition is determined based on the target partition's size information. Based on the capacity and proportion of the extended storage device, the size information of at least one target partition in the configuration information is adjusted to obtain the adjusted size information of at least one target partition. The target file system type information of at least one target partition is determined as the file system type information of at least one target partition. The file system type information, quantity information, and adjusted size information of at least one target partition constitute the target partition information. If it is determined that the target partition information and the current partition information do not match, the current partition of the extended storage device is adjusted based on the target partition information. This ensures that for extended storage devices that have been updated, the current partition of the extended storage device can be adjusted without modifying the startup script, thereby improving partitioning efficiency and partitioning cost.

[0166] As another optional embodiment of this application, refer to Figure 5 This is a flowchart illustrating a storage management method provided in Embodiment 5 of this application. This embodiment is mainly an extension of the storage management method described in Embodiment 1 above. The method may include, but is not limited to, the following steps:

[0167] Step S501: Obtain configuration information. The configuration information includes at least the number and size information of at least one target partition.

[0168] Step S502: Obtain the capacity and current partition information of at least one extended storage device of the baseboard management controller, wherein the current partition information is related to at least one current partition of the extended storage device.

[0169] Step S503: Determine the target partition information based at least on the configuration information and the capacity of the extended storage device.

[0170] Step S504: If it is determined that the target partition information and the current partition information do not match, adjust the current partition of the extended storage device based on the target partition information.

[0171] For detailed procedures of steps S501-S504, please refer to the relevant description of steps S101-S104 in Example 1, which will not be repeated here.

[0172] Step S505: Determine whether the file system of at least one target partition is a target file system.

[0173] In this embodiment, at least one target partition's partition header information can be obtained, and file system type information can be obtained from the partition header information. By determining whether the obtained file system type information is consistent with the user-defined file system type information, it can be determined whether the file system of the target partition is the target file system. If the obtained file system type information is consistent with the user-defined file system type information, then the file system of the target partition is determined to be the target file system.

[0174] If yes, proceed to step S506; otherwise, proceed to step S510.

[0175] Step S506: Determine whether there are any abnormal file nodes in at least one target partition.

[0176] It is possible, but not limited to, using file system verification tools or referencing open-source verification algorithms to detect the presence of abnormal file nodes in at least one target partition.

[0177] An abnormal file node can be understood as a file node in the target partition of the target file system whose information is corrupted.

[0178] If yes, proceed to step S507; otherwise, proceed to step S508.

[0179] Step S507: Repair abnormal file nodes.

[0180] In this embodiment, abnormal file nodes can be repaired based on file node repair tools or repair algorithms referenced in open-source code, but not limited to this method.

[0181] Step S508: Determine whether the abnormal file node has been restored to a normal file node.

[0182] In this embodiment, it is possible, but not limited to, using file system verification tools or referencing open-source verification algorithms to detect whether there are abnormal file nodes in at least one target partition. If there are no abnormal file nodes, it can be determined that the abnormal file nodes have been restored to normal file nodes.

[0183] If yes, proceed to step S509; otherwise, proceed to step S510.

[0184] Step S509: Perform read / write tests on at least one target partition.

[0185] If the read / write test results of at least one target partition meet the set conditions, the process ends; if the read / write test results of at least one target partition do not meet the set conditions, the first alarm log can be recorded.

[0186] Step S510: Determine whether the number of times the target partition is formatted based on the target file system has reached the file system verification limit.

[0187] The file system verification limit can be set as needed, and is not limited in this application.

[0188] If not, proceed to step S511; if yes, then the second alarm log can be recorded.

[0189] Step S511: Format at least one target partition based on the target file system, and then execute step S509.

[0190] In this embodiment, by obtaining configuration information and the capacity and current partition information of at least one extended storage device of the baseboard management controller, the target partition information is determined based at least on the configuration information and the capacity of the extended storage device. If it is determined that the target partition information and the current partition information do not match, the current partition of the extended storage device is adjusted based on the target partition information. This ensures that for extended storage devices that have been updated, the current partition of the extended storage device can be adjusted without modifying the startup script, thereby improving partitioning efficiency and partitioning cost.

[0191] Furthermore, if at least one target partition uses the target file system, it is further guaranteed that there are no abnormal file nodes in at least one target partition. Based on this, file read and write tests are performed on at least one target partition to reliably verify at least one target partition using the target file system.

[0192] As another optional embodiment of this application, refer to Figure 6 This is a flowchart illustrating a storage management method provided in Embodiment 6 of this application. This embodiment is mainly an extension of the storage management method described in Embodiment 1 above. The method may include, but is not limited to, the following steps:

[0193] Step S601: Obtain configuration information. The configuration information includes at least the number and size information of at least one target partition.

[0194] Step S602: Obtain the capacity and current partition information of at least one extended storage device of the baseboard management controller, wherein the current partition information is related to at least one current partition of the extended storage device.

[0195] Step S603: Determine the target partition information based at least on the configuration information and the capacity of the extended storage device.

[0196] Step S604: If it is determined that the target partition information and the current partition information do not match, adjust the current partition of the extended storage device based on the target partition information.

[0197] For a detailed description of steps S601-S604, please refer to the relevant description of steps S101-S104 in Example 1, which will not be repeated here.

[0198] Step S605: Obtain the kernel report of the baseboard management controller and identify the corrupted file node from the kernel report.

[0199] Step S606: Determine whether the number of corrupted file nodes has reached the first upper limit threshold.

[0200] The first upper limit threshold can be set as needed, and is not restricted in this application.

[0201] If yes, proceed to step S607; otherwise, proceed to step S610.

[0202] Step S607: Record the first alarm information.

[0203] Step S608: Determine whether the baseboard management controller needs to be restarted.

[0204] If yes, proceed to step S609; otherwise, return to step S605.

[0205] Step S609: Restart the baseboard management controller.

[0206] Step S610: Determine whether the number of corrupted file nodes has reached the second upper limit threshold.

[0207] If yes, proceed to step S611; otherwise, proceed to step S612.

[0208] Step S611: Record the second alarm information. The second upper limit threshold is less than the first upper limit threshold.

[0209] The second upper limit threshold can be set as needed and is not restricted in this application, but it must be ensured that the second upper limit threshold is less than the first upper limit threshold.

[0210] Step S612: Determine whether the number of corrupted file nodes has reached the third upper limit threshold, where the third upper limit threshold is less than the second upper limit threshold.

[0211] The third upper limit threshold can be set as needed and is not restricted in this application, but it must be ensured that the third upper limit threshold is less than the second upper limit threshold.

[0212] If not, return to step S605; if yes, proceed to step S613.

[0213] Step S613: Record the third alarm information.

[0214] In this embodiment, while executing steps S605-S612, if the waiting time reaches the first set time, the partition header information of at least one target partition can be obtained. Based on the partition header information of at least one target partition, it can be determined whether the file system of at least one target partition is damaged. If it is damaged, a fourth alarm message is recorded. If it is not damaged, the process returns to the step of obtaining the partition header information of at least one target partition if the waiting time reaches the first set time.

[0215] In this embodiment, by obtaining configuration information and the capacity and current partition information of at least one extended storage device of the baseboard management controller, the target partition information is determined based at least on the configuration information and the capacity of the extended storage device. If it is determined that the target partition information and the current partition information do not match, the current partition of the extended storage device is adjusted based on the target partition information. This ensures that for extended storage devices that have been updated, the current partition of the extended storage device can be adjusted without modifying the startup script, thereby improving partitioning efficiency and partitioning cost.

[0216] Furthermore, by determining whether the number of corrupted file nodes has reached a corresponding threshold, at least one target partition using the corresponding file system is monitored.

[0217] The following section describes a storage management device provided in this application. The storage management device described below can be referred to in correspondence with the storage management method described above.

[0218] Please see Figure 7 The storage management device includes: a first acquisition module 100, a second acquisition module 200, a determination module 300, and an adjustment module 400.

[0219] The first acquisition module 100 is used to acquire configuration information, which includes at least the quantity and size information of at least one target partition.

[0220] The second acquisition module 200 is used to acquire the capacity and current partition information of at least one extended storage device of the baseboard management controller, wherein the current partition information is related to at least one current partition of the extended storage device;

[0221] Module 300 is used to determine target partition information based at least on configuration information and the capacity of the extended storage device;

[0222] The adjustment module 400 is used to adjust the current partition of the extended storage device based on the target partition information when it is determined that the target partition information and the current partition information do not match.

[0223] In this embodiment, the determining module 300 can be specifically used for:

[0224] Based on the size information of the target partition, determine the proportion of the capacity of the target partition in the total capacity of at least one target partition;

[0225] Based on the capacity and proportion of the extended storage device, adjust the size information of at least one target partition in the configuration information to obtain the adjusted size information of at least one target partition;

[0226] The target partition information consists of at least the number of target partitions and their adjusted size information.

[0227] In this embodiment, the capacity of the extended storage device may include: the theoretical capacity and the actual capacity of the extended storage device;

[0228] The process by which module 300 adjusts the size information of at least one target partition in the configuration information based on the capacity and proportion of the extended storage device to obtain the adjusted size information of at least one target partition may specifically include:

[0229] Based on the percentage and the theoretical capacity of the extended storage device, generate initial size information for at least one target partition;

[0230] Based on the actual capacity of the extended storage device, adjust the initial size information of at least one target partition to obtain the target size information of at least one target partition;

[0231] Based on the target size information of at least one target partition, determine the address information of at least one target partition;

[0232] Among them, the number information and address information of at least one target partition constitute the target partition information.

[0233] The process by which the determining module 300 determines the address information of at least one target partition based on the target size information of at least one target partition may specifically include:

[0234] Determine the starting address of the first target partition in at least one target partition;

[0235] Based on the target size information of at least one target partition and the starting address of the first target partition, the ending address of each of the at least one target partitions, excluding the last target partition, is determined. The starting address of each target partition is divisible by a set constant value, and the starting address of each target partition is different.

[0236] Based on the start address and end address of each target partition except the last target partition, determine the capacity loss value of at least one target partition. The capacity loss value is related to the start address being divisible by a set constant value.

[0237] Based on the target size information of the last target partition, determine the capacity of the last target partition;

[0238] Based on the capacity loss value of at least one target partition and the capacity of the last target partition, determine the available capacity of the last target partition.

[0239] Based on the available capacity of the last target partition, determine the start and end addresses of the last target partition.

[0240] In this embodiment, the process by which the determining module 300 adjusts the initial size information of at least one target partition based on the actual capacity of the extended storage device to obtain the target size information of at least one target partition may specifically include:

[0241] According to the proportion, the actual capacity of the extended storage device is divided, and the partition size information corresponding to the actual capacity is used to replace the initial size information of at least one target partition to obtain the target size information of at least one target partition.

[0242] Alternatively, determine the difference between the theoretical capacity and the actual capacity of the extended storage device, replace the initial size information of the last target partition in at least one target partition with the partition size information corresponding to the difference, and obtain the target size information of at least one target partition.

[0243] In this embodiment, the configuration information may further include: target file system type information of at least one target partition;

[0244] Module 300 can also be used for:

[0245] The target file system type information of at least one target partition is determined to be the file system type information of at least one target partition;

[0246] The target partition information consists of at least one file system type information, quantity information, and adjusted size information of the target partition.

[0247] In this embodiment, the current partition information may include: at least one current partition quantity information, address information, and file system type information;

[0248] Accordingly, a mismatch between the target partition information and the current partition information can include:

[0249] There is a mismatch between any one or more of the following: the number of at least one target partition and the number of at least one current partition; the address of at least one target partition and the address of at least one current partition; and the file system type of at least one target partition and the file system type of at least one current partition.

[0250] In this embodiment, the storage management device may further include:

[0251] The verification module is used for:

[0252] If at least one target partition is identified as a target file system, and if at least one target partition is found to contain an abnormal file node, repair the abnormal file node.

[0253] If the abnormal file node is restored to a normal file node, perform read and write tests on at least one target partition;

[0254] If the abnormal file node is not restored to a normal file node, and it is determined that the number of times the target partition is formatted based on the target file system has not reached the file system verification limit, the target partition is formatted based on the target file system, and the read and write test of the target partition is performed.

[0255] If it is determined that the file system of at least one target partition is not the target file system, and if it is determined that the number of times the target partition is formatted based on the target file system has not reached the file system verification limit, the target partition is formatted based on the target file system, and read / write tests are performed on the target partition.

[0256] In this embodiment, the storage management device may further include:

[0257] The monitoring module is used for:

[0258] Obtain the kernel report from the baseboard management controller and identify the corrupted file nodes from the kernel report;

[0259] If the number of corrupted file nodes is determined to have reached the first upper limit threshold, record the first alarm message;

[0260] If it is determined that the baseboard management controller needs to be restarted, restart the baseboard management controller;

[0261] If the number of damaged file nodes does not reach the first upper limit threshold, but reaches the second upper limit threshold, record the second alarm information. The second upper limit threshold is less than the first upper limit threshold.

[0262] If the number of corrupted file nodes does not reach the first upper limit threshold, nor the second upper limit threshold, nor the third upper limit threshold, return to the step of obtaining the kernel report from the baseboard management controller, where the third upper limit threshold is less than the second upper limit threshold;

[0263] If the number of corrupted file nodes does not reach the first upper limit threshold, does not reach the second upper limit threshold, but reaches the third upper limit threshold, record the third alarm information.

[0264] It should be noted that each embodiment focuses on describing the differences from other embodiments, and the same or similar parts between the embodiments can be referred to accordingly. For the device embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiments.

[0265] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0266] For ease of description, the above devices are described in terms of function, divided into various modules. Of course, in implementing this application, the functions of each module can be implemented in one or more software and / or hardware.

[0267] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or some parts of the embodiments of this application.

[0268] The above provides a detailed description of a storage management method and apparatus provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A storage management method applied to a baseboard management controller, the method comprising: obtaining configuration information, the configuration information comprising at least quantity information and size information of at least one target partition; obtaining, from kernel data of the baseboard management controller, capacity of at least one extended storage device of the baseboard management controller and current partition information related to at least one current partition of the extended storage device; determining target partition information based on at least the configuration information and the capacity of the extended storage device; adjusting the current partition of the extended storage device based on the target partition information in a case where the target partition information and the current partition information are determined to be mismatched. 2.The method of claim 1, wherein determining target partition information based on at least the configuration information and the capacity of the extended storage device comprises: determining a proportion of capacity of the target partition in total capacity of the at least one target partition based on the size information of the target partition; adjusting the size information of at least one target partition in the configuration information based on the capacity of the extended storage device and the proportion to obtain adjusted size information of the at least one target partition; the quantity information and the adjusted size information of the at least one target partition constitute the target partition information.

3. The method of claim 2, the extending the capacity of the storage device comprising: theoretical capacity and actual capacity of the extended storage device; adjusting the size information of at least one target partition in the configuration information based on the capacity of the extended storage device and the proportion to obtain adjusted size information of the at least one target partition comprises: generating initial size information of the at least one target partition based on the proportion and the theoretical capacity of the extended storage device; adjusting the initial size information of the at least one target partition based on the actual capacity of the extended storage device to obtain target size information of the at least one target partition; determining address information of the at least one target partition based on the target size information of the at least one target partition; wherein the quantity information and the address information of the at least one target partition constitute the target partition information. 4.The method of claim 3, wherein determining address information of the at least one target partition based on the target size information of the at least one target partition comprises: determining a start address of a first target partition of the at least one target partition; determining an end address of each target partition of the at least one target partition except for a last target partition based on the target size information of the at least one target partition and the start address of the first target partition, wherein the start address of each target partition is divisible by a constant value, and the start address of each target partition is different from each other; determining a capacity loss value of the at least one target partition based on the start address and the end address of each target partition of the at least one target partition except for the last target partition, wherein the capacity loss value is related to the start address being divisible by the constant value. determining a capacity of the last target partition based on the target size information of the last target partition; determining an available capacity of the last target partition based on the capacity loss value of the at least one target partition and the capacity of the last target partition; determining a start address and an end address of the last target partition based on the available capacity of the last target partition.

5. The method of claim 3, wherein the adjusting the initial size information of the at least one target partition based on the actual capacity of the extended storage device to obtain the target size information of the at least one target partition comprises: dividing the actual capacity of the extended storage device according to the proportion, and replacing the initial size information of the at least one target partition with size information of a partition corresponding to the divided actual capacity to obtain the target size information of the at least one target partition; or determining a difference between the theoretical capacity and the actual capacity of the extended storage device, and replacing the initial size information of the last target partition of the at least one target partition with size information of a partition corresponding to the difference to obtain the target size information of the at least one target partition. target file system type information of the at least one target partition; 6. The method of claim 2, the configuration information further comprising: determining the target partition information based on at least the configuration information and the capacity of the extended storage device further comprises: determining the target file system type information of the at least one target partition as file system type information of the at least one target partition; the file system type information, the number information, and the adjusted size information of the at least one target partition constitute the target partition information. number information, address information, and file system type information of the at least one current partition; 7. The method of claim 6, the current partition information comprising: the target partition information and the current partition information do not match, including: any one or more of the number information of the at least one target partition and the number information of the at least one current partition, the address information of the at least one target partition and the address information of the at least one current partition, and the file system type information of the at least one target partition and the file system type information of the at least one current partition do not match.

8. The method of claim 1, further comprising: in a case where it is determined that the file system of the at least one target partition is a target file system, if it is determined that there is an abnormal file node in the at least one target partition, repairing the abnormal file node; if the abnormal file node is restored to a normal file node, performing read-write testing on the at least one target partition; if the abnormal file node is not restored to a normal file node, and if it is determined that a number of times of formatting processing on the at least one target partition based on the target file system does not reach an upper limit of file system verification, performing the formatting processing on the at least one target partition based on the target file system, and performing read-write testing on the at least one target partition. ​ In a case where it is determined that the file system of the at least one target partition is not the target file system, if it is determined that a number of times of formatting processing on the at least one target partition based on the target file system does not reach an upper limit of the file system check, the target file system is used to perform the formatting processing on the at least one target partition, and read-write testing is performed on the at least one target partition.

9. The method of claim 1, further comprising: obtaining a kernel report of the baseboard management controller, determining a number of corrupted file nodes from the kernel report; if it is determined that the number of corrupted file nodes reaches a first upper limit threshold, recording first alarm information; if it is determined that the baseboard management controller needs to be restarted, restarting the baseboard management controller; if the number of corrupted file nodes does not reach the first upper limit threshold and reaches a second upper limit threshold, recording second alarm information, the second upper limit threshold being less than the first upper limit threshold; if the number of corrupted file nodes does not reach the first upper limit threshold, does not reach the second upper limit threshold, and does not reach a third upper limit threshold, returning to perform the step of obtaining the kernel report of the baseboard management controller, the third upper limit threshold being less than the second upper limit threshold; if the number of corrupted file nodes does not reach the first upper limit threshold, does not reach the second upper limit threshold, and reaches the third upper limit threshold, recording third alarm information.

10. A storage management apparatus, comprising: a first obtaining module configured to obtain configuration information, the configuration information comprising at least number information and size information of at least one target partition; a second obtaining module configured to obtain, from kernel data of a baseboard management controller, capacity of at least one extended storage device of the baseboard management controller and current partition information related to at least one current partition of the extended storage device; a determining module configured to determine target partition information based at least on the configuration information and the capacity of the extended storage device; an adjusting module configured to, in a case where it is determined that the target partition information and the current partition information do not match, adjust the current partition of the extended storage device based on the target partition information.

Images