You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the initiators, e.g. in linux, it is not easy to correlate between the block device and the nsid that we have in the gw. One way to do it is for example:
run cat /sys/block/nvme1n2/nguid ===> and get the nguid
Then list the namespaces in the gw, and look for a ns with this uuid.
An easier way would be to provide a cli that will find information about a namespace by uuid. E.g. "namespace find -uuid X" - it should look in all subsystems, and return the namespace properties (subsystem, ana grp, ...)
The text was updated successfully, but these errors were encountered:
In the initiators, e.g. in linux, it is not easy to correlate between the block device and the nsid that we have in the gw. One way to do it is for example:
An easier way would be to provide a cli that will find information about a namespace by uuid. E.g. "namespace find -uuid X" - it should look in all subsystems, and return the namespace properties (subsystem, ana grp, ...)
The text was updated successfully, but these errors were encountered: