Format of Possible ld Exception Messages
LD ld:<ldname> "LD is not mapped to a volume"
LD ld:<ldname> "LD is in write-through mode"
LD ld:<ldname> "LD has <X> preserved RAID sets and <Y> preserved chunklets"
LD ld:<ldname> "LD has reduced availability. Current: <cavail>, Configured:
<avail>"
LD ld:<ldname> "LD does not have a backup"
LD ld:<ldname> "LD does not have owner and backup"
LD ld:<ldname> "Logical Disk is owned by <owner>, but preferred owner is <powner>"
LD ld:<ldname> "Logical Disk is backed by <backup>, but preferred backup is
<pbackup>"
LD ld:<ldname> "A logging LD is smaller than 20G in size"
LD ld:<ldname> "Detailed State:<ldstate>" (degraded or failed)
LD -- "Number of logging LD's does not match number of nodes in the cluster"
LD -- "Preserved data storage space does not equal total node's Data memory"
ld Example 1
Component -------Summary Description-------- Qty
LD LDs not mapped to a volume 1
Component -Identifier-- --------Detailed Description---------
LD ld:vv.9.usr.3 LD is not mapped to a volume
ld Suggested Action 1
Examine the identified LDs using CLI commands such as showld, showld –d , showldmap,
showvvmap, and other such commands.
LDs are normally mapped to (used by) VVs but they can be disassociated with a VV if a VV is deleted
without the underlying LDs being deleted, or by an aborted tune operation. Normally, you would remove
the unmapped LD to return its chunklets to the free pool.
cli% showld vv.9.usr.3
Id Name RAID -Detailed_State- Own SizeMB UsedMB Use Lgct LgId WThru
MapV
57 vv.9.usr.3 1 normal 1/0 8192 0 C,V 0 --- N N
---------------------------------------------------------------------
1 8192 0
cli% showldmap vv.9.usr.3
Ld space not used by any vv
ld Example 2
Troubleshooting 77
To Next Page
Loading...
