[Veritas-vx] vxdisk list shows disk in error status

[Romeo Theriault]

I am using Veritas Volume Manager 4.1 on Solaris 9. Disk c4t2d0s2 shows this
status:

# vxdisk list | grep c4t2d0s2
c4t2d0s2 auto:sliced - - error

# vxdisk list c4t2d0s2
Device: c4t2d0s2
devicetag: c4t2d0
type: auto
info: format=sliced,privoffset=1,pubslice=4,privslice=3
flags: online error private autoconfig
errno: Device path not valid
Multipathing information:
numpaths: 1
c4t2d0s2 state=enabled


Now here's the story, shortened. The disk used to have a vxfs filesystem on
it (which I was unaware of, previous employee put it there and it was no
longer being used). The server, which is using SVM for the localdisk, needed
more swap space so I created a partition on the drive which appeared to be
unused and then added the partition to the existing swap space. Worked well
and was pretty much end of story until I released that the drive used to be
used for a different purpose. Not a big deal but I would like to get rid of
the error state and remove the drive from Veritas's knowledge so it shows up
like the other local drives, which is:

c4t1d0s2 auto:none - - online invalid

I've tried this so far: Stopping swap usage on the drive and then `vxdisk rm
c4t2d0s2`, I then `vxdctl enable` but the drive still shows up in the
errored state.

Does anyone know how I can remove this drive from Veritas Volume Manager
Knowledge?

Thanks for any help.

Romeo

[A Darren Dunham]

Post by Romeo Theriault
I am using Veritas Volume Manager 4.1 on Solaris 9. Disk c4t2d0s2 shows this
# vxdisk list | grep c4t2d0s2
c4t2d0s2 auto:sliced - - error

Is that a problem?

Post by Romeo Theriault
Not a big deal but I would like to get rid of
the error state and remove the drive from Veritas's knowledge so it shows up
c4t1d0s2 auto:none - - online invalid

Use vxdiskunsetup on the disk if it is no longer in any VxVM disk group
and has no valuable data on it. That will remove the VxVM partition
setup on it.

[Romeo Theriault]

Post by A Darren Dunham

Post by Romeo Theriault
I am using Veritas Volume Manager 4.1 on Solaris 9. Disk c4t2d0s2 shows

this

Post by Romeo Theriault
# vxdisk list | grep c4t2d0s2
c4t2d0s2 auto:sliced - - error

Is that a problem?

No, it hasn't been a problem yet, but I'd prefer it didn't turn into one
either.

Post by A Darren Dunham

Post by Romeo Theriault
Not a big deal but I would like to get rid of
the error state and remove the drive from Veritas's knowledge so it

shows up

Post by Romeo Theriault
c4t1d0s2 auto:none - - online invalid

Use vxdiskunsetup on the disk if it is no longer in any VxVM disk group
and has no valuable data on it. That will remove the VxVM partition
setup on it.

Thank you for pointing this out. Though when I run it I get this error.

# vxdiskunsetup c4t2d0
VxVM vxdiskunsetup NOTICE V-5-2-3522 c4t2d0: Disk is not a volume manager
disk

So I guess veritas doesn't seem to think it knows anything about the disk in
this case. I also tried repartitioning and labeling the drive then running
vxdclt enable but it is still showing up as auto:sliced with a status of
error. I'm leaning towards leaving it alone at this point as it doesn't seem
to be causing any problems.

Thanks,

Post by A Darren Dunham
--
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
_______________________________________________
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

[A Darren Dunham]

Post by Romeo Theriault
Thank you for pointing this out. Though when I run it I get this error.
# vxdiskunsetup c4t2d0
VxVM vxdiskunsetup NOTICE V-5-2-3522 c4t2d0: Disk is not a volume manager
disk
So I guess veritas doesn't seem to think it knows anything about the disk in
this case. I also tried repartitioning and labeling the drive then running
vxdclt enable but it is still showing up as auto:sliced with a status of
error. I'm leaning towards leaving it alone at this point as it doesn't seem
to be causing any problems.

It shouldn't cause any problems, but you can likely get rid of it by
adding it back into VxVM and then unsetting it again.

# /usr/lib/vxvm/bin/vxdisksetup -i c1t8d0
# vxdisk list | grep t8
c1t8d0s2 auto:cdsdisk - - online
# /usr/lib/vxvm/bin/vxdiskunsetup c1t8d0
# vxdisk list | grep t8
c1t8d0s2 auto:none - - online invalid

[Romeo Theriault]

Post by Romeo Theriault

Post by Romeo Theriault
Thank you for pointing this out. Though when I run it I get this error.
# vxdiskunsetup c4t2d0
VxVM vxdiskunsetup NOTICE V-5-2-3522 c4t2d0: Disk is not a volume

manager

Post by Romeo Theriault
disk
So I guess veritas doesn't seem to think it knows anything about the

disk in

Post by Romeo Theriault
this case. I also tried repartitioning and labeling the drive then

running

Post by Romeo Theriault
vxdclt enable but it is still showing up as auto:sliced with a status of
error. I'm leaning towards leaving it alone at this point as it doesn't

seem

Post by Romeo Theriault
to be causing any problems.

It shouldn't cause any problems, but you can likely get rid of it by
adding it back into VxVM and then unsetting it again.
# /usr/lib/vxvm/bin/vxdisksetup -i c1t8d0
# vxdisk list | grep t8
c1t8d0s2 auto:cdsdisk - - online
# /usr/lib/vxvm/bin/vxdiskunsetup c1t8d0
# vxdisk list | grep t8
c1t8d0s2 auto:none - - online invalid

Bingo! This worked perfectly.

Thank you very much. It probably wouldn't have caused a problem but I'm a
stickler for consistency.

[Sengor]

vxedit -fr rm might help