Failure recovery in shared storage operations

• US 9,959,176 B2
• Filed: 02/29/2016
• Issued: 05/01/2018
• Est. Priority Date: 02/22/2016
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Litke, Adam, Soffer, Nir, Aravot, Liron
• Primary Examiner(s): Butler, Sarai E
• Application Number:
  US15/055,861
• Publication Number:
  US 20170242755A1
• Time in Patent Office: 792 Days
• Field of Search: 714 19
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 2009/45583 Memory management, e.g. access or allocation
• CPC Class Codes: G06F 2201/805 Real-time
• CPC Class Codes: G06F 2201/815 Virtual
• CPC Class Codes: G06F 2201/82 Solving problems relating to consistency
• CPC Class Codes: G06F 2201/825 the problem or solution involving locking
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0622 in relation to access
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/0659 Command handling arrangements, e.g. command buffers, queues, command scheduling
• CPC Class Codes: G06F 3/0665 at area level, e.g. provisioning of virtual or logical volumes
• CPC Class Codes: G06F 3/0667 at data level, e.g. file, record or object virtualisation
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 3/0673 Single storage device
• CPC Class Codes: G06F 9/45545 Guest-host, i.e. hypervisor is an application program itself, e.g. VirtualBox
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

Systems and methods for failure recovery in shared storage operations. An example method comprises: acquiring a lock with respect to a storage domain comprising a specified disk image; creating a transaction marker associated with the disk image; creating a component of a new volume associated with the disk image; destroying the transaction marker; and releasing the lock with respect to the storage domain.

Claims

1. A method, comprising:

acquiring, by a processing device, a lock with respect to a storage domain comprising a specified disk image;

creating a transaction marker associated with the disk image, wherein the transaction marker is represented by a metadata file having a name comprising a pre-defined extension;

creating a component of a new volume associated with the disk image;

destroying the transaction marker by removing the extension from the name of the metadata file representing the transaction marker; and

releasing the lock with respect to the storage domain.

2. The method of claim 1, wherein the component of the new volume is provided by one of:

a data file or a lease file.

3. The method of claim 1, wherein the component of the new volume is provided by one of:

a metadata area residing on a block-based storage device or a lease area residing on a block-based storage device.

7. The method of claim 1, wherein the storage object referenced by the marker is provided by one of:

a data file or a lease file.

8. The method of claim 1, wherein the storage object referenced by the marker is provided by one of:

a metadata area residing on a block-based storage device or a lease area residing on a block-based storage device.

4. A method, comprising:

scanning, by a processing device running a first process, a specified storage area to compile a list of transaction markers;

acquiring a lock with respect to the specified storage area;

identifying, in the list, a first transaction marker that was modified by a second process before the lock has been acquired by the first process;

removing the first transaction marker from the list;

retrieving a second transaction marker from the list;

destroying a storage object referenced by the second transaction marker;

destroying the second transaction marker; and

releasing the lock with respect to the specified storage area.

5. The method of claim 4, wherein the transaction marker is provided by a metadata file having a pre-defined filename extension.

6. The method of claim 4, wherein the transaction marker is provided by a pre-defined tag associated with a logical volume residing on a block-based storage device, wherein the logical volume implements a data area of the new volume.

9. The method of claim 4, wherein destroying the transaction marker further comprises:

removing a pre-defined extension from a name of a volume metadata file.

10. The method of claim 4, wherein destroying the transaction marker further comprises:

removing a pre-defined tag from a logical volume residing on a block-based storage device, wherein the logical volume represents a volume data area.

11. A computer-readable non-transitory storage medium comprising executable instructions that, when executed by a processing device, cause the processing device to:

scan a specified storage area to compile a list of transaction markers;

acquire a lock with respect to the specified storage area;

identifying, in the list, a first transaction marker that was modified by another process before the lock has been acquired;

removing the first transaction marker from the list;

retrieve a second transaction marker from the list;

destroy a storage object referenced by the second transaction marker;

destroy the second transaction marker; and

release the lock with respect to the specified storage area.

12. The computer-readable non-transitory storage medium of claim 11, wherein the transaction marker is provided by a pre-defined tag associated with a logical volume residing on a block-based storage device, wherein the logical volume implements a data area of the new volume.

13. The computer-readable non-transitory storage medium of claim 11, wherein destroying the transaction marker further comprises:

removing a pre-defined extension from a name of a volume metadata file.

14. The computer-readable non-transitory storage medium of claim 11, wherein destroying the transaction marker further comprises:

removing a pre-defined tag from a logical volume residing on a block-based storage device, wherein the logical volume represents a volume data area.