Component -------Summary Description-------- Qty
LD LDs in write through mode 3
Component -Identifier-- --------Detailed Description---------
LD ld:Ten.usr.12 LD is in write-through mode
ld Suggested Action 2
Examine the identified LDs using CLI commands such as showld, showld –d , showldch, and
showpd for any failed or missing Drives. Write-through mode (WThru) indicates that host I/O operations
must be written through to the Drive before the host I/O command is acknowledged. This is usually due to
a node-down condition, when Controller Node batteries are not working, or where Drive redundancy is not
optimal.
cli% showld Ten*
Id Name RAID -Detailed_State- Own SizeMB UsedMB Use Lgct LgId
WThru
MapV
91 Ten.usr.3 0 normal 1/0/3/2 13824 0 V 0 ---
N N
92 Ten.usr.12 0 normal 2/3/0/1 28672 0 V 0 ---
Y N
cli% showldch Ten.usr.12
cli% showpd 104
ld Example 3
Component ---------Summary Description--------- Qty
LD LDs with reduced availability 1
Component --Identifier-- ------------Detailed Description---------------
LD ld:R1.usr.0 LD has reduced availability. Current: ch, Configured:
cage
ld Suggested Action 3
LDs are created with certain high-availability characteristics, such as -ha -cage. If chunklets in an LD
get moved to locations where the Current Availability (CAvail) is not at least as good as the desired level
of availability (Avail), this condition is reported. Chunklets might have been manually moved with
movech or by specifying it during a tune operation or during failure conditions such as Controller Node,
path, or cage failures. The HA levels from highest to lowest are port, cage, mag, and ch (disk).
Examine the identified LDs using CLI commands such as showld, showld –d , showldch, and
showpd for any failed or missing Drives. In the example below, the LD should have cage-level availability,
but it currently has chunklet (Drive) level availability (the chunklets are on the same Drive).
78 Troubleshooting
To Next Page
Loading...
