This section explains how to use the
qq fs_release_nlm_lock command.Description
Release an arbitrary NLM byte-range 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.
Usage
qq fs_release_nlm_lock [-h] (--path PATH | --id ID) --offset OFFSET --size SIZE --owner-id OWNER_ID [--force] [--snapshot SNAPSHOT]
Flags
| Flag Name | Required | Description |
|---|---|---|
--path
|
No | File path |
--id
|
No | File ID |
--offset
|
Yes | NLM byte-range lock offset |
--size
|
Yes | NLM byte-range lock size |
--owner-id
|
Yes | Owner id |
--force
|
No | This command can cause corruption, add this flag to release lock |
--snapshot
|
No | Snapshot ID of the specified file |