Plex in detached/active state

Question

We have a plex in a detached/active state after losing fibre connectivity on the lun. Other luns were recovered by running vxreattach after the fibre issues had been sorted. All paths to the disk look fine.
Will appreciate any suggestions to get this one sorted.
&nbsp;
Output:
vxdisk list
c2t2d3s2&nbsp;&nbsp;&nbsp;&nbsp; auto:cdsdisk&nbsp;&nbsp;&nbsp; APPDR_QZdg03&nbsp; APPDR_QZdg&nbsp;&nbsp; online&nbsp;
c2t3d3s2&nbsp;&nbsp;&nbsp;&nbsp; auto:cdsdisk&nbsp;&nbsp;&nbsp; APPDR_QZdg04&nbsp; APPDR_QZdg&nbsp;&nbsp; online&nbsp;
vxprint -htg
dm APPDR_QZdg03 c2t2d3s2&nbsp;&nbsp;&nbsp;&nbsp; auto&nbsp;&nbsp;&nbsp;&nbsp; 2048&nbsp;&nbsp;&nbsp;&nbsp; 52406016 -
	dm APPDR_QZdg04 c2t3d3s2&nbsp;&nbsp;&nbsp;&nbsp; auto&nbsp;&nbsp;&nbsp;&nbsp; 2048&nbsp;&nbsp;&nbsp;&nbsp; 52406016 -
v&nbsp; APPDR_QZvol&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENABLED&nbsp; ACTIVE&nbsp;&nbsp; 52219088 SELECT&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fsgen
	pl APPDR_QZVOLnew-01 APPDR_QZvol ENABLED ACTIVE 52219088 CONCAT&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RW
	sd APPDR_QZdg03-01 APPDR_QZVOLnew-01 APPDR_QZdg03 0 52219088 0&nbsp;&nbsp;&nbsp; c2t2d3&nbsp;&nbsp; ENA
	pl APPDR_QZVOLnew-02 APPDR_QZvol DETACHED ACTIVE 52219088 CONCAT&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RW
	sd APPDR_QZdg04-01 APPDR_QZVOLnew-02 APPDR_QZdg04 0 52219088 0&nbsp;&nbsp;&nbsp; c2t3d3&nbsp;&nbsp; ENA
	pl APPDR_QZVOLnew-03 APPDR_QZvol ENABLED ACTIVE LOGONLY CONCAT&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RW
	sd APPDR_QZdg03-02 APPDR_QZVOLnew-03 APPDR_QZdg03 52219088 528 LOG c2t2d3&nbsp; ENA
	pl APPDR_QZVOLnew-04 APPDR_QZvol DETACHED(SPARSE) ACTIVE LOGONLY CONCAT -&nbsp; RW
	sd APPDR_QZdg04-02 APPDR_QZVOLnew-04 APPDR_QZdg04 52219088 528 LOG c2t3d3&nbsp; DET&nbsp;
&nbsp;
vxdg list
Group:&nbsp;&nbsp;&nbsp;&nbsp; APPDR_QZdg
	dgid:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1142436630.42.QuartzAPPDR
	import-id: 1024.14
	flags:&nbsp;&nbsp;&nbsp;&nbsp; cds
	version:&nbsp;&nbsp; 120
	alignment: 8192 (bytes)
	ssb:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; on
	detach-policy: global
	dg-fail-policy: dgdisable
	copies:&nbsp;&nbsp;&nbsp; nconfig=default nlog=default
	config:&nbsp;&nbsp;&nbsp; seqno=0.1530 permlen=1280 free=1271 templen=6 loglen=192
	config disk c2t2d3s2 copy 1 len=1280 state=clean online
	config disk c2t3d3s2 copy 1 len=1280 state=iofail online
	log disk c2t2d3s2 copy 1 len=192
	log disk c2t3d3s2 copy 1 len=192 invalid
&nbsp;
OS: Solaris 10
VxVM: 5.1 MP1
	&nbsp;

har-d · Accepted Answer

Hope this is a simple volume with mirror and log plexes?
If yes, could you please try disassociating and reattaching it :
&nbsp;
vxplex -g &lt;diskgroup&gt; -v &lt;volume_name&gt; dis &lt;mirrored-plex&gt;
vxplex -g &lt;diskgroup&gt; att &lt;volume_name&gt; &lt;mirrored-plex&gt;
&nbsp;
Also, please monitor the vxtask and messages for any errors.

har-d · Answer

There is a possibility the LUN is not yet available on the OS.
Could you provide additional info to confirm the same. Like :
# vxdisk list
# vxdisk -e list
# echo|format
# prtvtoc &lt;on_the_affected_disk&gt;

daniev · Answer

The lun is available :
root@QuartzAPPDR # vxdisk list c2t3d3s2
	Device:&nbsp;&nbsp;&nbsp; c2t3d3s2
	devicetag: c2t3d3
	type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; auto
	hostid:
	disk:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; name=APPDR_QZdg04 id=1298278552.62.QuartzAPPDR
	group:&nbsp;&nbsp;&nbsp;&nbsp; name=APPDR_QZdg id=1142436630.42.QuartzAPPDR
	info:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; format=cdsdisk,privoffset=256,pubslice=2,privslice=2
	flags:&nbsp;&nbsp;&nbsp;&nbsp; online ready private autoconfig imported
	pubpaths:&nbsp; block=/dev/vx/dmp/c2t3d3s2 char=/dev/vx/rdmp/c2t3d3s2
	guid:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {630d5c12-1dd2-11b2-894e-0003badbea62}
	udid:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; HITACHI%5FOPEN-V%20%20%20%20%20%20-SUN%5F06E10%5F6520
	site:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	version:&nbsp;&nbsp; 3.1
	iosize:&nbsp;&nbsp;&nbsp; min=512 (bytes) max=2048 (blocks)
	public:&nbsp;&nbsp;&nbsp; slice=2 offset=2304 len=52406016 disk_offset=0
	private:&nbsp;&nbsp; slice=2 offset=256 len=2048 disk_offset=0
	update:&nbsp;&nbsp;&nbsp; time=1332751618 seqno=0.83
	ssb:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; actual_seqno=0.0
	headers:&nbsp;&nbsp; 0 240
	configs:&nbsp;&nbsp; count=1 len=1280
	logs:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; count=1 len=192
	Defined regions:
	&nbsp;config&nbsp;&nbsp; priv 000048-000239[000192]: copy=01 offset=000000 enabled
	&nbsp;config&nbsp;&nbsp; priv 000256-001343[001088]: copy=01 offset=000192 enabled
	&nbsp;log&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; priv 001344-001535[000192]: copy=01 offset=000000 enabled
	&nbsp;lockrgn&nbsp; priv 001536-001679[000144]: part=00 offset=000000
	Multipathing information:
	numpaths:&nbsp;&nbsp; 2
	c2t3d3s2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; state=enabled
	c3t0d3s2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; state=enabled
	&nbsp;
root@QuartzAPPDR # luxadm inq /dev/rdsk/c2t3d3s2
INQUIRY:
	&nbsp; Physical Path:
	&nbsp; /devices/pci@8,600000/fibre-channel@1/sd@3,3:c,raw
	Vendor:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; HITACHI
	Product:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OPEN-V&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -SUN
	Revision:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 6008
	Serial Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 50 06E106520
	Device type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x0 (Disk device)
	Removable media:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	ISO version:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	ECMA version:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	ANSI version:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2 (Device complies to ANSI X3.131-1994 (SCSI-2))
	Response data format:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2
	Additional length:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0xcf
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; VENDOR-SPECIFIC PARAMETERS
	Byte#&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Hex Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ASCII
	52&nbsp;&nbsp;&nbsp; 01 01 01 01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ....
	96&nbsp;&nbsp;&nbsp; 00 0a 12 00 65 65 ff 00 21 00 00 e0 8b 81 8c a3&nbsp;&nbsp;&nbsp;&nbsp; ....ee..!.......
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 20 00 00 e0 8b 81 8c a3 12 00 00 04 00 00 00 00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ...............
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00&nbsp;&nbsp;&nbsp;&nbsp; ................
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00&nbsp;&nbsp;&nbsp;&nbsp; ................
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00&nbsp;&nbsp;&nbsp;&nbsp; ................
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00&nbsp;&nbsp;&nbsp;&nbsp; ................
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00&nbsp;&nbsp;&nbsp;&nbsp; ................
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 00 00 00 00&nbsp; &nbsp;

tonygriffiths · Answer

Not sure why the vxreattach did not resolve this, but Har-D's suggestion of re-attaching the plex should resolve it as long as there are no further i/o issues with the device.
&nbsp;
cheers

gaurav_s · Answer

Har-D's suggestion should be the right option here as this is a mirrored volume ...
You could have used vxmend commands to fix the plex states but that may need volume to stop &amp; start (which is outage to volume) ... rather it can be done online by keeping the volume running with active plex APPDR_QZVOLnew-01 &amp; disassociating &amp; reassociating the plex ...
cheers
&nbsp;
G

Forum Discussion

Plex in detached/active state

5 Replies

Related Content

plex at TEMPRMSD state

plex

plex

plex node

Number of Plexes

Recent Discussions

DataDomain To StoreOnce Migration

VCS ERROR V-16-1-10205 Group Mediation_NFS is faulted on system com1em03

vxprivutil

URGENT disk oublic region recover

super block corrupt