# US 2013/0086318 A1 · Safe management of data storage using a volume manager

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0086318 A1
- Document ID: US20130086318A1
- Status: Published application
- Kind: A1
- Application number: 13/251,752
- Filed: 2011-10-03
- Published: 2013-04-04
- Earliest claimed: 2011-10-03
- Assignees: International Business Machines Corporation
- Inventors: Adekunle BELLO; Radhika CHIRRA; Anil Kumar Kaniveedu DAMODARAN; Rakesh THOUTEM
- Web page: https://patentgrep.com/patent/US20130086318A1

## CPC

- G06F 11/0727: {in a storage system, e.g. in a DASD or network based storage system (drivers for digital recording or reproducing units G06F3/06; circuits for error detection or correction within digital recording or reproducing units G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method, system, and computer program product for safe management of data storage using a VM are provided in the illustrative embodiments. An I/O request is received from the VM. A determination is made whether the I/O request requests a data manipulation on the data storage in an address range that overlaps with an address range of a VM signature stored on the data storage. In response to determining that the address range of the data manipulation overlaps with the address range of the VM signature, a determination is made whether an identifier of the VM matches an identifier of a second VM associated with the signature. In response to determining that the identifier of the VM does not match the identifier of the second VM, the I/O request is failed, thereby preventing an unsafe overwriting of the signature on the data storage.

## Claims

### Claim 1

A method for safe management of a data storage using a volume manager (VM), the method comprising:
a computer receiving an I/O request from the VM;
the computer determining whether the I/O request requests a data manipulation on the data storage in an address range that overlaps with an address range of a VM signature stored on the data storage;
the computer, responsive to determining that the address range of the data manipulation overlaps with the address range of the VM signature, determining whether an identifier of the VM matches an identifier of a second VM associated with the VM signature; and
the computer, responsive to determining that the identifier of the VM does not match the identifier of the second VM, failing the I/O request, thereby preventing an unsafe overwriting of the VM signature on the data storage.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
the computer receiving a second I/O request;
the computer determining that an address range of a data manipulation requested by the second I/O request overlaps with the address range of the VM signature;
the computer determining whether the second I/O request includes an indicator to indicate that the second I/O request is intended to overwrite the VM signature;
the computer, responsive to determining that the I/O request does not include the indicator, failing the second I/O request.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
the computer receiving a second I/O request;
the computer determining that an address range of a data manipulation requested by the second I/O request does not overlap with the address range of the VM signature; and
the computer processing the second I/O request through normal I/O process.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
the computer receiving a registration from the VM;
the computer determining, using the registration, a signature metadata associated with the VM;
the computer recording the signature metadata on the data storage.

### Claim 5 (depends on 4)

The method of claim 4, wherein the recording comprises:
the computer recording the signature metadata in a monitor table on a storage subsystem associated with the data storage; and
the computer updating a copy of a portion of the monitor table existing in a memory associated with the computer.

### Claim 6 (depends on 1)

The method of claim 1, wherein the method is performed by a VM identification service executing in a kernel space of the computer.

### Claim 7 (depends on 1)

The method of claim 1, wherein the data storage is a volume identified by a logical unit number (LUN) in a signature metadata, and wherein the VM manages the LUN.

### Claim 8 (depends on 7)

The method of claim 7, wherein the VM signature is a signature of a different VM than the VM that also manages the LUN.

### Claim 9 (depends on 7)

The method of claim 7, wherein the signature metadata further includes an identifier for the VM and an identifier for the LUN.

### Claim 10 (depends on 7)

The method of claim 7, wherein the signature metadata further includes a list of nodes from where the VM can manage the LUN.

### Claim 11 (depends on 1)

The method of claim 1, further comprising the computer deducing the address range of the signature from a signature metadata, the signature metadata including a location and a size of the VM signature on the data storage.

### Claim 12 (depends on 1)

A computer program product comprising one or more computer-readable tangible storage devices and computer-readable program instructions which are stored on the one or more storage devices and when executed by one or more processors, perform the method of claim 1.

### Claim 13 (depends on 1)

A computer system comprising one or more processors, one or more computer-readable memories, one or more computer-readable tangible storage devices and program instructions which are stored on the one or more storage devices for execution by the one or more processors via the one or more memories and when executed by the one or more processors, perform the method of claim 1.

### Claim 14

A computer program product for safe management of a data storage using a volume manager (VM), the computer program product comprising:
one or more computer-readable tangible storage devices;
program instructions, stored on at least one of the one or more storage devices, to receive an I/O request from the VM;
program instructions, stored on at least one of the one or more storage devices, to determine whether the I/O request requests a data manipulation on the data storage in an address range that overlaps with an address range of a VM signature stored on the data storage;
program instructions, stored on at least one of the one or more storage devices, to, responsive to determining that the address range of the data manipulation overlaps with the address range of the VM signature, determine whether an identifier of the VM matches an identifier of a second VM associated with the VM signature; and
program instructions, stored on at least one of the one or more storage devices, to, responsive to determining that the identifier of the VM does not match the identifier of the second VM, fail the I/O request, thereby preventing an unsafe overwriting of the VM signature on the data storage.

### Claim 15 (depends on 14)

The computer program product of claim 14, further comprising:
program instructions, stored on at least one of the one or more storage devices, to determine whether the I/O request includes an indicator to indicate that the I/O request is intended to overwrite the VM signature; and
program instructions, stored on at least one of the one or more storage devices, to, responsive to determining that the I/O request does not include the indicator, fail the I/O request, thereby preventing the unsafe overwriting of the VM signature on the data storage.

### Claim 16 (depends on 14)

The computer program product of claim 14, further comprising:
program instructions, stored on at least one of the one or more storage devices, to process the I/O request through normal I/O processing responsive to determining that the address range of the data manipulation does not overlap with the address range of the VM signature.

### Claim 17 (depends on 14)

The computer program product of claim 14, further comprising:
program instructions, stored on at least one of the one or more storage devices, to receive a registration from the VM;
program instructions, stored on at least one of the one or more storage devices, to determine, using the registration, a signature metadata associated with the VM;
program instructions, stored on at least one of the one or more storage devices, to record the signature metadata on the data storage.

### Claim 18 (depends on 14)

The computer program product of claim 14, wherein the program instructions are stored in at least one of the one or more computer-readable tangible storage devices in a data processing system, and wherein the program instructions are transferred over a network from a remote data processing system.

### Claim 19 (depends on 14)

The computer program product of claim 14, wherein the program instructions are stored in at least one of the one or more computer-readable tangible storage devices in a server data processing system, and wherein the program instructions are downloaded over a network to a remote data processing system for use in a computer-readable tangible storage device associated with the remote data processing system.

### Claim 20

A computer system for safe management of a data storage using a volume manager (VM), the computer system comprising:
one or more processors, one or more computer-readable memories and one or more computer-readable tangible storage devices;
program instructions, stored on at least one of the one or more storage devices for execution by at least one of the one or more processors via at least one of the one or more memories, to receive an I/O request from the VM;
program instructions, stored on at least one of the one or more storage devices for execution by at least one of the one or more processors via at least one of the one or more memories, to determine whether the I/O request requests a data manipulation on the data storage in an address range that overlaps with an address range of a VM signature stored on the data storage;
program instructions, stored on at least one of the one or more storage devices for execution by at least one of the one or more processors via at least one of the one or more memories, to, responsive to determining that the address range of the data manipulation overlaps with the address range of the VM signature, determine whether an identifier of the VM matches an identifier of a second VM associated with the VM signature; and
program instructions, stored on at least one of the one or more storage devices for execution by at least one of the one or more processors via at least one of the one or more memories, to, responsive to determining that the identifier of the VM does not match the identifier of the second VM, fail the I/O request, thereby preventing an unsafe overwriting of the VM signature on the data storage.
