WO2023284174A1 - 一种清理主机端残留路径的方法、装置、设备及存储介质 - Google Patents

一种清理主机端残留路径的方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2023284174A1
WO2023284174A1 PCT/CN2021/127521 CN2021127521W WO2023284174A1 WO 2023284174 A1 WO2023284174 A1 WO 2023284174A1 CN 2021127521 W CN2021127521 W CN 2021127521W WO 2023284174 A1 WO2023284174 A1 WO 2023284174A1
Authority
WO
WIPO (PCT)
Prior art keywords
subordinate
host
abnormal
information
devices
Prior art date
Application number
PCT/CN2021/127521
Other languages
English (en)
French (fr)
Inventor
张振广
Original Assignee
苏州浪潮智能科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 苏州浪潮智能科技有限公司 filed Critical 苏州浪潮智能科技有限公司
Priority to US18/270,219 priority Critical patent/US20240061573A1/en
Publication of WO2023284174A1 publication Critical patent/WO2023284174A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604—Improving or facilitating administration, e.g. storage management
    • G06F3/0605—Improving or facilitating administration, e.g. storage management by facilitating the interaction with a user or administrator
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604—Improving or facilitating administration, e.g. storage management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629—Configuration or reconfiguration of storage systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629—Configuration or reconfiguration of storage systems
    • G06F3/0635—Configuration or reconfiguration of storage systems by changing the path, e.g. traffic rerouting, path reconfiguration
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671—In-line storage system

Definitions

  • the present application relates to the field of storage technologies, and in particular to a method for clearing residual paths at the host end; and also relates to a device, equipment and computer-readable storage medium for clearing residual paths at the host end.
  • volume can be mapped to the host to provide storage space for the host.
  • the host side can discover the device corresponding to the volume through scanning. If multiple links exist, each volume corresponds to multiple devices.
  • multi-path software is generally installed on the host, and the multi-path software will aggregate multiple devices into one multi-path. After the aggregated multipath is formatted according to the specified file system type, and then mounted to the specified directory, the user can use the stored volume normally. When the user no longer uses the stored volume, first dismount the specified directory on the host, then delete the multipath and device on the host, and finally unmap it on the storage.
  • Unmapping through normal steps will not cause residual multipaths and devices. However, if the user does not operate properly and only unmaps the storage without deleting the multipaths and devices on the host, it will cause residual multipaths and devices. For the remaining multi-paths and devices, the existing solution is to manually delete the multi-paths and devices. However, manual deletion of multi-paths and devices not only increases the manual workload, but also risks storage. Because the basis for manual deletion is that the device status is failed, that is, when the device status is failed, the multipath and device are deleted. However, the device status of failed may also be a temporary link abnormality (it will be automatically restored later), rather than the storage. map. Once the device is deleted, it is difficult to restore the link, which seriously affects user services.
  • the purpose of the present application is to provide a method for cleaning the residual path on the host side, which can safely and reliably clean up the residual path on the host side.
  • Another object of the present application is to provide a device, device and computer-readable storage medium for clearing residual paths on the host side, all of which have the above-mentioned technical effects.
  • this application provides a method for cleaning the residual path on the host side, including:
  • obtaining the device information of each subordinate device of the multipath includes:
  • obtaining the device information of each subordinate device of the multipath includes:
  • the determining whether all links corresponding to the subordinate devices are abnormal according to the device information includes:
  • the determining whether all links corresponding to the subordinate devices are abnormal according to the device information includes:
  • the method before obtaining the device information of each subordinate device of the multipath, the method further includes:
  • the supplier of the subordinate equipment is the target supplier, then perform obtaining the equipment information of each subordinate equipment of the multipath and subsequent steps;
  • this application also provides a device for clearing the residual path on the host side, including:
  • the first obtaining module is used to obtain the device information of each subordinate device of the multipath
  • a judging module configured to judge whether all links corresponding to the subordinate devices are abnormal according to the device information
  • the second obtaining module is used to obtain the global identification number and connection information of the subordinate device if the links corresponding to the subordinate device are all abnormal;
  • a query module configured to query the mapping status and mapping of the volume corresponding to the global identification number according to the global identification number and the connection information when the global identification number is not empty and the connection information is successfully obtained.
  • a deletion module configured to delete the multipath and the subordinate device when the volume is not in the mapping state or the mapped host is not the target host.
  • the present application also provides a device for clearing the residual path on the host side, including:
  • a processor configured to implement the steps of the method for cleaning up host-side residual paths as described in any one of the above when executing the computer program.
  • the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the cleaning as described in any one of the above items is realized.
  • the steps of the host-side residual path method are described in any one of the above items.
  • the method for clearing the residual path on the host side includes: obtaining the device information of each subordinate device with multiple paths; judging whether the links corresponding to the subordinate devices are all abnormal according to the device information; If all links are abnormal, obtain the global identification number and connection information of the subordinate device; when the global identification number is not empty and the connection information is successfully obtained, according to the global identification number and the connection information Query the mapping state of the volume corresponding to the global identification number and the mapped host; when the volume is not in the mapping state or the mapped host is not the target host, delete the multipath and the subordinate device.
  • the method for clearing the host-side residual path provided by this application, when it is judged that the link of the multi-path subordinate device is abnormal, further inquires the mapping status of the volume and the mapped host on the storage system, and determines that the volume is not in the In the mapping state, or even if the volume is in the mapping state, but the mapped host is not the target host, the multipath and subordinate devices are deleted on the target host, thereby avoiding accidental deletion caused by temporary link failures and ensuring the deletion of multipath Safe and reliable with subordinate equipment.
  • the device, equipment, and computer-readable storage medium provided by the present application for clearing the residual path at the host end all have the above-mentioned technical effects.
  • FIG. 1 is a schematic flowchart of a method for clearing a host-side residual path provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of a device for clearing the residual path on the host side provided by the embodiment of the present application;
  • FIG. 3 is a schematic diagram of a device for clearing residual paths on a host side provided by an embodiment of the present application.
  • the core of the present application is to provide a method for cleaning the residual path on the host side, which can safely and reliably clean up the residual path on the host side.
  • Another core of the present application is to provide a device, equipment, and computer-readable storage medium for clearing residual paths at the host end, all of which have the above-mentioned technical effects.
  • Figure 1 is a schematic flowchart of a method for clearing the host-side residual path provided by the embodiment of the present application. Referring to Figure 1, the method includes:
  • the device information of the multipath and the subordinate devices of the multipath is acquired on the host. After obtaining the device information of the subordinate devices, it is judged according to the obtained device information whether the links corresponding to the subordinate devices are all abnormal.
  • the acquired device information of the subordinate device is information that can reflect the link state of the subordinate device.
  • the present application does not make a unique limitation on the specific content of the obtained device information, as long as it can reflect the link status of the subordinate device.
  • acquiring the device information of each subordinate device of the multipath includes: acquiring a device state of each of the subordinate devices of the multipath.
  • the judging whether the links corresponding to the subordinate devices are all abnormal according to the device information includes: judging whether the device states of the subordinate devices are all abnormal; if the device states of the subordinate devices are all abnormal, then the The links corresponding to the subordinate devices are all abnormal; if the device states of the subordinate devices are not all abnormal, then the links corresponding to the subordinate devices are not all abnormal.
  • the acquired device information of the subordinate device in this embodiment is the device state of the subordinate device. If the device states of each subordinate device are all failed, that is, they are all abnormal, it indicates that the links corresponding to each subordinate device are abnormal, and at this time, the subsequent steps S103, S104 and S105 are further performed. If the device states of each subordinate device are not all failed, that is, not all are abnormal, it indicates that the corresponding links of each subordinate device are not all abnormal, and the multipath can still be used at this time, and the subsequent steps S103, S104 and S105, and directly end the process of cleaning up the residual path on the host side.
  • the multipath /dev/dm-2 includes two subordinate devices /dev/sdb and /dev/sdc. If the device status of the subordinate device /dev/sdb and the device status of the subordinate device /dev/sdc are both failed, the link corresponding to the subordinate device /dev/sdb and the link corresponding to the subordinate device /dev/sdc are both abnormal; if If the status of either the subordinate device /dev/sdb or the subordinate device /dev/sdc is not failed, then the link corresponding to the subordinate device /dev/sdb and the link corresponding to the subordinate device /dev/sdc are not abnormal.
  • obtaining the device information of each subordinate device of the multipath includes: obtaining a SCSI (Small Computer System Interface, small computer system interface) protocol identifier of each subordinate device of the multipath.
  • the judging whether the links corresponding to the subordinate devices are all abnormal according to the device information includes: judging whether the SCSI protocol identifiers of the subordinate devices are all empty; if the SCSI protocol identifiers of the subordinate devices are all empty , the links corresponding to the subordinate devices are all abnormal; if the SCSI protocol identifiers of the subordinate devices are not all empty, then the links corresponding to the subordinate devices are not all abnormal.
  • the acquired device information of the subordinate device in this embodiment is the SCSI protocol identifier of the subordinate device, that is, scsi_id. If the SCSI protocol identifiers of the subordinate devices are all empty, it indicates that the links corresponding to the subordinate devices are all abnormal, and at this time, the subsequent steps S103, S104 and S105 are further performed. If the SCSI protocol identifiers of the subordinate devices are not all empty, it means that the respective links of the subordinate devices are not all abnormal, and the multipath can still be used at this time, and the subsequent steps S103, S104 and S105 are not executed, and the process ends directly The process of cleaning up the residual path on the host side.
  • the link corresponding to the subordinate device /dev/sdb and the link corresponding to the subordinate device /dev/sdc are not All abnormal.
  • acquiring the device information of each subordinate device of the multipath includes: acquiring the device status and SCSI protocol identifier of each subordinate device of the multipath.
  • the judging whether the links corresponding to the subordinate devices are all abnormal according to the device information includes: judging whether the device states of the subordinate devices are all abnormal and whether the SCSI protocol identifiers of each subordinate device are all empty; If the device states of the subordinate devices are all abnormal and the SCSI protocol identifiers of the subordinate devices are all empty, then the links corresponding to the subordinate devices are all abnormal.
  • the acquired device information of the subordinate device in this embodiment includes the device state and the SCSI protocol identifier of the subordinate device. If the device states of the subordinate devices are not all failed, then the links corresponding to the subordinate devices are not all abnormal, and the subsequent process is directly ended at this time. If the SCSI protocol identifiers of the subordinate devices are not all empty, then the links corresponding to the subordinate devices are not all abnormal, and at this time also directly end the subsequent process. If the device status of each subordinate device is failed, and the SCSI protocol identifier of each subordinate device is empty, it means that the links corresponding to each subordinate device are abnormal. The state of the link corresponding to each subordinate device can be judged more reliably by combining the device status of the subordinate devices and the SCSI protocol identifier.
  • the WWID and the connection information of each subordinate device are further obtained. For example, use the command lsblk-o serial/dev/sd* to obtain the global identification number of the subordinate device /dev/sd*, and obtain the connection information corresponding to the subordinate device /dev/sd* by querying the directory /dev/disk/by_path/, namely target, portal, and scsi_id.
  • the subordinate device's global identification number is not empty, it means that the device is a volume from a storage system (at least it used to be), and if the subordinate device's global identification number is empty, it means that the device is not a volume from a storage system. If the connection information is obtained successfully, it means that the storage system from which the device comes can be known; if the connection information is not obtained successfully, it means that it is impossible to know which storage system the device comes from.
  • the target host refers to the host that executes the above steps to clear the residual path. If the volume corresponding to the global identification number of the subordinate device is not in the mapping state, or although the volume corresponding to the global identification number of the subordinate device is in the mapping state, but the mapped host is not the target host, it means that the link abnormality is permanent. It may be automatically restored. At this time, you can delete the multipath through the command multipath-f/dev/dm-*, and delete the subordinate device through the command echo 1>/sys/block/sd*/device/delete. If the volume corresponding to the global identification number of the subordinate device is in the mapping state and the mapped host is the target host, it means that the link abnormality is temporary and may be automatically recovered later. At this time, the multipath and the subordinate device are not deleted.
  • obtaining the device information of each subordinate device of the multipath it also includes: obtaining the vendor information of the subordinate device; judging whether the supplier of the subordinate device is a target according to the vendor information Supplier; if the supplier of the subordinate equipment is the target supplier, then perform the equipment information acquisition of each subordinate equipment of multipath and subsequent steps; if the supplier of the subordinate equipment is not the target supplier, then finish cleaning the host The process of terminal residual path.
  • step S101 and subsequent steps If the supplier of the subordinate equipment is not the target supplier, step S101 and subsequent steps are not executed.
  • step S101 and subsequent steps For example, if the target supplier is Inspur, if the supplier of the subordinate equipment is Inspur, perform step S101 and subsequent steps. If the supplier of the subordinate equipment is not Inspur, then step S101 and subsequent steps will not be executed.
  • the method for clearing the host-side residual path provided by this application, when it is judged that the link of the multi-path subordinate device is abnormal, further queries the storage system for the mapping status of the volume and the mapped host, and determines When the volume is not in the mapping state, or even if the volume is in the mapping state, but the mapped host is not the target host, delete the multipath and subordinate devices on the target host, thereby avoiding accidental deletion caused by temporary link failures and ensuring Removing multi-path and subordinate devices is safe and reliable.
  • FIG. 2 is a schematic diagram of a device for clearing the residual path on the host side provided by the embodiment of the present application. As shown in Figure 2, the device includes:
  • the first obtaining module 10 is used to obtain the device information of each subordinate device of the multipath;
  • a judging module 20 configured to judge whether all the links corresponding to the subordinate devices are abnormal according to the device information
  • the second obtaining module 30 is configured to obtain the global identification number and connection information of the subordinate device if the links corresponding to the subordinate device are abnormal;
  • the query module 40 is configured to query the mapping status and mapping of the volume corresponding to the global identification number according to the global identification number and the connection information when the global identification number is not empty and the connection information is obtained successfully the host;
  • the deletion module 50 is configured to delete the multi-path and the subordinate device when the volume is not in the mapped state or the mapped host is not the target host.
  • the first acquiring module 10 is specifically configured to:
  • the first acquiring module 10 is specifically configured to:
  • the judging module 20 is specifically used for:
  • the judging module 20 is specifically used for:
  • An end module configured to end the process of cleaning up the residual path on the host side when the global identification number is empty or the connection information cannot be obtained successfully.
  • the third obtaining module is used to obtain the manufacturer information of the subordinate equipment
  • the supplier judging module is used to judge whether the supplier of the subordinate equipment is a target supplier according to the manufacturer information; information and subsequent steps; if the supplier of the subordinate device is not the target supplier, then end the process of cleaning the residual path on the host side.
  • the device for clearing the residual path on the host side provided by this application, when it is judged that the link of the multi-path subordinate device is abnormal, further inquires the mapping state of the volume and the mapped host on the storage system, and determines that the volume is not in the mapping state , or even if the volume is in the mapping state, but the mapped host is not the target host, delete the multipath and subordinate devices on the target host, thereby avoiding accidental deletion caused by temporary link failures and ensuring the deletion of multipath and subordinate devices.
  • the equipment is safe and reliable.
  • the present application also provides a device for clearing residual paths on the host side, as shown in FIG. 3 , the device includes a memory 1 and a processor 2 .
  • Memory 1 used to store computer programs
  • Processor 2 configured to execute a computer program to implement the following steps:
  • the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the following steps can be realized:
  • the computer-readable storage medium may include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc., which can store program codes. medium.
  • each embodiment in the description is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same and similar parts of each embodiment can be referred to each other.
  • the description is relatively simple, and for related details, please refer to the description of the method part.
  • RAM random access memory
  • ROM read-only memory
  • EEPROM electrically programmable ROM
  • EEPROM electrically erasable programmable ROM
  • registers hard disk, removable disk, CD-ROM, or any other Any other known storage medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Debugging And Monitoring (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种清理主机端残留路径的方法，包括：获取多路径的各下属设备的设备信息（S101）；根据设备信息判断下属设备对应的链路是否都异常（S102）；若下属设备对应的链路都异常，获取下属设备的全球识别号与连接信息（S103）；当全球识别号不为空且成功获取到连接信息时，根据全球识别号与连接信息查询全球识别号对应的卷的映射状态与映射的主机（S104）；当卷不处于映射状态或映射的主机不是目标主机时，删除多路径与下属设备（S105）。应用该方法能够安全可靠的清理主机端的残留路径。

Description

一种清理主机端残留路径的方法、装置、设备及存储介质
本申请要求在2021年07月12日提交中国专利局、申请号为202110784141.7、发明名称为“一种清理主机端残留路径的方法、装置以及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及存储技术领域，特别涉及一种清理主机端残留路径的方法；还涉及一种清理主机端残留路径的装置、设备以及计算机可读存储介质。
背景技术
存储系统与主机连接后，可以将卷映射到主机，以便给主机提供存储空间。主机端通过扫描可以发现卷对应的设备。如果存在多条链路，在每个卷对应多个设备。为了保证路径的高可用，一般主机上安装有多路径软件，多路径软件会将多个设备聚合成一条多路径。对聚合的多路径按照指定的文件系统类型格式化，然后将其挂接到指定目录后，用户就可以正常使用存储的卷。当用户不再使用存储的卷时，首先在主机上卸除指定目录，然后在主机上删除多路径与设备，最后在存储上解除映射。
通过正常的步骤解除映射不会造成多路径与设备残留，但是，如果用户操作不当，只在存储上解除映射，而没有在主机上删除多路径与设备，就会造成多路径和设备的残留。针对残留的多路径与设备，现有解决方案是手动删除多路径与设备，然而手动删除多路径与设备不仅增加了人工的工作量，而且存储一定的风险。因为手动删除的依据是设备状态为failed，即当设备状态为failed时删除多路径与设备，然而设备状态为failed也可能是暂时的链路异常(后续会自动恢复)，而非存储上已解除映射。设备一旦删除，链路再难恢复，由此严重影响到用户业务。
有鉴于此，如何安全可靠的清理主机端的残留路径已成为本领域技术人员亟待解决的技术问题。
发明内容
本申请的目的是提供一种清理主机端残留路径的方法，能够安全可靠的清理主机端的残留路径。本申请的另一个目的是提供一种清理主机端残留路径的装置、设备以及计算机可读存储介质，均具有上述技术效果。
为解决上述技术问题，本申请提供了一种清理主机端残留路径的方法，包括：
获取多路径的各下属设备的设备信息；
根据所述设备信息判断所述下属设备对应的链路是否都异常；
若所述下属设备对应的链路都异常，则获取所述下属设备的全球识别号与连接信息；
当所述全球识别号不为空且成功获取到所述连接信息时，根据所述全球识别号与所述连接信息查询所述全球识别号对应的卷的映射状态与映射的主机；
当所述卷不处于映射状态或映射的所述主机不是目标主机时，删除所述多路径与所述下属设备。
可选的，获取多路径的各下属设备的设备信息包括：
获取所述多路径的各所述下属设备的设备状态。
可选的，获取多路径的各下属设备的设备信息包括：
获取所述多路径的各所述下属设备的SCSI协议标识。
可选的，所述根据所述设备信息判断所述下属设备对应的链路是否都异常包括：
判断所述下属设备的设备状态是否都异常；
若所述下属设备的设备状态都是异常，则所述下属设备对应的链路都异常；
若所述下属设备的设备状态不都是异常，则所述下属设备对应的所述链路不都异常。
可选的，所述根据所述设备信息判断所述下属设备对应的链路是否都异常包括：
判断所述下属设备的SCSI协议标识是否都为空；
若所述下属设备的SCSI协议标识都为空，则所述下属设备对应的链路都异常；
若所述下属设备的SCSI协议标识不都为空，则所述下属设备对应的链路不都异常。
可选的，还包括：
当所述全球识别号为空或未能成功获取到所述连接信息时，结束清理主机端残留路径的流程。
可选的，所述获取多路径的各下属设备的设备信息前还包括：
获取所述下属设备的厂商信息；
根据所述厂商信息判断所述下属设备的供应商是否为目标供应商；
若所述下属设备的供应商为目标供应商，则执行获取多路径的各下属设备的设备信息以及后续步骤；
若所述下属设备的供应商不为目标供应商，则结束清理主机端残留路径的流程。
为解决上述技术问题，本申请还提供了一种清理主机端残留路径的装置，包括：
第一获取模块，用于获取多路径的各下属设备的设备信息；
判断模块，用于根据所述设备信息判断所述下属设备对应的链路是否都异常；
第二获取模块，用于若所述下属设备对应的链路都异常，则获取所述下属设备的全球识别号与连接信息；
查询模块，用于当所述全球识别号不为空且成功获取到所述连接信息时，根据所述全球识别号与所述连接信息查询所述全球识别号对应的卷的映射状态与映射的主机；
删除模块，用于当所述卷不处于映射状态或映射的所述主机不是目标主机时，删除所述多路径与所述下属设备。
为解决上述技术问题，本申请还提供了一种清理主机端残留路径的设备，包括：
存储器，用于存储计算机程序；
处理器，用于执行所述计算机程序时实现如上任一项所述的清理主机端 残留路径的方法的步骤。
为解决上述技术问题，本申请还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如上任一项所述的清理主机端残留路径的方法的步骤。
本申请所提供的清理主机端残留路径的方法，包括：获取多路径的各下属设备的设备信息；根据所述设备信息判断所述下属设备对应的链路是否都异常；若所述下属设备对应的链路都异常，则获取所述下属设备的全球识别号与连接信息；当所述全球识别号不为空且成功获取到所述连接信息时，根据所述全球识别号与所述连接信息查询所述全球识别号对应的卷的映射状态与映射的主机；当所述卷不处于映射状态或映射的所述主机不是目标主机时，删除所述多路径与所述下属设备。
可见，本申请所提供的清理主机端残留路径的方法，在判断出多路径的下属设备的链路异常时，进一步去存储系统上查询卷的映射状态与映射的主机，并在确定卷不处于映射状态，或者即使卷处于映射状态，但是所映射的主机不是目标主机时，才在目标主机上删除多路径与下属设备，由此可以避免暂时的链路故障导致的误删，保障删除多路径与下属设备的安全可靠。
本申请所提供的清理主机端残留路径的装置、设备以及计算机可读存储介质均具有上述技术效果。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对现有技术和实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例所提供的一种清理主机端残留路径的方法的流程示意图；
图2为本申请实施例所提供的一种清理主机端残留路径的装置的示意图；
图3为本申请实施例所提供的一种清理主机端残留路径的设备的示意图。
具体实施方式
本申请的核心是提供一种清理主机端残留路径的方法，能够安全可靠的清理主机端的残留路径。本申请的另一个核心是提供一种清理主机端残留路径的装置、设备以及计算机可读存储介质，均具有上述技术效果。
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
请参考图1，图1为本申请实施例所提供的一种清理主机端残留路径的方法的流程示意图，参考图1所示，该方法包括：
S101：获取多路径的各下属设备的设备信息；
S102：根据所述设备信息判断所述下属设备对应的链路是否都异常；
具体的，在主机上获取多路径以及多路径的下属设备的设备信息。在获取到下属设备的设备信息后，根据所获取的设备信息判断下属设备对应的链路是否都异常。
其中，所获取的下属设备的设备信息是能够反映出下属设备的链路状态的信息。对于所获取的设备信息的具体内容，本申请不做唯一限定，能够反映出下属设备的链路状态即可。
在第一种具体的实施方式中，获取多路径的各下属设备的设备信息包括：获取所述多路径的各所述下属设备的设备状态。相应的，所述根据所述设备信息判断所述下属设备对应的链路是否都异常包括：判断所述下属设备的设备状态是否都异常；若所述下属设备的设备状态都是异常，则所述下属设备对应的链路都异常；若所述下属设备的设备状态不都是异常，则所述下属设备对应的所述链路不都异常。
具体而言，本实施例中所获取的下属设备的设备信息为下属设备的设备状态。如果各下属设备的设备状态都是failed，即都是异常，则表明各下属设备对应的链路均异常，此时进一步执行后续步骤S103、S104以及S105。如果各下属设备的设备状态不都是failed，即不都是异常，则表明各下属设备各自对应的链路不都异常，此时多路径仍可继续使用，不再执行后续步骤S103、 S104以及S105，而直接结束清理主机端残留路径的流程。
例如，通过命令multipath-ll/dev/dm-*获取多路径/dev/dm-2，多路径/dev/dm-2包含两个下属设备/dev/sdb和/dev/sdc。若下属设备/dev/sdb的设备状态与下属设备/dev/sdc的设备状态均为failed，则下属设备/dev/sdb对应的链路与下属设备/dev/sdc对应的链路都异常；若下属设备/dev/sdb与下属设备/dev/sdc中的任意一个的设备状态不是failed，则下属设备/dev/sdb对应的链路与下属设备/dev/sdc对应的链路不都异常。
在第二种具体的实施方式中，获取多路径的各下属设备的设备信息包括：获取所述多路径的各所述下属设备的SCSI(Small Computer System Interface，小型计算机系统接口)协议标识。相应的，所述根据所述设备信息判断所述下属设备对应的链路是否都异常包括：判断所述下属设备的SCSI协议标识是否都为空；若所述下属设备的SCSI协议标识都为空，则所述下属设备对应的链路都异常；若所述下属设备的SCSI协议标识不都为空，则所述下属设备对应的链路不都异常。
具体而言，本实施例中所获取的下属设备的设备信息为下属设备的SCSI协议标识即scsi_id。如果各下属设备的SCSI协议标识都为空，则表明各下属设备对应的链路均异常，此时进一步执行后续步骤S103、S104以及S105。如果各下属设备的SCSI协议标识不都为空，则表明各下属设备各自对应的链路不都异常，此时多路径仍可继续使用，不再执行后续步骤S103、S104以及S105，而直接结束清理主机端残留路径的流程。
例如，通过命令/lib/udev/scsi_id--whitelisted-page＝0x83-device＝/dev/sd*获取下属设备/dev/sd*的SCSI协议标识。若下属设备/dev/sdb的SCSI协议标识与下属设备/dev/sdc的SCSI协议标识均为空，则下属设备/dev/sdb对应的链路与下属设备/dev/sdc对应的链路都异常；若下属设备/dev/sdb与下属设备/dev/sdc中的任意一个的SCSI协议标识不为空，则下属设备/dev/sdb对应的链路与下属设备/dev/sdc对应的链路不都异常。
在第三种具体的实施方式中，获取多路径的各下属设备的设备信息包括：获取所述多路径的各所述下属设备的设备状态与SCSI协议标识。相应的，所述根据所述设备信息判断所述下属设备对应的链路是否都异常包括：判断所述下属设备的设备状态是否都异常以及各下属设备的SCSI协议标识是否都为 空；若所述下属设备的设备状态都是异常且所述下属设备的SCSI协议标识都为空，则所述下属设备对应的链路都异常。
具体而言，本实施例中所获取的下属设备的设备信息包括下属设备的设备状态与SCSI协议标识。如果各下属设备的设备状态不都是failed，则所述下属设备对应的所述链路不都异常，此时直接结束后续流程。如果各下属设备的SCSI协议标识不都为空，则所述下属设备对应的所述链路不都异常，此时同样直接结束后续流程。如果各下属设备的设备状态都是failed，且各下属设备的SCSI协议标识均为空，则说明各下属设备对应的链路都异常。综合下属设备的设备状态与SCSI协议标识，可以更加可靠的判断出各下属设备对应的链路的状态。
S103：若所述下属设备对应的链路都异常，则获取所述下属设备的全球识别号与连接信息；
S104：当所述全球识别号不为空且成功获取到所述连接信息时，根据所述全球识别号与所述连接信息查询所述全球识别号对应的卷的映射状态与映射的主机；
具体的，当判断出多路径的各下属设备对应的链路都异常时，进一步获取各下属设备的全球识别号即WWID与连接信息。例如，通过命令lsblk-o serial/dev/sd*获取下属设备/dev/sd*的全球识别号，通过查询目录/dev/disk/by_path/获取下属设备/dev/sd*对应的连接信息，即target、portal和scsi_id。
如果下属设备的全球识别号不为空，说明该设备是来自某存储系统的卷(至少曾经是)，如果下属设备的全球识别号为空，则说明该设备不是来自某存储系统的卷。如果连接信息获取成功，说明可以获知该设备来自哪个存储系统，如果连接信息获取不成功，则说明无法获知该设备来自哪个存储系统。
因此，在所述全球识别号不为空且成功获取到所述连接信息的情况下，根据所述全球识别号与所述连接信息，到指定的存储系统查询所述全球识别号对应的卷的映射状态与映射的主机。而在所述全球识别号为空或未能成功获取到所述连接信息的情况下，直接结束清理主机端残留路径的流程。
S105：当所述卷不处于映射状态或映射的所述主机不是目标主机时，删除所述多路径与所述下属设备。
具体的，目标主机是指执行上述步骤，要清除残留路径的主机。如果下属设备的全球识别号对应的卷不处于映射状态，或者虽然下属设备的全球识别号对应的卷处于映射状态，但是所映射的主机不是目标主机，则说明链路异常是永久的，后续不可能自动恢复，此时可以通过命令multipath-f/dev/dm-*删除多路径，以及通过命令echo 1>/sys/block/sd*/device/delete删除下属设备。如果下属设备的全球识别号对应的卷处于映射状态且所映射的主机是目标主机，则说明链路异常是暂时的，后续可能自动恢复，此时不删除多路径与下属设备。
进一步，在一种具体的实施方式中，获取多路径的各下属设备的设备信息前还包括：获取所述下属设备的厂商信息；根据所述厂商信息判断所述下属设备的供应商是否为目标供应商；若所述下属设备的供应商为目标供应商，则执行获取多路径的各下属设备的设备信息以及后续步骤；若所述下属设备的供应商不为目标供应商，则结束清理主机端残留路径的流程。
具体而言，可通过命令lsblk-l-S-o+UUID/dev/sd*获取下属设备/dev/sd*的厂商信息。如果下属设备的供应商为目标供应商，则执行步骤S101及后续步骤。如果下属设备的供应商不是目标供应商，则不再执行步骤S101及后续步骤。
例如，目标供应商为浪潮，如果下属设备的供应商为浪潮，则执行步骤S101及后续步骤。如果下属设备的供应商不是浪潮，则不再执行步骤S101及后续步骤。
综上所述，本申请所提供的清理主机端残留路径的方法，在判断出多路径的下属设备的链路异常时，进一步去存储系统上查询卷的映射状态与映射的主机，并在确定卷不处于映射状态，或者即使卷处于映射状态，但是所映射的主机不是目标主机时，才在目标主机上删除多路径与下属设备，由此可以避免暂时的链路故障导致的误删，保障删除多路径与下属设备的安全可靠。
本申请还提供了一种清理主机端残留路径的装置，下文描述的该装置可以与上文描述的方法相互对应参照。请参考图2，图2为本申请实施例所提供的一种清理主机端残留路径的装置示意图，结合图2所示，该装置包括：
第一获取模块10，用于获取多路径的各下属设备的设备信息；
判断模块20，用于根据所述设备信息判断所述下属设备对应的链路是否都异常；
第二获取模块30，用于若所述下属设备对应的链路都异常，则获取所述下属设备的全球识别号与连接信息；
查询模块40，用于当所述全球识别号不为空且成功获取到所述连接信息时，根据所述全球识别号与所述连接信息查询所述全球识别号对应的卷的映射状态与映射的主机；
删除模块50，用于当所述卷不处于映射状态或映射的所述主机不是目标主机时，删除所述多路径与所述下属设备。
在上述实施例的基础上，可选的，所述第一获取模块10具体用于：
获取所述多路径的各所述下属设备的设备状态。
在上述实施例的基础上，可选的，所述第一获取模块10具体用于：
获取所述多路径的各所述下属设备的SCSI协议标识。
在上述实施例的基础上，可选的，所述判断模块20具体用于：
判断所述下属设备的设备状态是否都异常；
若所述下属设备的设备状态都是异常，则所述下属设备对应的链路都异常；
若所述下属设备的设备状态不都是异常，则所述下属设备对应的所述链路不都异常。
在上述实施例的基础上，可选的，所述判断模块20具体用于：
判断所述下属设备的SCSI协议标识是否都为空；
若所述下属设备的SCSI协议标识都为空，则所述下属设备对应的链路都异常；
若所述下属设备的SCSI协议标识不都为空，则所述下属设备对应的链路不都异常。
在上述实施例的基础上，可选的，还包括：
结束模块，用于当所述全球识别号为空或未能成功获取到所述连接信息时，结束清理主机端残留路径的流程。
在上述实施例的基础上，可选的，还包括：
第三获取模块，用于获取所述下属设备的厂商信息；
供应商判断模块，用于根据所述厂商信息判断所述下属设备的供应商是否为目标供应商；若所述下属设备的供应商为目标供应商，则执行获取多路径的各下属设备的设备信息以及后续步骤；若所述下属设备的供应商不为目标供应商，则结束清理主机端残留路径的流程。
本申请所提供的清理主机端残留路径的装置，在判断出多路径的下属设备的链路异常时，进一步去存储系统上查询卷的映射状态与映射的主机，并在确定卷不处于映射状态，或者即使卷处于映射状态，但是所映射的主机不是目标主机时，才在目标主机上删除多路径与下属设备，由此可以避免暂时的链路故障导致的误删，保障删除多路径与下属设备的安全可靠。
本申请还提供了一种清理主机端残留路径的设备，参考图3所示，该设备包括存储器1和处理器2。
存储器1，用于存储计算机程序；
处理器2，用于执行计算机程序实现如下的步骤：
获取多路径的各下属设备的设备信息；根据所述设备信息判断所述下属设备对应的链路是否都异常；若所述下属设备对应的链路都异常，则获取所述下属设备的全球识别号与连接信息；当所述全球识别号不为空且成功获取到所述连接信息时，根据所述全球识别号与所述连接信息查询所述全球识别号对应的卷的映射状态与映射的主机；当所述卷不处于映射状态或映射的所述主机不是目标主机时，删除所述多路径与所述下属设备。
对于本申请所提供的设备的介绍请参照上述方法实施例，本申请在此不做赘述。
本申请还提供了一种计算机可读存储介质，该计算机可读存储介质上存储有计算机程序，计算机程序被处理器执行时可实现如下的步骤：
获取多路径的各下属设备的设备信息；根据所述设备信息判断所述下属设备对应的链路是否都异常；若所述下属设备对应的链路都异常，则获取所述下属设备的全球识别号与连接信息；当所述全球识别号不为空且成功获取到所述连接信息时，根据所述全球识别号与所述连接信息查询所述全球识别号对应的卷的映射状态与映射的主机；当所述卷不处于映射状态或映射的所述主机不是目标主机时，删除所述多路径与所述下属设备。
该计算机可读存储介质可以包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
对于本申请所提供的计算机可读存储介质的介绍请参照上述方法实施例，本申请在此不做赘述。
说明书中各个实施例采用递进的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似部分互相参见即可。对于实施例公开的装置、设备以及计算机可读存储介质而言，由于其与实施例公开的方法相对应，所以描述的比较简单，相关之处参见方法部分说明即可。
专业人员还可以进一步意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
结合本文中所公开的实施例描述的方法或算法的步骤可以直接用硬件、处理器执行的软件模块，或者二者的结合来实施。软件模块可以置于随机存储器(RAM)、内存、只读存储器(ROM)、电可编程ROM、电可擦除可编程ROM、寄存器、硬盘、可移动磁盘、CD-ROM、或技术领域内所公知的任意其它形式的存储介质中。
以上对本申请所提供的清理主机端残留路径的方法、装置、设备以及计算机可读存储介质进行了详细介绍。本文中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想。应当指出，对于本技术领域的普通技术人员来说，在不脱离本申请原理的前提下，还可以对本申请进行若干改进和修饰，这些改进和修饰也落入本申请权利要求的保护范围。

Claims (12)

  1. 一种清理主机端残留路径的方法，其特征在于，包括：
    获取多路径的各下属设备的设备信息；
    根据所述设备信息判断所述下属设备对应的链路是否都异常；
    若所述下属设备对应的链路都异常，则获取所述下属设备的全球识别号与连接信息；
    当所述全球识别号不为空且成功获取到所述连接信息时，根据所述全球识别号与所述连接信息查询所述全球识别号对应的卷的映射状态与映射的主机；
    当所述卷不处于映射状态或映射的所述主机不是目标主机时，删除所述多路径与所述下属设备。
  2. 根据权利要求1所述的清理主机端残留路径的方法，其特征在于，获取多路径的各下属设备的设备信息包括：
    获取所述多路径的各所述下属设备的设备状态。
  3. 根据权利要求1所述的清理主机端残留路径的方法，其特征在于，获取多路径的各下属设备的设备信息包括：
    获取所述多路径的各所述下属设备的SCSI协议标识。
  4. 根据权利要求2所述的清理主机端残留路径的方法，其特征在于，所述根据所述设备信息判断所述下属设备对应的链路是否都异常包括：
    判断所述下属设备的设备状态是否都异常；
    若所述下属设备的设备状态都是异常，则所述下属设备对应的链路都异常；
    若所述下属设备的设备状态不都是异常，则所述下属设备对应的所述链路不都异常。
  5. 根据权利要求3所述的清理主机端残留路径的方法，其特征在于，所述根据所述设备信息判断所述下属设备对应的链路是否都异常包括：
    判断所述下属设备的SCSI协议标识是否都为空；
    若所述下属设备的SCSI协议标识都为空，则所述下属设备对应的链路都异常；
    若所述下属设备的SCSI协议标识不都为空，则所述下属设备对应的链路不都异常。
  6. 根据权利要求1所述的清理主机端残留路径的方法，其特征在于，还包括：
    当所述全球识别号为空或未能成功获取到所述连接信息时，结束清理主机端残留路径的流程。
  7. 根据权利要求1所述的清理主机端残留路径的方法，其特征在于，所述获取多路径的各下属设备的设备信息前还包括：
    获取所述下属设备的厂商信息；
    根据所述厂商信息判断所述下属设备的供应商是否为目标供应商；
    若所述下属设备的供应商为目标供应商，则执行获取多路径的各下属设备的设备信息以及后续步骤；
    若所述下属设备的供应商不为目标供应商，则结束清理主机端残留路径的流程。
  8. 根据权利要求1至7中任一项所述的清理主机端残留路径的方法，其特征在于，所述设备信息是能够反映出所述下属设备的链路状态的信息。
  9. 一种清理主机端残留路径的装置，其特征在于，包括：
    第一获取模块，用于获取多路径的各下属设备的设备信息；
    判断模块，用于根据所述设备信息判断所述下属设备对应的链路是否都异常；
    第二获取模块，用于若所述下属设备对应的链路都异常，则获取所述下属设备的全球识别号与连接信息；
    查询模块，用于当所述全球识别号不为空且成功获取到所述连接信息时，根据所述全球识别号与所述连接信息查询所述全球识别号对应的卷的映射状态与映射的主机；
    删除模块，用于当所述卷不处于映射状态或映射的所述主机不是目标主机时，删除所述多路径与所述下属设备。
  10. 根据权利要求9所述的清理主机端残留路径的装置，其特征在于，所述设备信息是能够反映出所述下属设备的链路状态的信息。
  11. 一种清理主机端残留路径的设备，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于执行所述计算机程序时实现如权利要求1至8任一项所述的清理主机端残留路径的方法的步骤。
  12. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至8任一项所述的清理主机端残留路径的方法的步骤。
PCT/CN2021/127521 2021-07-12 2021-10-29 一种清理主机端残留路径的方法、装置、设备及存储介质 WO2023284174A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/270,219 US20240061573A1 (en) 2021-07-12 2021-10-29 Method, apparatus, and device for cleaning residual paths on host end, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110784141.7 2021-07-12
CN202110784141.7A CN113238719B (zh) 2021-07-12 2021-07-12 一种清理主机端残留路径的方法、装置以及设备

Publications (1)

Publication Number Publication Date
WO2023284174A1 true WO2023284174A1 (zh) 2023-01-19

Family

ID=77135421

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/127521 WO2023284174A1 (zh) 2021-07-12 2021-10-29 一种清理主机端残留路径的方法、装置、设备及存储介质

Country Status (3)

Country Link
US (1) US20240061573A1 (zh)
CN (1) CN113238719B (zh)
WO (1) WO2023284174A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113238719B (zh) * 2021-07-12 2021-10-15 苏州浪潮智能科技有限公司 一种清理主机端残留路径的方法、装置以及设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104423889A (zh) * 2013-08-26 2015-03-18 国际商业机器公司 一种多路径管理方法和系统
US20200074409A1 (en) * 2018-08-29 2020-03-05 Launch Tech Co., Ltd. Device management method, device management server and computer readable storage medium
CN111352899A (zh) * 2018-12-24 2020-06-30 中兴通讯股份有限公司 路径聚合方法、访问方法及通信设备、存储介质
CN111901399A (zh) * 2020-07-08 2020-11-06 苏州浪潮智能科技有限公司 云平台块设备异常审计方法、装置、设备及存储介质
CN111988169A (zh) * 2020-07-29 2020-11-24 苏州浪潮智能科技有限公司 一种云平台异常磁盘清理修复的方法、系统、设备及介质
CN113238719A (zh) * 2021-07-12 2021-08-10 苏州浪潮智能科技有限公司 一种清理主机端残留路径的方法、装置以及设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104423889A (zh) * 2013-08-26 2015-03-18 国际商业机器公司 一种多路径管理方法和系统
US20200074409A1 (en) * 2018-08-29 2020-03-05 Launch Tech Co., Ltd. Device management method, device management server and computer readable storage medium
CN111352899A (zh) * 2018-12-24 2020-06-30 中兴通讯股份有限公司 路径聚合方法、访问方法及通信设备、存储介质
CN111901399A (zh) * 2020-07-08 2020-11-06 苏州浪潮智能科技有限公司 云平台块设备异常审计方法、装置、设备及存储介质
CN111988169A (zh) * 2020-07-29 2020-11-24 苏州浪潮智能科技有限公司 一种云平台异常磁盘清理修复的方法、系统、设备及介质
CN113238719A (zh) * 2021-07-12 2021-08-10 苏州浪潮智能科技有限公司 一种清理主机端残留路径的方法、装置以及设备

Also Published As

Publication number Publication date
US20240061573A1 (en) 2024-02-22
CN113238719B (zh) 2021-10-15
CN113238719A (zh) 2021-08-10

Similar Documents

Publication Publication Date Title
US7587627B2 (en) System and method for disaster recovery of data
US8010836B2 (en) Storage configuration recovery method and storage management system
US8706694B2 (en) Continuous data protection of files stored on a remote storage device
US8799709B2 (en) Snapshot management method, snapshot management apparatus, and computer-readable, non-transitory medium
US20060236050A1 (en) Computer system, computer, and remote copy processing method
WO2021088254A1 (zh) 一种用户态网络文件系统双栈访问方法、装置及设备
US20210406216A1 (en) Managing Volume Snapshots in the Cloud
US20120095971A1 (en) Online file system consistency check
CN110535692A (zh) 故障处理方法、装置、计算机设备、存储介质及存储系统
WO2023284174A1 (zh) 一种清理主机端残留路径的方法、装置、设备及存储介质
WO2012171349A1 (zh) 一种分布式自增计数的实现方法、装置及系统
CN114416665B (zh) 一种数据一致性检测和修复的方法、装置及介质
JP2006012004A (ja) ホットスタンバイシステム
CN110321197A (zh) 一种基于kvm的虚拟网卡管理方法
CN113300953A (zh) 一种多路径故障转移组的管理方法、系统及相关装置
CN107704206B (zh) 在线迁移异构系统数据的方法、装置、设备和存储介质
CN114443332A (zh) 一种存储池的检测方法、装置、电子设备及存储介质
CN113330426B (zh) 一种备份数据的方法、装置和系统
CN107203451B (zh) 用于在存储系统中处理故障的方法及设备
US20120072776A1 (en) Fault isolation using code paths
US7853726B2 (en) FCP command-data matching for write operations
CN111404780B (zh) 一种远程直接存储器访问网络集群的功能测试方法和装置
WO2017054643A1 (zh) 一种数据抢救方法及文件服务器
CN112579359A (zh) 业务系统重建方法、装置、设备及存储介质
CN111984366A (zh) 一种容器化部署灾备机制的方法和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21949947

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18270219

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE