Understanding a Volume Location in the Lightbits Cluster

You can use the lbcli get volumes command for a specific volume to see which of the cluster nodes holds the data of a specific volume.

Sample Command

Bash
    
 
$ lbcli get volume --uuid=48dbbe54-1548-4444-866e-6438d4877e5f
Copy

In this command, the JWT is not stored in the lbcli configuration file:

Bash
    
 
$ lbcli -J $JWT get volume --project-name=proj-1 --uuid=48dbbe54-1548-4444-866e-6438d4877e5f
Copy

Sample Output

Bash
    
 
name: vol_3rebuildProgress: NoneUUID: 48dbbe54-1548-4444-866e-6438d4877e5fAcl:  Values:  - hostnqn1nsid: 4size: "107374182400"nodeList:- 9a625dbf-de1b-4211-b9d3-0bdf70faa5f5- 9f1a3a85-5be5-4f98-a44e-4271fbdbe7ccprotectionState: FullyProtectedreplicaCount: 2state: Created
Copy

You can also run the nvme list-subsys command on the application server.

Sample Command

Bash
    
 
# nvme list-subsys nvme0n1
Copy

Sample Output

Bash
    
 
nvme-subsys0 -NQN=nqn.2014-08.org.nvmexpress:NVMf:uuid:b550533c-8bb0-46df-9019-cd4c25c6e6e7\ +- nvme0 tcp traddr=10.18.38.4 trsvcid=4420 live  +- nvme1 tcp traddr=10.18.38.5 trsvcid=4420 live  +- nvme2 tcp traddr=10.18.38.7 trsvcid=4420 live  +- nvme3 tcp traddr=10.18.38.8 trsvcid=4420 live optimized +- nvme4 tcp traddr=10.18.38.29 trsvcid=4420 live inaccessible
Copy

This command’s output includes the cluster’s primary node (optimized) IP address for the volume, the secondary node (inaccessible) IP address, and the other nodes that do not hold data for that volume (block device nvme0n1).

Last updated on

Was this page helpful?