The lsmdisk command returns a concise list or a detailed view of managed disks (MDisks) visible to the cluster. It can also list detailed information about a single MDisk.
Syntax
>>- svcinfo -- -- lsmdisk -- -----------------------------------> >--+----------------------------------------------------------+--> '- -filtervalue -- attribute=value --+-------------------+-' '- -unit --+- b --+-' +- kb -+ +- mb -+ +- gb -+ +- pb -+ '- tb -' >-- --+----------+-- --+----------+-- --------------------------> '- -nohdr -' '- -bytes -' >--+-----------------------+-- -- --+-----------------+---------> '- -delim -- delimiter -' '- -filtervalue? -' >--+---------------+------------------------------------------->< +- object_id ---+ '- object_name -'
Parameters
- -filtervalue attribute=value
- (Optional) Specifies a list of one or more filter attributes matching the specified values; see -filtervalue? for the supported attributes. Only objects with a value that matches the filter attribute value are returned. If capacity is specified, the units must also be included.
- Note: Some filters allow the use of a wildcard when entering the command. The following rules apply to the use of wildcards with the SAN Volume Controller CLI:
- The wildcard character is an asterisk (*).
- The command can contain a maximum of one wildcard, which must be the first or last character in the string.
- When using a wildcard character, you must enclose the filter
entry within double quotation marks (""), as
follows:
svcinfo lsmdisk -filtervalue "name=md*"
- -filtervalue?
- (Optional) Includes all of the valid filter attributes in
the report. The following filter attributes are valid for the svcinfo
lsmdisk command:
- id
- name
- status
- mode
- mdisk_grp_id
- mdisk_grp_name
- capacity
- quorum_index
- block_size
- controller_name
- ctrl_type
- ctrl_WWNN
- controller_id
- path_count
- max_path_count
- ctrl_LUN_#
- UID
- preferred_WWPN
- active_WWPN
- node_id
- node_name
- location
- -nohdr
- (Optional) By default, headings are displayed for each column
of data in a concise style view, and for each item of data in a detailed
style view. The -nohdr parameter suppresses the
display of these headings.Note: If there is no data to be displayed, headings are not displayed.
- -bytes
- (Optional) Specifies that you want the report to display all capacities as bytes. Capacity values displayed in units other than bytes might be rounded. When filtering on capacity, use a unit of bytes, -unit b, for exact filtering.
- -delim delimiter
- (Optional) By default in a concise view, all columns of data are space separated. The width of each column is set to the maximum possible width of each item of data. In a detailed view, each item of data has its own row, and if the headers are displayed the data is separated from the header by a space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a one-byte character. If you enter -delim : on the command line, the colon character (:) separates all items of data in a concise view; for example, the spacing of columns does not occur. In a detailed view, the data is separated from its header by the specified delimiter.
- object_id | object_name
- (Optional) Specifies the name or ID of an object. When you use this parameter, the detailed view of the specific object is returned and any value that is specified by the -filtervalue parameter is ignored. If you do not specify the object_id | object_name parameter, the concise view displays all objects matching the filtering requirements that are specified by the -filtervalue parameter.
Description
This
command returns a concise list or a detailed view of MDisks visible
to the cluster. Table 1 provides
the potential output for MDisks.
| Attribute | Values |
|---|---|
| status | online, offline, excluded, degraded_paths, degraded_ports |
| mode | unmanaged, managed, image |
| quorum_index | 0, 1, 2, or blank if the MDisk is not being used as a quorum disk |
| block_size | 512, 524 bytes in each block of storage |
| ctrl_type | 4, 6, where 6 is a solid-state drive (SSD) attached inside a node and 4 is any other device |
Note: The automatic
discovery performed by the cluster does not write anything to an unmanaged
MDisk. It is only when you add an MDisk to an MDisk group, or use
an MDisk to create an image mode virtual disk, that the system uses
the storage.
To see which MDisks are available, issue the svctask detectmdisk command to manually rescan the fibre-channel network for any new MDisks. Issue the svcinfo lsmdiskcandidate command to show the unmanaged MDisks. These MDisks have not been assigned to an MDisk group.
Notes:
- The MDisk path_count value is the number of nodes through which the MDisk is currently accessible.
- The MDisk max_path_count value is the highest value that the path-count has reached since the MDisk was initially discovered or since the MDisk was last accessible through all nodes in the cluster.
- If an SSD is
attached inside a node:
- The node_id value is the ID of the node that the MDisk is in.
- The node_name value is the name of the node that the MDisk is in.
- The location value is the slot number printed on the drive bay.
The following define the
status fields:
- Online
- The MDisk is online and available.
- Degraded ports
- There are one or more MDisk port errors.
- Degraded paths
- One or more paths to the MDisk have been lost; the MDisk is not online to every node in the cluster.
- Offline
- All paths to the MDisk are lost.
- Excluded
- The MDisk is excluded from use by the cluster; the MDisk port error count exceeded the threshold.
A concise invocation example
svcinfo lsmdisk -delim :
The concise resulting output
id:name:status:mode:mdisk_grp_id:mdisk_grp_name:capacity:
ctrl_LUN_#:controller_name:UID
0:mdisk0:online:managed:0:mdiskgrp0:68.4GB:0000000000000000:controller0:
20000004cf2422aa000000000000000000000000000000000000000000000000
1:mdisk1:online:managed:0:mdiskgrp0:68.4GB:0000000000000000:controller1:
20000004cf1fd19d000000000000000000000000000000000000000000000000
2:mdisk2:online:managed:0:mdiskgrp0:68.4GB:0000000000000000:controller2:
20000004cf242531000000000000000000000000000000000000000000000000
3:mdisk3:online:managed:0:mdiskgrp0:68.4GB:0000000000000000:controller3:
20000004cf1fd7a0000000000000000000000000000000000000000000000000
4:mdisk4:online:unmanaged:::68.4GB:0000000000000000:controller4:
20000004cf241308000000000000000000000000000000000000000000000000
5:mdisk5:online:unmanaged:::68.4GB:0000000000000000:controller5:
20000004cf2412ca000000000000000000000000000000000000000000000000
A detailed invocation example
svcinfo lsmdisk -delim : 2
The detailed resulting output
id:2
name:mdisk2
status:online
mode:unmanaged
mdisk_grp_id:
mdisk_grp_name:
capacity:68.4GB
quorum_index:
block_size:512
controller_name:controller2
ctrl_type:4
ctrl_WWNN:20000004CF242531
controller_id:2
path_count:1
max_path_count:1
ctrl_LUN_#:0000000000000000
UID:20000004cf242531000000000000000000000000000000000000000000000000
preferred_WWPN:22000004CF242531
active_WWPN:22000004CF242531
node_id
node_name
location