headers
badlya badlya | 1 Aug 2011 08:33
Picon

pathtype

Hi ALL,


I have some of the disks with state as enabled but some others (within same dg) have primary/secondary (first/second path). 


c3t10d34s2      state=enabled
c6t13d34s2      state=enabled

So are the above disks in active/active or primary/primary state or else.

=========

c3t14d4s2       state=enabled   type=primary
c5t14d4s2       state=enabled   type=secondary

<div>
<p>Hi ALL,</p>
<div><br></div>
<div>I have some of the disks with state as enabled but some others (within same dg) have primary/secondary (first/second path).&nbsp;</div>
<div><br></div>
<div>
<div><br></div>
<div>c3t10d34s2 &nbsp; &nbsp; &nbsp;state=enabled</div>
<div>c6t13d34s2 &nbsp; &nbsp; &nbsp;state=enabled</div>
</div>
<div><br></div>
<div>So are the above disks in active/active or primary/primary state or else.</div>
<div><br></div>
<div>=========</div>
<div>
<div><br></div>
<div>c3t14d4s2 &nbsp; &nbsp; &nbsp; state=enabled &nbsp; type=primary</div>
<div>c5t14d4s2 &nbsp; &nbsp; &nbsp; state=enabled &nbsp; type=secondary</div>
</div>
<div><br></div>
</div>
Permalink | Reply | 1 comment |
headers
Hari Vemuri | 2 Aug 2011 06:54
Favicon

Re: pathtype

If the pathtype is not specified then its an Active/Active LUN. If the pathtype is specified then its an
Active/Passive or Asymmetric Active/Active [ALUA] LUN. All primary paths would be shown with pathtype
as 'primary' and same is the case with 'secondary' paths.

With regards 
Hari
-----Original Message-----
From: veritas-vx-bounces <at> mailman.eng.auburn.edu
[mailto:veritas-vx-bounces <at> mailman.eng.auburn.edu] On Behalf Of veritas-vx-request <at> mailman.eng.auburn.edu
Sent: Monday, August 01, 2011 10:30 PM
To: veritas-vx <at> mailman.eng.auburn.edu
Subject: Veritas-vx Digest, Vol 61, Issue 1

Send Veritas-vx mailing list submissions to
	veritas-vx <at> mailman.eng.auburn.edu

To subscribe or unsubscribe via the World Wide Web, visit
	http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
or, via email, send a message with subject or body 'help' to
	veritas-vx-request <at> mailman.eng.auburn.edu

You can reach the person managing the list at
	veritas-vx-owner <at> mailman.eng.auburn.edu

When replying, please edit your Subject line so it is more specific than "Re: Contents of Veritas-vx digest..."

Today's Topics:

   1. pathtype (badlya badlya)

----------------------------------------------------------------------

Message: 1
Date: Mon, 1 Aug 2011 12:03:53 +0530
From: badlya badlya <badlya.dibil <at> gmail.com>
Subject: [Veritas-vx] pathtype
To: veritas-vx <at> mailman.eng.auburn.edu
Message-ID:
	<CAANE1w1kAPtcBz1xEc8CzQpfE_DSe1inixnh69ga353gBhwhiQ <at> mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Hi ALL,

I have some of the disks with state as enabled but some others (within same
dg) have primary/secondary (first/second path).

c3t10d34s2      state=enabled
c6t13d34s2      state=enabled

So are the above disks in active/active or primary/primary state or else.

=========

c3t14d4s2       state=enabled   type=primary
c5t14d4s2       state=enabled   type=secondary
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-vx/attachments/20110801/d57210b5/attachment-0001.htm 

------------------------------

_______________________________________________
Veritas-vx maillist  -  Veritas-vx <at> mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

End of Veritas-vx Digest, Vol 61, Issue 1
*****************************************
Permalink | Reply | 0 comments |
headers
badlya badlya | 2 Aug 2011 10:49
Picon

Re: pathtype

thanks Hari. even i got the same input from google as well.  as i didn't get any response  i have done some testing on my machines. here are my findings.

1. The process doesn't use both the disks (basically reads only) simultaneously when pathtype is not specified (active / active position)

(verified using vxdmp stat)

2. i tried to make the both the disks as primary after than it started using both the disks... 

so which one is working one. active/active or primary/primary.?


-----Original Message-----
From: veritas-vx-bounces <at> mailman.eng.auburn.edu [mailto:veritas-vx-bounces <at> mailman.eng.auburn.edu] On Behalf Of Hari Vemuri
Sent: Tuesday, August 02, 2011 10:25 AM
To: veritas-vx <at> mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] pathtype

If the pathtype is not specified then its an Active/Active LUN. If the pathtype is specified then its an Active/Passive or Asymmetric Active/Active [ALUA] LUN. All primary paths would be shown with pathtype as 'primary' and same is the case with 'secondary' paths.

 

With regards

Hari



On Mon, Aug 1, 2011 at 12:03 PM, badlya badlya <badlya.dibil <at> gmail.com> wrote:
Hi ALL,

I have some of the disks with state as enabled but some others (within same dg) have primary/secondary (first/second path). 


c3t10d34s2      state=enabled
c6t13d34s2      state=enabled

So are the above disks in active/active or primary/primary state or else.

=========

c3t14d4s2       state=enabled   type=primary
c5t14d4s2       state=enabled   type=secondary


<div>
<p class="MsoPlainText">thanks Hari. even i got the same input from google as well. &nbsp;as i didn't get any response &nbsp;i have done some testing on my machines. here are my findings.</p>
<p class="MsoPlainText">1. The process doesn't use both the disks (basically reads only) simultaneously when pathtype is not specified (active / active position)</p>
<p class="MsoPlainText">(verified using vxdmp stat)</p>
<p class="MsoPlainText">2. i tried to make the both the disks as primary after than it started using both the disks...&nbsp;</p>
<p class="MsoPlainText">so which one is working one. active/active or primary/primary.?</p>
<p class="MsoPlainText"><br></p>
<p class="MsoPlainText">-----Original Message-----<br>
From: <a href="mailto:veritas-vx-bounces <at> mailman.eng.auburn.edu">veritas-vx-bounces <at> mailman.eng.auburn.edu</a>
[mailto:<a href="mailto:veritas-vx-bounces <at> mailman.eng.auburn.edu">veritas-vx-bounces <at> mailman.eng.auburn.edu</a>] On Behalf Of Hari Vemuri<br>
Sent: Tuesday, August 02, 2011 10:25 AM<br>
To: <a href="mailto:veritas-vx <at> mailman.eng.auburn.edu">veritas-vx <at> mailman.eng.auburn.edu</a><br>
Subject: Re: [Veritas-vx] pathtype</p>

<p class="MsoPlainText">If the pathtype is not specified then its an
Active/Active LUN. If the pathtype is specified then its an Active/Passive or
Asymmetric Active/Active [ALUA] LUN. All primary paths would be shown with
pathtype as 'primary' and same is the case with 'secondary' paths.</p>

<p class="MsoPlainText">&nbsp;</p>

<p class="MsoPlainText">With regards</p>

<p class="MsoPlainText">Hari</p>
<p class="MsoPlainText"><br></p>
<br><div class="gmail_quote">On Mon, Aug 1, 2011 at 12:03 PM, badlya badlya <span dir="ltr">&lt;<a href="mailto:badlya.dibil <at> gmail.com">badlya.dibil <at> gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">Hi ALL,<div><br></div>
<div>I have some of the disks with state as enabled but some others (within same dg) have primary/secondary (first/second path).&nbsp;</div>
<div><br></div>
<div>
<div><br></div>
<div>c3t10d34s2 &nbsp; &nbsp; &nbsp;state=enabled</div>
<div>c6t13d34s2 &nbsp; &nbsp; &nbsp;state=enabled</div>
</div>
<div><br></div>
<div>So are the above disks in active/active or primary/primary state or else.</div>
<div><br></div>
<div>=========</div>
<div>
<div><br></div>
<div>c3t14d4s2 &nbsp; &nbsp; &nbsp; state=enabled &nbsp; type=primary</div>

<div>c5t14d4s2 &nbsp; &nbsp; &nbsp; state=enabled &nbsp; type=secondary</div>
</div>
<div><br></div>
</blockquote>
</div>
<br>
</div>
Permalink | Reply | 0 comments |
headers
Lupin Deterd | 16 Aug 2011 13:19
Picon

Ghost VXVM Devices

Hi All,

I need some help tips on this, basically I don't know the exact
history of this server but I just destroy the last DG and remove the
disk that is part of that DG on the VXVM control.

I did:

# vxvol -g dg_name stopall
# vxdg destroy dg_name
# vxdisk rm disk_name
# unbind the LUN(EMC)
# clear the dead paths
# devfsadm -C
# vxdctl enable
# vxconfigd -k

after that I got this this additional Devices(EMC_*): which not there
before when I run the same command.

# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON1_0 auto            -            -            error
c6t0d0s2     auto:none       -            -            online invalid
c6t1d0s2     auto:none       -            -            online invalid
c6t2d0s2     auto:none       -            -            online invalid

# vxdisk list EMC_CLARiiON1_0
Device:    EMC_CLARiiON1_0
devicetag: EMC_CLARiiON1_0
type:      auto
flags:     online error private autoconfig
errno:     Device path not valid
Multipathing information:
numpaths:   4
c5t5006016139A0222Ed0s2 state=disabled
c5t5006016839A0222Ed0s2 state=disabled
c2t5006016039A0222Ed0s2 state=disabled
c2t5006016939A0222Ed0s2 state=disabled

My question is where did this coming from? And why it's not there
until I reset the vxconfigd?

TIA,

lupin
Permalink | Reply | 7 comments |
headers
William Havey | 16 Aug 2011 19:46
Picon

Re: Ghost VXVM Devices

Lupin
vxconfigd reads a file /etc/vx/disk.info in some versions of VM. See if this ascii text file exists, then if it does, edit out the lines in the file which concern the "ghost" disks and reset vxconfigd again.
Bill


On Tue, Aug 16, 2011 at 7:19 AM, Lupin Deterd <lupindeterd <at> gmail.com> wrote:
Hi All,

I need some help tips on this, basically I don't know the exact
history of this server but I just destroy the last DG and remove the
disk that is part of that DG on the VXVM control.

I did:

# vxvol -g dg_name stopall
# vxdg destroy dg_name
# vxdisk rm disk_name
# unbind the LUN(EMC)
# clear the dead paths
# devfsadm -C
# vxdctl enable
# vxconfigd -k

after that I got this this additional Devices(EMC_*): which not there
before when I run the same command.


# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON1_0 auto            -            -            error
c6t0d0s2     auto:none       -            -            online invalid
c6t1d0s2     auto:none       -            -            online invalid
c6t2d0s2     auto:none       -            -            online invalid

# vxdisk list EMC_CLARiiON1_0
Device:    EMC_CLARiiON1_0
devicetag: EMC_CLARiiON1_0
type:      auto
flags:     online error private autoconfig
errno:     Device path not valid
Multipathing information:
numpaths:   4
c5t5006016139A0222Ed0s2 state=disabled
c5t5006016839A0222Ed0s2 state=disabled
c2t5006016039A0222Ed0s2 state=disabled
c2t5006016939A0222Ed0s2 state=disabled


My question is where did this coming from? And why it's not there
until I reset the vxconfigd?


TIA,

lupin
_______________________________________________
Veritas-vx maillist  -  Veritas-vx <at> mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx



--
William (Bill) Havey
Symantec Certified HA Professional
917 515-3385
 

<div>
<div>Lupin</div>
<div> </div>
<div>vxconfigd reads a file /etc/vx/≤a href="http://disk.info">disk.info</a> in some versions of VM. See if this ascii text file exists, then if it does, edit out the lines in the file which concern the "ghost" disks and reset vxconfigd again.</div>
<div> </div>
<div>Bill<br><br><br>
</div>
<div class="gmail_quote">On Tue, Aug 16, 2011 at 7:19 AM, Lupin Deterd <span dir="ltr">&lt;<a href="mailto:lupindeterd <at> gmail.com">lupindeterd <at> gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
Hi All,<br><br>
I need some help tips on this, basically I don't know the exact<br>
history of this server but I just destroy the last DG and remove the<br>
disk that is part of that DG on the VXVM control.<br><br>
I did:<br><br>
# vxvol -g dg_name stopall<br>
# vxdg destroy dg_name<br>
# vxdisk rm disk_name<br>
# unbind the LUN(EMC)<br>
# clear the dead paths<br>
# devfsadm -C<br>
# vxdctl enable<br>
# vxconfigd -k<br><br>
after that I got this this additional Devices(EMC_*): which not there<br>
before when I run the same command.<br><br><br>
# vxdisk list<br>
DEVICE &nbsp; &nbsp; &nbsp; TYPE &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;DISK &nbsp; &nbsp; &nbsp; &nbsp; GROUP &nbsp; &nbsp; &nbsp; &nbsp;STATUS<br>
EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
EMC_CLARiiON1_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
c6t0d0s2 &nbsp; &nbsp; auto:none &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;online invalid<br>
c6t1d0s2 &nbsp; &nbsp; auto:none &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;online invalid<br>
c6t2d0s2 &nbsp; &nbsp; auto:none &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;online invalid<br><br>
# vxdisk list EMC_CLARiiON1_0<br>
Device: &nbsp; &nbsp;EMC_CLARiiON1_0<br>
devicetag: EMC_CLARiiON1_0<br>
type: &nbsp; &nbsp; &nbsp;auto<br>
flags: &nbsp; &nbsp; online error private autoconfig<br>
errno: &nbsp; &nbsp; Device path not valid<br>
Multipathing information:<br>
numpaths: &nbsp; 4<br>
c5t5006016139A0222Ed0s2 state=disabled<br>
c5t5006016839A0222Ed0s2 state=disabled<br>
c2t5006016039A0222Ed0s2 state=disabled<br>
c2t5006016939A0222Ed0s2 state=disabled<br><br><br>
My question is where did this coming from? And why it's not there<br>
until I reset the vxconfigd?<br><br><br>
TIA,<br><br>
lupin<br>
_______________________________________________<br>
Veritas-vx maillist &nbsp;- &nbsp;<a href="mailto:Veritas-vx <at> mailman.eng.auburn.edu">Veritas-vx <at> mailman.eng.auburn.edu</a><br><a href="http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx" target="_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx</a><br>
</blockquote>
</div>
<br><br clear="all"><br>-- <br><div>William (Bill) Havey</div>
<div>Symantec Certified HA&nbsp;Professional</div>
<div>917 515-3385</div>
<div>
<span></span><span></span>&nbsp;</div>
<br>
</div>
Permalink | Reply | 6 comments |
headers
Lupin Deterd | 17 Aug 2011 07:43
Picon

Re: Ghost VXVM Devices

Hi Bill,

After doing what you've suggested(edited the file), I encountered this
error during the vxconfigd -k.

root <at> sv3# vxconfigd -k
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed5s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed10s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed6s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed3s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed8s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed12s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed7s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed9s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016939A0222Ed11s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016939A0222Ed8s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016939A0222Ed2s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed1s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed11s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016939A0222Ed12s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c5t5006016839A0222Ed8s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016939A0222Ed6s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016939A0222Ed10s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower3c
by NR list: No such device or address
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower8c
by NR list: No such device or address
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/emcpower21c by NR list: No such device or address
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/emcpower19c by NR list: No such device or address
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/emcpower15c by NR list: No such device or address

And the list afterwards, those disks comes up again.

 vxdisk -e -o alldgs list
DEVICE       TYPE      DISK         GROUP        STATUS       OS_NATIVE_NAME
EMC_CLARiiON0_0 auto      -             -            error
c2t5006016930603960d0s2
EMC_CLARiiON0_0 auto      -             -            error
c2t5006016930603960d0s2
EMC_CLARiiON0_0 auto      -             -            error
c2t5006016930603960d0s2
EMC_CLARiiON0_0 auto      -             -            error
c2t5006016930603960d0s2
EMC_CLARiiON0_0 auto      -             -            error
c2t5006016930603960d0s2
EMC_CLARiiON1_0 auto      -             -            error
c5t5006016139A0222Ed0s2
c6t0d0s2     auto      -             -            online       c6t0d0s2
c6t1d0s2     auto      -             -            online       c6t1d0s2
c6t2d0s2     auto      -             -            online       c6t2d0s2
emcpower9s2  auto      -             -            error        emcpower9c
emcpower10s2 auto      -             -            error        emcpower10c
emcpower11s2 auto      -             -            error        emcpower11c
emcpower12s2 auto      -             -            error        emcpower12c
emcpower13s2 auto      -             -            error        emcpower13c
emcpower14s2 auto      -             -            error        emcpower14c
emcpower15s2 auto      -             -            error        emcpower15c
emcpower17s2 auto      -             -            error        emcpower17c
emcpower18s2 auto      -             -            error        emcpower18c
emcpower19s2 auto      -             -            error        emcpower19c
emcpower20s2 auto      -             -            error        emcpower20c
emcpower21s2 auto      -             -            error        emcpower21c
emcpower22s2 auto      -             -            error        emcpower22c

Would deleting the disk.info file, help?

TIA,

lupin

On Wed, Aug 17, 2011 at 1:46 AM, William Havey <bbhavey <at> gmail.com> wrote:
> Lupin
> vxconfigd reads a file /etc/vx/disk.info in some versions of VM. See if this
> ascii text file exists, then if it does, edit out the lines in the file
> which concern the "ghost" disks and reset vxconfigd again.
> Bill
>
>
> On Tue, Aug 16, 2011 at 7:19 AM, Lupin Deterd <lupindeterd <at> gmail.com> wrote:
>>
>> Hi All,
>>
>> I need some help tips on this, basically I don't know the exact
>> history of this server but I just destroy the last DG and remove the
>> disk that is part of that DG on the VXVM control.
>>
>> I did:
>>
>> # vxvol -g dg_name stopall
>> # vxdg destroy dg_name
>> # vxdisk rm disk_name
>> # unbind the LUN(EMC)
>> # clear the dead paths
>> # devfsadm -C
>> # vxdctl enable
>> # vxconfigd -k
>>
>> after that I got this this additional Devices(EMC_*): which not there
>> before when I run the same command.
>>
>>
>> # vxdisk list
>> DEVICE       TYPE            DISK         GROUP        STATUS
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON1_0 auto            -            -            error
>> c6t0d0s2     auto:none       -            -            online invalid
>> c6t1d0s2     auto:none       -            -            online invalid
>> c6t2d0s2     auto:none       -            -            online invalid
>>
>> # vxdisk list EMC_CLARiiON1_0
>> Device:    EMC_CLARiiON1_0
>> devicetag: EMC_CLARiiON1_0
>> type:      auto
>> flags:     online error private autoconfig
>> errno:     Device path not valid
>> Multipathing information:
>> numpaths:   4
>> c5t5006016139A0222Ed0s2 state=disabled
>> c5t5006016839A0222Ed0s2 state=disabled
>> c2t5006016039A0222Ed0s2 state=disabled
>> c2t5006016939A0222Ed0s2 state=disabled
>>
>>
>> My question is where did this coming from? And why it's not there
>> until I reset the vxconfigd?
>>
>>
>> TIA,
>>
>> lupin
>> _______________________________________________
>> Veritas-vx maillist  -  Veritas-vx <at> mailman.eng.auburn.edu
>> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>
>
> --
> William (Bill) Havey
> Symantec Certified HA Professional
> 917 515-3385
>
>
Permalink | Reply | 5 comments |
headers
William Havey | 17 Aug 2011 16:13
Picon

Re: Ghost VXVM Devices

This seems to be the right track but we may not have gone far enough. By this I mean I went to sort.symantec.con and searched on the error code V-5-1-8645. I got two hits. I selected the second,   www.symantec.com/docs/TECH61541 because it referenced a tech note. The note is about Netbackup but, ignoring that, the end of the note states to do this
 
Resolution:
Move the contents of the /etc/vx/disk.info, /etc/vx/array.info and /etc/vx/jbod.info directories to an alternate location and reboot:

# mv /etc/vx/disk.info /root/etc_vx_disk.info.OLD
# mv /etc/vx/array.info /root/etc_vx_array.info.OLD
# mv /etc/vx/jbod.info /root/etc_vx_jbod.info.OLD

# reboot
If a reboot is possible the above listed files will be re-created. If reboot is not possible, I'd use "vxconfigd -k -m enable"
On Wed, Aug 17, 2011 at 1:43 AM, Lupin Deterd <lupindeterd <at> gmail.com> wrote:
Hi Bill,

After doing what you've suggested(edited the file), I encountered this
error during the vxconfigd -k.

root <at> sv3# vxconfigd -k
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed5s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed10s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed6s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed3s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed8s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed12s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed7s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed9s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016939A0222Ed11s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016939A0222Ed8s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016939A0222Ed2s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed1s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed11s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016939A0222Ed12s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c5t5006016839A0222Ed8s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016939A0222Ed6s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016939A0222Ed10s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower3c
by NR list: No such device or address
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower8c
by NR list: No such device or address
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/emcpower21c by NR list: No such device or address
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/emcpower19c by NR list: No such device or address
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/emcpower15c by NR list: No such device or address

And the list afterwards, those disks comes up again.

 vxdisk -e -o alldgs list
DEVICE       TYPE      DISK         GROUP        STATUS       OS_NATIVE_NAME
EMC_CLARiiON0_0 auto      -             -            error
c2t5006016930603960d0s2
EMC_CLARiiON0_0 auto      -             -            error
c2t5006016930603960d0s2
EMC_CLARiiON0_0 auto      -             -            error
c2t5006016930603960d0s2
EMC_CLARiiON0_0 auto      -             -            error
c2t5006016930603960d0s2
EMC_CLARiiON0_0 auto      -             -            error
c2t5006016930603960d0s2
EMC_CLARiiON1_0 auto      -             -            error
c5t5006016139A0222Ed0s2
c6t0d0s2     auto      -             -            online       c6t0d0s2
c6t1d0s2     auto      -             -            online       c6t1d0s2
c6t2d0s2     auto      -             -            online       c6t2d0s2
emcpower9s2  auto      -             -            error        emcpower9c
emcpower10s2 auto      -             -            error        emcpower10c
emcpower11s2 auto      -             -            error        emcpower11c
emcpower12s2 auto      -             -            error        emcpower12c
emcpower13s2 auto      -             -            error        emcpower13c
emcpower14s2 auto      -             -            error        emcpower14c
emcpower15s2 auto      -             -            error        emcpower15c
emcpower17s2 auto      -             -            error        emcpower17c
emcpower18s2 auto      -             -            error        emcpower18c
emcpower19s2 auto      -             -            error        emcpower19c
emcpower20s2 auto      -             -            error        emcpower20c
emcpower21s2 auto      -             -            error        emcpower21c
emcpower22s2 auto      -             -            error        emcpower22c


Would deleting the disk.info file, help?

TIA,

lupin

On Wed, Aug 17, 2011 at 1:46 AM, William Havey <bbhavey <at> gmail.com> wrote:
> Lupin
> vxconfigd reads a file /etc/vx/disk.info in some versions of VM. See if this
> ascii text file exists, then if it does, edit out the lines in the file
> which concern the "ghost" disks and reset vxconfigd again.
> Bill
>
>
> On Tue, Aug 16, 2011 at 7:19 AM, Lupin Deterd <lupindeterd <at> gmail.com> wrote:
>>
>> Hi All,
>>
>> I need some help tips on this, basically I don't know the exact
>> history of this server but I just destroy the last DG and remove the
>> disk that is part of that DG on the VXVM control.
>>
>> I did:
>>
>> # vxvol -g dg_name stopall
>> # vxdg destroy dg_name
>> # vxdisk rm disk_name
>> # unbind the LUN(EMC)
>> # clear the dead paths
>> # devfsadm -C
>> # vxdctl enable
>> # vxconfigd -k
>>
>> after that I got this this additional Devices(EMC_*): which not there
>> before when I run the same command.
>>
>>
>> # vxdisk list
>> DEVICE       TYPE            DISK         GROUP        STATUS
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON0_0 auto            -            -            error
>> EMC_CLARiiON1_0 auto            -            -            error
>> c6t0d0s2     auto:none       -            -            online invalid
>> c6t1d0s2     auto:none       -            -            online invalid
>> c6t2d0s2     auto:none       -            -            online invalid
>>
>> # vxdisk list EMC_CLARiiON1_0
>> Device:    EMC_CLARiiON1_0
>> devicetag: EMC_CLARiiON1_0
>> type:      auto
>> flags:     online error private autoconfig
>> errno:     Device path not valid
>> Multipathing information:
>> numpaths:   4
>> c5t5006016139A0222Ed0s2 state=disabled
>> c5t5006016839A0222Ed0s2 state=disabled
>> c2t5006016039A0222Ed0s2 state=disabled
>> c2t5006016939A0222Ed0s2 state=disabled
>>
>>
>> My question is where did this coming from? And why it's not there
>> until I reset the vxconfigd?
>>
>>
>> TIA,
>>
>> lupin
>> _______________________________________________
>> Veritas-vx maillist  -  Veritas-vx <at> mailman.eng.auburn.edu
>> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>
>
> --
> William (Bill) Havey
> Symantec Certified HA Professional
> 917 515-3385
>
>



--
William (Bill) Havey
Symantec Certified HA Professional
917 515-3385
 

<div>
<div>This seems to be the right track but we may not have gone far enough. By this I mean I went to sort.symantec.con and searched on the error code V-5-1-8645. I got two hits. I selected the second,&nbsp;&nbsp; <a href="http://www.symantec.com/docs/TECH61541">www.symantec.com/docs/TECH61541</a>&nbsp;because it referenced a tech note. The note is about Netbackup but, ignoring that, the end of the note states to do this</div>
<div>&nbsp;</div>
<div>Resolution:<br>Move the contents of the /etc/vx/≤a href="http://disk.info">disk.info</a>, /etc/vx/≤a href="http://array.info">array.info</a> and /etc/vx/≤a href="http://jbod.info">jbod.info</a> directories to an alternate location and reboot:<br><br><span class="FIXEDFONT"># mv /etc/vx/≤a href="http://disk.info">disk.info</a> /root/etc_vx_disk.info.OLD</span><br><span class="FIXEDFONT"># mv /etc/vx/≤a href="http://array.info">array.info</a> /root/etc_vx_array.info.OLD</span><br><span class="FIXEDFONT"># mv /etc/vx/≤a href="http://jbod.info">jbod.info</a> /root/etc_vx_jbod.info.OLD</span><br><br><span class="FIXEDFONT"># reboot</span><br>
</div>
<div>If a reboot is possible the above listed files will be re-created. If reboot is not possible, I'd use "vxconfigd -k -m enable"<br>
</div>
<div class="gmail_quote">On Wed, Aug 17, 2011 at 1:43 AM, Lupin Deterd <span dir="ltr">&lt;<a href="mailto:lupindeterd <at> gmail.com">lupindeterd <at> gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
Hi Bill,<br><br>
After doing what you've suggested(edited the file), I encountered this<br>
error during the vxconfigd -k.<br><br>
root <at> sv3# vxconfigd -k<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016039A0222Ed5s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016039A0222Ed10s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016039A0222Ed6s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016039A0222Ed3s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016039A0222Ed8s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016039A0222Ed12s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016039A0222Ed7s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016039A0222Ed9s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016939A0222Ed11s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016939A0222Ed8s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016939A0222Ed2s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016039A0222Ed1s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016039A0222Ed11s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016939A0222Ed12s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c5t5006016839A0222Ed8s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016939A0222Ed6s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/c2t5006016939A0222Ed10s2 by NR list: I/O error<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower3c<br>
by NR list: No such device or address<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower8c<br>
by NR list: No such device or address<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/emcpower21c by NR list: No such device or address<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/emcpower19c by NR list: No such device or address<br>
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming<br>
/dev/rdsk/emcpower15c by NR list: No such device or address<br><br>
And the list afterwards, those disks comes up again.<br><br>
&nbsp;vxdisk -e -o alldgs list<br>
DEVICE &nbsp; &nbsp; &nbsp; TYPE &nbsp; &nbsp; &nbsp;DISK &nbsp; &nbsp; &nbsp; &nbsp; GROUP &nbsp; &nbsp; &nbsp; &nbsp;STATUS &nbsp; &nbsp; &nbsp; OS_NATIVE_NAME<br><div class="im">EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
</div>c2t5006016930603960d0s2<br><div class="im">EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
</div>c2t5006016930603960d0s2<br><div class="im">EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
</div>c2t5006016930603960d0s2<br><div class="im">EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
</div>c2t5006016930603960d0s2<br><div class="im">EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
</div>c2t5006016930603960d0s2<br><div class="im">EMC_CLARiiON1_0 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
</div>c5t5006016139A0222Ed0s2<br>
c6t0d0s2 &nbsp; &nbsp; auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;online &nbsp; &nbsp; &nbsp; c6t0d0s2<br>
c6t1d0s2 &nbsp; &nbsp; auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;online &nbsp; &nbsp; &nbsp; c6t1d0s2<br>
c6t2d0s2 &nbsp; &nbsp; auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;online &nbsp; &nbsp; &nbsp; c6t2d0s2<br>
emcpower9s2 &nbsp;auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error &nbsp; &nbsp; &nbsp; &nbsp;emcpower9c<br>
emcpower10s2 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error &nbsp; &nbsp; &nbsp; &nbsp;emcpower10c<br>
emcpower11s2 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error &nbsp; &nbsp; &nbsp; &nbsp;emcpower11c<br>
emcpower12s2 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error &nbsp; &nbsp; &nbsp; &nbsp;emcpower12c<br>
emcpower13s2 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error &nbsp; &nbsp; &nbsp; &nbsp;emcpower13c<br>
emcpower14s2 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error &nbsp; &nbsp; &nbsp; &nbsp;emcpower14c<br>
emcpower15s2 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error &nbsp; &nbsp; &nbsp; &nbsp;emcpower15c<br>
emcpower17s2 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error &nbsp; &nbsp; &nbsp; &nbsp;emcpower17c<br>
emcpower18s2 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error &nbsp; &nbsp; &nbsp; &nbsp;emcpower18c<br>
emcpower19s2 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error &nbsp; &nbsp; &nbsp; &nbsp;emcpower19c<br>
emcpower20s2 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error &nbsp; &nbsp; &nbsp; &nbsp;emcpower20c<br>
emcpower21s2 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error &nbsp; &nbsp; &nbsp; &nbsp;emcpower21c<br>
emcpower22s2 auto &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error &nbsp; &nbsp; &nbsp; &nbsp;emcpower22c<br><br><br>
Would deleting the <a href="http://disk.info" target="_blank">disk.info</a> file, help?<br><br>
TIA,<br><br>
lupin<br><div>
<div></div>
<div class="h5">
<br>
On Wed, Aug 17, 2011 at 1:46 AM, William Havey &lt;<a href="mailto:bbhavey <at> gmail.com">bbhavey <at> gmail.com</a>&gt; wrote:<br>
&gt; Lupin<br>
&gt; vxconfigd reads a file /etc/vx/≤a href="http://disk.info" target="_blank">disk.info</a> in some versions of VM. See if this<br>
&gt; ascii text file exists, then if it does, edit out the lines in the file<br>
&gt; which concern the "ghost" disks and reset vxconfigd again.<br>
&gt; Bill<br>
&gt;<br>
&gt;<br>
&gt; On Tue, Aug 16, 2011 at 7:19 AM, Lupin Deterd &lt;<a href="mailto:lupindeterd <at> gmail.com">lupindeterd <at> gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Hi All,<br>
&gt;&gt;<br>
&gt;&gt; I need some help tips on this, basically I don't know the exact<br>
&gt;&gt; history of this server but I just destroy the last DG and remove the<br>
&gt;&gt; disk that is part of that DG on the VXVM control.<br>
&gt;&gt;<br>
&gt;&gt; I did:<br>
&gt;&gt;<br>
&gt;&gt; # vxvol -g dg_name stopall<br>
&gt;&gt; # vxdg destroy dg_name<br>
&gt;&gt; # vxdisk rm disk_name<br>
&gt;&gt; # unbind the LUN(EMC)<br>
&gt;&gt; # clear the dead paths<br>
&gt;&gt; # devfsadm -C<br>
&gt;&gt; # vxdctl enable<br>
&gt;&gt; # vxconfigd -k<br>
&gt;&gt;<br>
&gt;&gt; after that I got this this additional Devices(EMC_*): which not there<br>
&gt;&gt; before when I run the same command.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; # vxdisk list<br>
&gt;&gt; DEVICE &nbsp; &nbsp; &nbsp; TYPE &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;DISK &nbsp; &nbsp; &nbsp; &nbsp; GROUP &nbsp; &nbsp; &nbsp; &nbsp;STATUS<br>
&gt;&gt; EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
&gt;&gt; EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
&gt;&gt; EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
&gt;&gt; EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
&gt;&gt; EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
&gt;&gt; EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
&gt;&gt; EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
&gt;&gt; EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
&gt;&gt; EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
&gt;&gt; EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
&gt;&gt; EMC_CLARiiON0_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
&gt;&gt; EMC_CLARiiON1_0 auto &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;error<br>
&gt;&gt; c6t0d0s2 &nbsp; &nbsp; auto:none &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;online invalid<br>
&gt;&gt; c6t1d0s2 &nbsp; &nbsp; auto:none &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;online invalid<br>
&gt;&gt; c6t2d0s2 &nbsp; &nbsp; auto:none &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;online invalid<br>
&gt;&gt;<br>
&gt;&gt; # vxdisk list EMC_CLARiiON1_0<br>
&gt;&gt; Device: &nbsp; &nbsp;EMC_CLARiiON1_0<br>
&gt;&gt; devicetag: EMC_CLARiiON1_0<br>
&gt;&gt; type: &nbsp; &nbsp; &nbsp;auto<br>
&gt;&gt; flags: &nbsp; &nbsp; online error private autoconfig<br>
&gt;&gt; errno: &nbsp; &nbsp; Device path not valid<br>
&gt;&gt; Multipathing information:<br>
&gt;&gt; numpaths: &nbsp; 4<br>
&gt;&gt; c5t5006016139A0222Ed0s2 state=disabled<br>
&gt;&gt; c5t5006016839A0222Ed0s2 state=disabled<br>
&gt;&gt; c2t5006016039A0222Ed0s2 state=disabled<br>
&gt;&gt; c2t5006016939A0222Ed0s2 state=disabled<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; My question is where did this coming from? And why it's not there<br>
&gt;&gt; until I reset the vxconfigd?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; TIA,<br>
&gt;&gt;<br>
&gt;&gt; lupin<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; Veritas-vx maillist &nbsp;- &nbsp;<a href="mailto:Veritas-vx <at> mailman.eng.auburn.edu">Veritas-vx <at> mailman.eng.auburn.edu</a><br>
&gt;&gt; <a href="http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx" target="_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; William (Bill) Havey<br>
&gt; Symantec Certified HA&nbsp;Professional<br>
&gt; <a href="tel:917%20515-3385" value="+19175153385">917 515-3385</a><br>
&gt;<br>
&gt;<br>
</div>
</div>
</blockquote>
</div>
<br><br clear="all"><br>-- <br><div>William (Bill) Havey</div>
<div>Symantec Certified HA&nbsp;Professional</div>
<div>917 515-3385</div>
<div>
<span></span><span></span>&nbsp;</div>
<br>
</div>
Permalink | Reply | 4 comments |
headers
Hari Vemuri | 17 Aug 2011 16:42
Favicon

Re: Ghost VXVM Devices

Just do "vxdisk rm <name>" on each of the ghost devices and check. VxVM sometimes keeps records of disks it
has seen in the past

With regards
Hari
-----Original Message-----
From: veritas-vx-bounces <at> mailman.eng.auburn.edu
[mailto:veritas-vx-bounces <at> mailman.eng.auburn.edu] On Behalf Of veritas-vx-request <at> mailman.eng.auburn.edu
Sent: Tuesday, August 16, 2011 10:30 PM
To: veritas-vx <at> mailman.eng.auburn.edu
Subject: Veritas-vx Digest, Vol 61, Issue 3

Send Veritas-vx mailing list submissions to
	veritas-vx <at> mailman.eng.auburn.edu

To subscribe or unsubscribe via the World Wide Web, visit
	http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
or, via email, send a message with subject or body 'help' to
	veritas-vx-request <at> mailman.eng.auburn.edu

You can reach the person managing the list at
	veritas-vx-owner <at> mailman.eng.auburn.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Veritas-vx digest..."

Today's Topics:

   1. Ghost VXVM Devices (Lupin Deterd)

----------------------------------------------------------------------

Message: 1
Date: Tue, 16 Aug 2011 19:19:13 +0800
From: Lupin Deterd <lupindeterd <at> gmail.com>
Subject: [Veritas-vx] Ghost VXVM Devices
To: veritas-vx <at> mailman.eng.auburn.edu
Message-ID:
	<CAL0mBkS-azjiGW7_shw_V5JYueTkaGiqaebszDr0d1KEqhcy6Q <at> mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hi All,

I need some help tips on this, basically I don't know the exact
history of this server but I just destroy the last DG and remove the
disk that is part of that DG on the VXVM control.

I did:

# vxvol -g dg_name stopall
# vxdg destroy dg_name
# vxdisk rm disk_name
# unbind the LUN(EMC)
# clear the dead paths
# devfsadm -C
# vxdctl enable
# vxconfigd -k

after that I got this this additional Devices(EMC_*): which not there
before when I run the same command.

# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON0_0 auto            -            -            error
EMC_CLARiiON1_0 auto            -            -            error
c6t0d0s2     auto:none       -            -            online invalid
c6t1d0s2     auto:none       -            -            online invalid
c6t2d0s2     auto:none       -            -            online invalid

# vxdisk list EMC_CLARiiON1_0
Device:    EMC_CLARiiON1_0
devicetag: EMC_CLARiiON1_0
type:      auto
flags:     online error private autoconfig
errno:     Device path not valid
Multipathing information:
numpaths:   4
c5t5006016139A0222Ed0s2 state=disabled
c5t5006016839A0222Ed0s2 state=disabled
c2t5006016039A0222Ed0s2 state=disabled
c2t5006016939A0222Ed0s2 state=disabled

My question is where did this coming from? And why it's not there
until I reset the vxconfigd?

TIA,

lupin

------------------------------

_______________________________________________
Veritas-vx maillist  -  Veritas-vx <at> mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

End of Veritas-vx Digest, Vol 61, Issue 3
*****************************************
Permalink | Reply | 1 comment |
headers
Lupin Deterd | 18 Aug 2011 07:02
Picon

Re: Ghost VXVM Devices

On Wed, Aug 17, 2011 at 10:13 PM, William Havey <bbhavey <at> gmail.com> wrote:
> This seems to be the right track but we may not have gone far enough. By
> this I mean I went to sort.symantec.con and searched on the error code
> V-5-1-8645. I got two hits. I selected the second,
> www.symantec.com/docs/TECH61541 because it referenced a tech note. The note
> is about Netbackup but, ignoring that, the end of the note states to do this
>
> Resolution:
> Move the contents of the /etc/vx/disk.info, /etc/vx/array.info and
> /etc/vx/jbod.info directories to an alternate location and reboot:
>
> # mv /etc/vx/disk.info /root/etc_vx_disk.info.OLD
> # mv /etc/vx/array.info /root/etc_vx_array.info.OLD
> # mv /etc/vx/jbod.info /root/etc_vx_jbod.info.OLD
>
> # reboot
> If a reboot is possible the above listed files will be re-created. If reboot
> is not possible, I'd use "vxconfigd -k -m enable"
> On Wed, Aug 17, 2011 at 1:43 AM, Lupin Deterd <lupindeterd <at> gmail.com> wrote:
>>

Thanks Bill,

I might try this.

>> Hi Bill,
>>
>> After doing what you've suggested(edited the file), I encountered this
>> error during the vxconfigd -k.
>>
>> root <at> sv3# vxconfigd -k
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016039A0222Ed5s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016039A0222Ed10s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016039A0222Ed6s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016039A0222Ed3s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016039A0222Ed8s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016039A0222Ed12s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016039A0222Ed7s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016039A0222Ed9s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016939A0222Ed11s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016939A0222Ed8s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016939A0222Ed2s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016039A0222Ed1s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016039A0222Ed11s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016939A0222Ed12s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c5t5006016839A0222Ed8s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016939A0222Ed6s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/c2t5006016939A0222Ed10s2 by NR list: I/O error
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower3c
>> by NR list: No such device or address
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower8c
>> by NR list: No such device or address
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/emcpower21c by NR list: No such device or address
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/emcpower19c by NR list: No such device or address
>> VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
>> /dev/rdsk/emcpower15c by NR list: No such device or address
>>
>> And the list afterwards, those disks comes up again.
>>
>>  vxdisk -e -o alldgs list
>> DEVICE       TYPE      DISK         GROUP        STATUS
>> OS_NATIVE_NAME
>> EMC_CLARiiON0_0 auto      -             -            error
>> c2t5006016930603960d0s2
>> EMC_CLARiiON0_0 auto      -             -            error
>> c2t5006016930603960d0s2
>> EMC_CLARiiON0_0 auto      -             -            error
>> c2t5006016930603960d0s2
>> EMC_CLARiiON0_0 auto      -             -            error
>> c2t5006016930603960d0s2
>> EMC_CLARiiON0_0 auto      -             -            error
>> c2t5006016930603960d0s2
>> EMC_CLARiiON1_0 auto      -             -            error
>> c5t5006016139A0222Ed0s2
>> c6t0d0s2     auto      -             -            online       c6t0d0s2
>> c6t1d0s2     auto      -             -            online       c6t1d0s2
>> c6t2d0s2     auto      -             -            online       c6t2d0s2
>> emcpower9s2  auto      -             -            error        emcpower9c
>> emcpower10s2 auto      -             -            error        emcpower10c
>> emcpower11s2 auto      -             -            error        emcpower11c
>> emcpower12s2 auto      -             -            error        emcpower12c
>> emcpower13s2 auto      -             -            error        emcpower13c
>> emcpower14s2 auto      -             -            error        emcpower14c
>> emcpower15s2 auto      -             -            error        emcpower15c
>> emcpower17s2 auto      -             -            error        emcpower17c
>> emcpower18s2 auto      -             -            error        emcpower18c
>> emcpower19s2 auto      -             -            error        emcpower19c
>> emcpower20s2 auto      -             -            error        emcpower20c
>> emcpower21s2 auto      -             -            error        emcpower21c
>> emcpower22s2 auto      -             -            error        emcpower22c
>>
>>
>> Would deleting the disk.info file, help?
>>
>> TIA,
>>
>> lupin
>>
>> On Wed, Aug 17, 2011 at 1:46 AM, William Havey <bbhavey <at> gmail.com> wrote:
>> > Lupin
>> > vxconfigd reads a file /etc/vx/disk.info in some versions of VM. See if
>> > this
>> > ascii text file exists, then if it does, edit out the lines in the file
>> > which concern the "ghost" disks and reset vxconfigd again.
>> > Bill
>> >
>> >
>> > On Tue, Aug 16, 2011 at 7:19 AM, Lupin Deterd <lupindeterd <at> gmail.com>
>> > wrote:
>> >>
>> >> Hi All,
>> >>
>> >> I need some help tips on this, basically I don't know the exact
>> >> history of this server but I just destroy the last DG and remove the
>> >> disk that is part of that DG on the VXVM control.
>> >>
>> >> I did:
>> >>
>> >> # vxvol -g dg_name stopall
>> >> # vxdg destroy dg_name
>> >> # vxdisk rm disk_name
>> >> # unbind the LUN(EMC)
>> >> # clear the dead paths
>> >> # devfsadm -C
>> >> # vxdctl enable
>> >> # vxconfigd -k
>> >>
>> >> after that I got this this additional Devices(EMC_*): which not there
>> >> before when I run the same command.
>> >>
>> >>
>> >> # vxdisk list
>> >> DEVICE       TYPE            DISK         GROUP        STATUS
>> >> EMC_CLARiiON0_0 auto            -            -            error
>> >> EMC_CLARiiON0_0 auto            -            -            error
>> >> EMC_CLARiiON0_0 auto            -            -            error
>> >> EMC_CLARiiON0_0 auto            -            -            error
>> >> EMC_CLARiiON0_0 auto            -            -            error
>> >> EMC_CLARiiON0_0 auto            -            -            error
>> >> EMC_CLARiiON0_0 auto            -            -            error
>> >> EMC_CLARiiON0_0 auto            -            -            error
>> >> EMC_CLARiiON0_0 auto            -            -            error
>> >> EMC_CLARiiON0_0 auto            -            -            error
>> >> EMC_CLARiiON0_0 auto            -            -            error
>> >> EMC_CLARiiON1_0 auto            -            -            error
>> >> c6t0d0s2     auto:none       -            -            online invalid
>> >> c6t1d0s2     auto:none       -            -            online invalid
>> >> c6t2d0s2     auto:none       -            -            online invalid
>> >>
>> >> # vxdisk list EMC_CLARiiON1_0
>> >> Device:    EMC_CLARiiON1_0
>> >> devicetag: EMC_CLARiiON1_0
>> >> type:      auto
>> >> flags:     online error private autoconfig
>> >> errno:     Device path not valid
>> >> Multipathing information:
>> >> numpaths:   4
>> >> c5t5006016139A0222Ed0s2 state=disabled
>> >> c5t5006016839A0222Ed0s2 state=disabled
>> >> c2t5006016039A0222Ed0s2 state=disabled
>> >> c2t5006016939A0222Ed0s2 state=disabled
>> >>
>> >>
>> >> My question is where did this coming from? And why it's not there
>> >> until I reset the vxconfigd?
>> >>
>> >>
>> >> TIA,
>> >>
>> >> lupin
>> >> _______________________________________________
>> >> Veritas-vx maillist  -  Veritas-vx <at> mailman.eng.auburn.edu
>> >> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>> >
>> >
>> >
>> > --
>> > William (Bill) Havey
>> > Symantec Certified HA Professional
>> > 917 515-3385
>> >
>> >
>
>
>
> --
> William (Bill) Havey
> Symantec Certified HA Professional
> 917 515-3385
>
>
Permalink | Reply | 3 comments |
headers
Lupin Deterd | 18 Aug 2011 07:05
Picon

Re: Ghost VXVM Devices

On Wed, Aug 17, 2011 at 10:42 PM, Hari Vemuri <hari_vemuri <at> symantec.com> wrote:
> Just do "vxdisk rm <name>" on each of the ghost devices and check. VxVM sometimes keeps records of disks it
has seen in the past
>

Hello Hari,

I might have missed but yeah I did that already and as Bill suggested
deleted those entry on disk.info as well, but every time I re-run the
vxdiskconfigd -k I got that error and those phantom disk back.

Thanks,

lupin

> With regards
> Hari
> -----Original Message-----
> From: veritas-vx-bounces <at> mailman.eng.auburn.edu
[mailto:veritas-vx-bounces <at> mailman.eng.auburn.edu] On Behalf Of veritas-vx-request <at> mailman.eng.auburn.edu
> Sent: Tuesday, August 16, 2011 10:30 PM
> To: veritas-vx <at> mailman.eng.auburn.edu
> Subject: Veritas-vx Digest, Vol 61, Issue 3
>
> Send Veritas-vx mailing list submissions to
>        veritas-vx <at> mailman.eng.auburn.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
> or, via email, send a message with subject or body 'help' to
>        veritas-vx-request <at> mailman.eng.auburn.edu
>
> You can reach the person managing the list at
>        veritas-vx-owner <at> mailman.eng.auburn.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Veritas-vx digest..."
>
>
> Today's Topics:
>
>   1. Ghost VXVM Devices (Lupin Deterd)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 16 Aug 2011 19:19:13 +0800
> From: Lupin Deterd <lupindeterd <at> gmail.com>
> Subject: [Veritas-vx] Ghost VXVM Devices
> To: veritas-vx <at> mailman.eng.auburn.edu
> Message-ID:
>        <CAL0mBkS-azjiGW7_shw_V5JYueTkaGiqaebszDr0d1KEqhcy6Q <at> mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi All,
>
> I need some help tips on this, basically I don't know the exact
> history of this server but I just destroy the last DG and remove the
> disk that is part of that DG on the VXVM control.
>
> I did:
>
> # vxvol -g dg_name stopall
> # vxdg destroy dg_name
> # vxdisk rm disk_name
> # unbind the LUN(EMC)
> # clear the dead paths
> # devfsadm -C
> # vxdctl enable
> # vxconfigd -k
>
> after that I got this this additional Devices(EMC_*): which not there
> before when I run the same command.
>
>
> # vxdisk list
> DEVICE       TYPE            DISK         GROUP        STATUS
> EMC_CLARiiON0_0 auto            -            -            error
> EMC_CLARiiON0_0 auto            -            -            error
> EMC_CLARiiON0_0 auto            -            -            error
> EMC_CLARiiON0_0 auto            -            -            error
> EMC_CLARiiON0_0 auto            -            -            error
> EMC_CLARiiON0_0 auto            -            -            error
> EMC_CLARiiON0_0 auto            -            -            error
> EMC_CLARiiON0_0 auto            -            -            error
> EMC_CLARiiON0_0 auto            -            -            error
> EMC_CLARiiON0_0 auto            -            -            error
> EMC_CLARiiON0_0 auto            -            -            error
> EMC_CLARiiON1_0 auto            -            -            error
> c6t0d0s2     auto:none       -            -            online invalid
> c6t1d0s2     auto:none       -            -            online invalid
> c6t2d0s2     auto:none       -            -            online invalid
>
> # vxdisk list EMC_CLARiiON1_0
> Device:    EMC_CLARiiON1_0
> devicetag: EMC_CLARiiON1_0
> type:      auto
> flags:     online error private autoconfig
> errno:     Device path not valid
> Multipathing information:
> numpaths:   4
> c5t5006016139A0222Ed0s2 state=disabled
> c5t5006016839A0222Ed0s2 state=disabled
> c2t5006016039A0222Ed0s2 state=disabled
> c2t5006016939A0222Ed0s2 state=disabled
>
>
> My question is where did this coming from? And why it's not there
> until I reset the vxconfigd?
>
>
> TIA,
>
> lupin
>
>
> ------------------------------
>
> _______________________________________________
> Veritas-vx maillist  -  Veritas-vx <at> mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
>
> End of Veritas-vx Digest, Vol 61, Issue 3
> *****************************************
> _______________________________________________
> Veritas-vx maillist  -  Veritas-vx <at> mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
>
Permalink | Reply | 0 comments |

Gmane