lsarraymember

Use the lsarraymember command to list the member drives of one or more array MDisks.

Syntax

lsarraymember [ -nohdr ] [ -filtervalue attribute=value ] [ -filtervalue? ] [ -delimdelimiter ] [ { mdisk_id | mdisk_name } ]

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.

-filtervalueattribute=value

(Optional) Specifies a list of one or more filter attributes matching the specified values; see -filtervalue? for the supported attributes.

Note: Some filters allow the use of a wildcard when entering the command. The following rules apply to the use of wildcards when using the 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 (""):
lsarraymember -filtervalue "mdisk_name=md*"

-filtervalue?

(Optional) Includes all of the valid filter attributes in the report. The following filter attributes are valid for the lsarraymember command:

mdisk_id

mdisk_name

member_id

drive_id

new_drive_id

spare_protection

balanced

Any parameters specified with the -filtervalue? parameter are ignored.
For more information about filtering attributes, see Attributes of the -filtervalue parameters.

-delimdelimiter

(Optional) By default, in a concise view all columns of data are space-separated, with the width of each column set to the maximum possible width of each item of data. In a detailed view, each item of data is an individual row, and if displaying headers, 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. Enter -delim : on the command line, and 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 specified delimiter separates the data from its header.

mdisk_id

(Optional) The identity of the array MDisk.

mdisk_name

(Optional) The MDisk name that you provided.

Description
This command lists the member drives of one or more array MDisks. It describes positions within an array unoccupied by a drive. The positions determine how mirroring the RAIDs takes place. For example, determining if x is mirrored to y for RAID-10, where parity starts from RAID-5.

Table 1 shows the potential output for this command.
Table 1. lsarraymember output

Attribute Value

member_id Specifies the identity of the array member. It represents drive order in RAID array

drive_id Specifies the identity of the drive for member ID, or the source drive if an exchange is in progress. It is blank if there is no drive configured.

new_drive_id Specifies the ID of the drive exchanged with this member ID. It is blank if there is no ID.

spare_protection Specifies the number of non-degrading spares for the member. This includes spare drives with different attributes from the array member goals that perform equally or better than the array member goals. For distributed array members this field is blank.

balanced
For nondistributed arrays, this describes if the array is balanced to its spare goals:

exact indicates that all populated members have the same (matching) capability and location.

yes indicates that all populated members have at least the same capability and chain, but a different enclosure or slot.

no indicates that it is unbalanced.

For distributed arrays, this indicates whether a superior drive class is being used for the array:

exact indicates that the same drive class is in use.

yes indicates that the drive exceeds the array drive class.

For distributed arrays, the array must also be balanced to its rebuild area goals.

slow_write_count Indicates the number of times this member has become unsynchronized because of high response time on write I/O operations.

slow_write_time_last Creates a timestamp of when the component last became unsynchronized. The time format is YYMMDDhhmmss in clustered system time. No time is indicated if the value is slow_write_count is 0.

A concise invocation example
lsarraymember -delim :

The resulting output:

lsarraymember -delim : mdisk_id:mdisk_name:member_id:drive_id:new_drive_id:spare_protection :balanced:slow_write_count:slow_write_time_last 2:mdisk1:0:55::1:exact:4:130103202158 2:mdisk1:1:56::1:exact:1:130103203930 2:mdisk2:0:0::2:exact:0: 2:mdisk2:1:2:5:3:exact:2:130103204044 2:mdisk2:2:::::: 2:mdisk2:3:8::0:no::

A concise invocation example (qualified with MDisk)
lsarraymember -delim : mdisk_2

The resulting output:

tmdisk_id:mdisk_name:member_id:drive_id:new_drive_id:spare_protection :balanced:slow_write_count:slow_write_time_last 2:mdisk2:0:0::2:exact:4:130103202158 2:mdisk2:1:2:5:3:exact:1:130103203930 2:mdisk2:2:::::0: 2:mdisk2:3:8::0:no:2:130103204044

Note: From this output, you can see that:

The array has four members (possibly a 4-member RAID-10 array). You cannot use RAID-10 with distributed arrays.

The second array member is undergoing exchange for drive5.

The third array member is not configured. It might be offline or failed, without a hot spare available.

The fourth array member has no spare protection and is not balanced.

An invocation example (two arrays)
lsarraymember -delim :

The resulting output:

mdisk_id:mdisk_name:member_id:drive_id:new_drive_id:spare_protection :balanced:slow_write_count:slow_write_time_last 2:mdisk1:0:55:::1:exact:4:130103202158 2:mdisk1:1:56:::1:exact:1:130103203930 2:mdisk2:0:0:::2:exact:0: 2:mdisk2:1:2:5::3:exact:2:130103204044 2:mdisk2:2::::::: 2:mdisk2:3:8:::0:no::

An invocation example (an array with a change in membership from (55,56) to (55,57,58))
lsarraymember -delim : mdisk_3

The resulting output:

mdisk_id:mdisk_name:member_id:drive_id:new_drive_id:spare_protection :balanced:slow_write_count:slow_write_time_last 3:mdisk3:0:55::55:1:exact:4:130103202158 3:mdisk3:1:56::57:1:exact:1:130103203930 3:mdisk3:2:::58:1:exact:0:

An invocation example (an array with a change in membership from (55,57,58) to (55,56))
lsarraymember -delim : mdisk_3

The resulting output:

mdisk_id:mdisk_name:member_id:drive_id:new_drive_id:spare_protection :balanced:slow_write_count:slow_write_time_last 3:mdisk3:0:55::55:1:exact:4:130103202158 3:mdisk3:1:57::56:1:exact:1:130103203930 3:mdisk3:2:58:::1:exact:0:

Attribute	Value
member_id	Specifies the identity of the array member. It represents drive order in RAID array
drive_id	Specifies the identity of the drive for member ID, or the source drive if an exchange is in progress. It is blank if there is no drive configured.
new_drive_id	Specifies the ID of the drive exchanged with this member ID. It is blank if there is no ID.
spare_protection	Specifies the number of non-degrading spares for the member. This includes spare drives with different attributes from the array member goals that perform equally or better than the array member goals. For distributed array members this field is blank.
balanced	For nondistributed arrays, this describes if the array is balanced to its spare goals: `exact` indicates that all populated members have the same (matching) capability and location. `yes` indicates that all populated members have at least the same capability and chain, but a different enclosure or slot. `no` indicates that it is unbalanced. For distributed arrays, this indicates whether a superior drive class is being used for the array: `exact` indicates that the same drive class is in use. `yes` indicates that the drive exceeds the array drive class. For distributed arrays, the array must also be balanced to its rebuild area goals.
slow_write_count	Indicates the number of times this member has become unsynchronized because of high response time on write I/O operations.
slow_write_time_last	Creates a timestamp of when the component last became unsynchronized. The time format is `YYMMDDhhmmss` in clustered system time. No time is indicated if the value is `slow_write_count` is `0`.