lsmdisk
Use the lsmdisk command to display a concise list or a detailed view of managed disks (MDisks) visible to the clustered system (system). It can also list detailed information about a single MDisk.
Syntax
>>- lsmdisk -- -------------------------------------------------> >--+-------------------------------------------------------------+- --> '- -filtervalue -- attribute=value -- --+-------------------+-' '- -unit --+- b --+-' +- kb -+ +- mb -+ +- gb -+ +- tb -+ '- pb -' >--+-----------------+-- --+----------+- -+----------+- --------> '- -filtervalue? -' '- -nohdr -' '- -bytes -' >--+-----------------------+-- --+---------------+------------->< '- -delim -- delimiter -' +- 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. Use the unit parameter to interpret the value for size or capacity.
- Note: Some filters allow the use of a wildcard when entering the command. The following rules apply to the use of wildcards with the Storwize® V3700 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:
lsmdisk -filtervalue "name=md*"
- -unit b | kb | mb | gb | tb | pb
- (Optional) Specifies the data units for the -filtervalue parameter.Note: -unit must be used with -filtervalue.
- -filtervalue?
- (Optional) Includes all of the valid filter attributes in
the report. The following filter attributes are valid for the lsmdisk command:
- block_size
- capacity
- controller_id
- controller_name
- ctrl_LUN_#
- easy_tier_load
- id
- max_path_count
- mode
- mdisk_grp_id
- mdisk_grp_name
- name
- path_count
- quorum_index
- site_id
- site_name
- status
- tier
- UID
For more information about filtering attributes, see Attributes of the -filtervalue parameters.
- -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 system. Table 1 provides
the potential output for MDisks.
Attribute | Values |
---|---|
status |
|
mode | unmanaged, managed, image, array |
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 flash drive attached inside a node and 4 is any other device |
tier | The tier this MDisk has been assigned to by auto-detection (for internal
MDisks) or by the user:
Note: You can change this value using the chmdisk command.
|
easy_tier_load | This value controls Easy Tier® settings, and is either blank (for arrays) or one of the
following values (for MDisks):
|
raid_status |
|
raid_level | The RAID level of the array (RAID0, RAID1, RAID5, RAID6, RAID10). |
redundancy | The number of how many member disks that fail before the array fails. |
strip_size | The strip size of the array (in KB). |
spare_goal | The number of spares that the array members should be protected by. |
spare_protection_min | The minimum number of spares that an array member is protected by. |
balanced | Describes if the array is balanced to its spare
goals:
|
site_id | Indicates the site value for the MDisk. This numeric value is 1, 2, 3 or blank. |
site_name | Indicates the site name for the MDisk. This is an alphanumeric value or is blank. |
fabric_type | Indicates a Fibre Channel (FC), SAS, or another
type of MDisk.
|
distributed | Indicates whether the array is distributed. The values are yes or no. |
drive_class_id | Indicates the drive class that makes up this array. If -allowsuperior was used during array creation, the lowest used drive class ID is displayed. This value is blank for traditional arrays. |
drive_count | Indicates the total width of the array, including rebuild areas. The value is a number from 4 to 128. The minumum value for RAID-6 and RAID-10 arrays is 6. |
stripe_width | Indicates the width of a single unit of redundancy
within a distributed set of drives. The values are:
|
rebuild_areas_total | Indicates the total number of rebuild areas set at array creation time. These rebuild areas provide performance but no capacity. The value is 1 - 4 for distributed array RAID-5 and RAID-6, and the value is 2 - 4 for distributed array RAID-10 (the value is blank for traditional arrays). |
rebuild_areas_available | Indicates the number of remaining build areas within the set of arrays. The value is 1 - 4 for distributed array RAID-5 and RAID-6, and the value is 2 - 4 for distributed array RAID-10 (the value is blank for traditional arrays). |
rebuild_areas_goal | Indicates the rebuild areas threshold (minimum limit) at which point the array logs an error. The value is 1 - 4 for distributed array RAID-5 and RAID-6, and the value is 2 - 4 for distributed array RAID-10 (the value is blank for traditional arrays). |
dedupe | Indicates that dedupe is enabled. If dedupe is enabled, duplicate copies of repeating data are compressed or removed. |
ctrl_WWNN | Indicates the control worldwide node name (WWNN). |
preferred_WWPN | Indicates the preferred worldwide port name (WWPN). |
active_WWPN | Indicates the active WWPN. |
preferred_iscsi_port_id | Indicates the preferred I/O port identifier, which has the same value as the preferred_WWPN value in the Fibre Channel (FC) domain. The Internet Small Computer System Interface (iSCSI) port ID value is displayed, but the value is blank for non-iSCSI domains. This value must be a numeric value that can range from 0 - 1023. |
active_iscsi_port_id | Indicates the active I/O port identifier, which has the same value as the active_WWPN value in the FC domain. The Internet Small Computer System Interface (iSCSI) port ID value is displayed, but the value is blank for non-iSCSI domains. This value must be a numeric value that can range from 0 - 1023. |
Note: The automatic discovery performed by the system
does not write anything to an unmanaged MDisk. It is only when you
add an MDisk to a storage pool,
or use an MDisk to create an image mode volume,
that the system uses the storage.
To see which MDisks are available, issue the detectmdisk command to manually rescan the Fibre Channel or iSCSI network for any new MDisks. Issue the lsmdiskcandidate command to show the unmanaged MDisks. These MDisks have not been assigned to a storage pool.
Notes:
- A Storwize V3700 connection from a node or node canister port to a storage controller port for a single MDisk is a path. The Mdisk path_count value is the number of paths currently being used to submit input/output (I/O) to this MDisk.
- The MDisk max_path_count value is the highest value path_count has reached since the MDisk was last fully online.
- The preferred_WWPN is one of the World Wide Port Names (WWPNs) the storage controller has specified as a preferred WWPN. If the controller has nothing specified, this is a blank field.
- The active_WWPN indicates the WWPN of the storage controller port currently being used for I/O.
- If no storage controller ports are available for I/O, this is a blank field.
- If multiple controller ports are actively being used for I/O, this field's value is many.
The following
define the status fields:
- online
- The MDisk is online and available.
- degraded
- (Internal MDisks only) The array has members that are degraded, or the raid_status is degraded.
- 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 system.
- offline
- All paths to the MDisk are lost.
- excluded
- The MDisk is excluded from use by the system; the MDisk port error count exceeded the threshold.
A concise invocation example
lsmdisk -delim :
The concise resulting output:
id:name:status:mode:mdisk_grp_id:mdisk_grp_name:capacity:ctrl_LUN_#:controller_name:UID:tier:encrypt:site_id:site_name:distributed:dedupe
0:mdisk0:online:unmanaged:::100.0GB:0000000000000000:controller0:600a0b800076b42000002a1755e4f5e200000000000000000000000000000000:enterprise:no:::no:no
1:mdisk1:degraded_paths:unmanaged:::1.0GB:0000000000000000:controller1:6005076802b580c10c0000000000000000000000000000000000000000000000:enterprise:no:::no:no
2:mdisk2:degraded_paths:managed:0:mdiskgrp2:1.0GB:0000000000000001:controller1:6005076802b580c10c0000000000000200000000000000000000000000000000:enterprise:no:::no:no
3:mdisk3:degraded_paths:unmanaged:::1.0GB:0000000000000002:controller1:6005076802b580c10c0000000000000300000000000000000000000000000000:enterprise:no:::no:no
4:mdisk4:degraded_paths:unmanaged:::1.0GB:0000000000000003:controller1:6005076802b580c10c0000000000000400000000000000000000000000000000:enterprise:no:::no:no
5:mdisk5:degraded_paths:unmanaged:::1.0GB:0000000000000004:controller1:6005076802b580c10c0000000000000100000000000000000000000000000000:enterprise:no:::no:no
A detailed invocation example
lsmdisk mdisk1
The detailed resulting output:
id:1
name:mdisk1
status:online
mode:array
mdisk_grp_id:0
mdisk_grp_name:mdgp0
capacity:136.0GB
quorum_index:
block_size:512
controller_name:controller1
ctrl_type:4
ctrl_WWNN:200400A0B80F0702
controller_id:1
path_count:2
max_path_count:2
ctrl_LUN_#:0000000000000002
UID:600a0b80000f07020000005c45ff8a7c00000000000000000000000000000000
preferred_WWPN:200400A0B80F0703
active_WWPN:200400A0B80F0703
fast_write_state:empty
raid_status:
raid_level:
redundancy:
strip_size:
spare_goal:
spare_protection_min:
balanced:
tier:tier0_flash
slow_write_priority:latency
fabric_type:fc
easy_tier_load:low
distributed:no
drive_class_id
drive_count:8
stripe_width:4
total_rebuild_areas
available_rebuild_areas
rebuild_areas_goal
preferred_iscsi_port_id
active_iscsi_port_id
dedupe:yes