Endpoint

/v1/files/{ref}/locks/nlm/byte-range/

GET

Return a list of all NLM byte range locks currently granted on the specified file.

Parameters

Name Description Required
ref The file ID or the absolute path to the file system object. File IDs can be found in the id field of responses of APIs that return file attributes. You must URL-encode the paths. The APIs & Tools page in the Qumulo Core Web UI URL-encodes the paths. Yes
snapshot The snapshot ID that specifies the version of the filesystem to use. If not specified, use the head version. No
after Return entries after the given key (keys are returned in the paging object) No
limit Return no more than this many entries; the system may choose a smaller limit. No

Response

Codes

Code Description
200 Return value on success

Schema

{
  "description": "api_byte_range_grants",
  "type": "object",
  "properties": {
    "grants": {
      "type": "array",
      "items": {
        "description": "grants",
        "type": "object",
        "properties": {
          "file_id": {
            "description": "file_id",
            "type": "string"
          },
          "stream_id": {
            "description": "stream_id",
            "type": "string"
          },
          "snapshot_id": {
            "description": "The locked file's snapshot ID. Empty if the file is at the head version (not from a snapshot).",
            "type": "string"
          },
          "mode": {
            "type": "array",
            "items": {
              "type": "string",
              "enum": [
                "API_BYTE_RANGE_EXCLUSIVE",
                "API_BYTE_RANGE_SHARED",
                "API_BYTE_RANGE_READ_OP",
                "API_BYTE_RANGE_WRITE_OP"
              ],
              "description": "mode:\n * `API_BYTE_RANGE_EXCLUSIVE` - API_BYTE_RANGE_EXCLUSIVE,\n * `API_BYTE_RANGE_READ_OP` - API_BYTE_RANGE_READ_OP,\n * `API_BYTE_RANGE_SHARED` - API_BYTE_RANGE_SHARED,\n * `API_BYTE_RANGE_WRITE_OP` - API_BYTE_RANGE_WRITE_OP"
            }
          },
          "offset": {
            "description": "offset",
            "type": "string"
          },
          "size": {
            "description": "size",
            "type": "string"
          },
          "owner_id": {
            "description": "The unique identifier for the process that owns the file lock.",
            "type": "string"
          },
          "owner_name": {
            "description": "The name of the machine that owns the lock.",
            "type": "string"
          },
          "owner_address": {
            "description": "The IP address to use for acquiring the file lock.",
            "type": "string"
          },
          "node_address": {
            "description": "The IP address of the node that receives the request.",
            "type": "string"
          }
        }
      }
    }
  }
}

DELETE

Release an arbitrary lock range. This is dangerous, and should only be used after confirming that the owning process has leaked the lock, and only if there is a very good reason why the situation should not be resolved by terminating that process.

Parameters

Name Description Required
ref The file ID or the absolute path to the file system object. File IDs can be found in the id field of responses of APIs that return file attributes. You must URL-encode the paths. The APIs & Tools page in the Qumulo Core Web UI URL-encodes the paths. Yes
offset Offset of the range to release Yes
size Size of range to release. Zero releases to the maximum file size. Yes
owner_id Opaque, unique identifier for the process that owns the lock. This is the owner_id attribute on entries returned by GET. Yes
snapshot The snapshot ID that specifies the version of the filesystem to use. If not specified, use the head version. No

Response

Codes

Code Description
200 Return value on success