Discussion:
[Veritas-vx] (no subject)
upen
2011-01-12 22:10:13 UTC
Permalink
Hello all,

some disks lost contact with solaris 10 system but the disks came back
online on their own. I used "vxreattach disk" to attach them to dg and
started raid 5 volume.

Voulme's kstate is Enabled however state is DETACH. It bothers me a lot.

In this state also I can mount the volume and perform rw operations on
the mounted volume.

How can I take care of DETACH STATE for this volume ?

vxprint -htr
Disk group: myapp-dg

DG NAME NCONFIG NLOG MINORS GROUP-ID
ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
CO NAME CACHEVOL KSTATE STATE
VT NAME RVG KSTATE STATE NVOLUME
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
EX NAME ASSOC VC PERMS MODE STATE
SR NAME KSTATE

dg myapp-dg default default 95000 1267475668.79.server

dm myapp-dg01 c1t2d0s2 auto 65536 143283520 SPARE
dm myapp-dg02 c1t3d0s2 auto 65536 143283520 -
dm myapp-dg03 c2t0d0s2 auto 65536 71061376 -
dm myapp-dg04 c2t1d0s2 auto 65536 71061376 -
dm myapp-dg05 c2t2d0s2 auto 65536 71061376 -
dm myapp-dg06 c2t8d0s2 auto 65536 71061376 -
dm myapp-dg07 c2t9d0s2 auto 65536 71061376 -
dm myapp-dg08 c2t10d0s2 auto 65536 71061376 -

v myapp-vxvol - ENABLED DETACH 355305600 RAID - raid5
pl myapp-vxvol-01 myapp-vxvol ENABLED ACTIVE 355305600 RAID 6/32 RW
sd myapp-dg02-01 myapp-vxvol-01 myapp-dg02 0 71061120 0/0 c1t3d0 ENA
sd myapp-dg03-01 myapp-vxvol-01 myapp-dg03 0 71061120 1/0 c2t0d0 ENA
sd myapp-dg04-01 myapp-vxvol-01 myapp-dg04 0 71061120 2/0 c2t1d0 ENA
sd myapp-dg05-01 myapp-vxvol-01 myapp-dg05 0 71061120 3/0 c2t2d0 ENA
sd myapp-dg06-01 myapp-vxvol-01 myapp-dg06 0 71061120 4/0 c2t8d0 ENA
sd myapp-dg07-01 myapp-vxvol-01 myapp-dg07 0 71061120 5/0 c2t9d0 ENA
pl myapp-vxvol-03 myapp-vxvol ENABLED LOG 5760 CONCAT - RW
sd myapp-dg08-UR-001 myapp-vxvol-03 myapp-dg08 0 5760 0 c2t10d0 ENA

Can someone throw some light on this issue?

Thanks,
A
Hudes, Dana
2011-01-12 22:44:42 UTC
Permalink
vxrecover -s

-----Original Message-----
From: veritas-vx-***@mailman.eng.auburn.edu [mailto:veritas-vx-***@mailman.eng.auburn.edu] On Behalf Of upen
Sent: Wednesday, January 12, 2011 5:10 PM
To: veritas-***@mailman.eng.auburn.edu
Subject: [Veritas-vx] (no subject)

Hello all,

some disks lost contact with solaris 10 system but the disks came back
online on their own. I used "vxreattach disk" to attach them to dg and
started raid 5 volume.

Voulme's kstate is Enabled however state is DETACH. It bothers me a lot.

In this state also I can mount the volume and perform rw operations on
the mounted volume.

How can I take care of DETACH STATE for this volume ?

vxprint -htr
Disk group: myapp-dg

DG NAME NCONFIG NLOG MINORS GROUP-ID
ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
CO NAME CACHEVOL KSTATE STATE
VT NAME RVG KSTATE STATE NVOLUME
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
EX NAME ASSOC VC PERMS MODE STATE
SR NAME KSTATE

dg myapp-dg default default 95000 1267475668.79.server

dm myapp-dg01 c1t2d0s2 auto 65536 143283520 SPARE
dm myapp-dg02 c1t3d0s2 auto 65536 143283520 -
dm myapp-dg03 c2t0d0s2 auto 65536 71061376 -
dm myapp-dg04 c2t1d0s2 auto 65536 71061376 -
dm myapp-dg05 c2t2d0s2 auto 65536 71061376 -
dm myapp-dg06 c2t8d0s2 auto 65536 71061376 -
dm myapp-dg07 c2t9d0s2 auto 65536 71061376 -
dm myapp-dg08 c2t10d0s2 auto 65536 71061376 -

v myapp-vxvol - ENABLED DETACH 355305600 RAID - raid5
pl myapp-vxvol-01 myapp-vxvol ENABLED ACTIVE 355305600 RAID 6/32 RW
sd myapp-dg02-01 myapp-vxvol-01 myapp-dg02 0 71061120 0/0 c1t3d0 ENA
sd myapp-dg03-01 myapp-vxvol-01 myapp-dg03 0 71061120 1/0 c2t0d0 ENA
sd myapp-dg04-01 myapp-vxvol-01 myapp-dg04 0 71061120 2/0 c2t1d0 ENA
sd myapp-dg05-01 myapp-vxvol-01 myapp-dg05 0 71061120 3/0 c2t2d0 ENA
sd myapp-dg06-01 myapp-vxvol-01 myapp-dg06 0 71061120 4/0 c2t8d0 ENA
sd myapp-dg07-01 myapp-vxvol-01 myapp-dg07 0 71061120 5/0 c2t9d0 ENA
pl myapp-vxvol-03 myapp-vxvol ENABLED LOG 5760 CONCAT - RW
sd myapp-dg08-UR-001 myapp-vxvol-03 myapp-dg08 0 5760 0 c2t10d0 ENA

Can someone throw some light on this issue?

Thanks,
A
_______________________________________________
Veritas-vx maillist - Veritas-***@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
upen
2011-01-12 22:48:27 UTC
Permalink
Hi Dana
Post by Hudes, Dana
vxrecover -s
Thanks for feedback. Unfortunately, no change after running that command.

bash-3.00# vxrecover -s

-bash-3.00# vxtask list
TASKID PTID TYPE/STATE PCT PROGRESS


vxprint -htg myapp-dg | grep myapp-vxvol
v myapp-vxvol - ENABLED DETACH 355305600 RAID - raid5
....

Thanks,
A
--
upen,
emerge -uD life (Upgrade Life with dependencies)
William Havey
2011-01-12 23:01:56 UTC
Permalink
I have the following in my notes about recovery of RAID5

/etc/vx/bin/vxr5check -g <dg> -iv <volume>
Post by upen
Hi Dana
Post by Hudes, Dana
vxrecover -s
Thanks for feedback. Unfortunately, no change after running that command.
bash-3.00# vxrecover -s
-bash-3.00# vxtask list
TASKID PTID TYPE/STATE PCT PROGRESS
vxprint -htg myapp-dg | grep myapp-vxvol
v myapp-vxvol - ENABLED DETACH 355305600 RAID -
raid5
....
Thanks,
A
--
upen,
emerge -uD life (Upgrade Life with dependencies)
_______________________________________________
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
--
William (Bill) Havey
Symantec HA Professional
917 515-3385
upen
2011-01-13 00:03:40 UTC
Permalink
Post by William Havey
I have the following in my notes about recovery of RAID5
/etc/vx/bin/vxr5check -g <dg> -iv <volume>
/etc/vx/bin/vxr5check -g myapp-dg myapp-vxvol
VxVM vxr5check INFO V-5-2-1451 verification in process... passed

Thanks William but the o/p is still DETACH for Volume
William Havey
2011-01-13 02:46:23 UTC
Permalink
The man page for vxvol has an entry for "maint". vxvol -g <dg> maint <vol>
will detach the volume. Try the command to see if it will attach the
volume.
Post by upen
Post by William Havey
I have the following in my notes about recovery of RAID5
/etc/vx/bin/vxr5check -g <dg> -iv <volume>
/etc/vx/bin/vxr5check -g myapp-dg myapp-vxvol
VxVM vxr5check INFO V-5-2-1451 verification in process... passed
Thanks William but the o/p is still DETACH for Volume
--
William (Bill) Havey
Symantec HA Professional
917 515-3385
upen
2011-01-13 14:25:22 UTC
Permalink
Post by William Havey
The man page for vxvol has an entry for "maint". vxvol -g <dg> maint <vol>
will detach the volume. Try the command to see if it will attach the
Thanks for support, William.

I wonder if it is this is the version issue?

vxvol -g myapp-dg maint myapp-vxvol
VxVM vxvol INFO V-5-1-9632
raid5/vxvol - Perform raid5 usage type volume operations


Usage: raid5/vxvol [-o useopt] [-ZVq] keyword arg ...
Recognized keywords:
init what vol object ...
set var=value ... vol ...
start vol ...
stop vol ...
resync vol ...
recover vol [subdisk]


Thanks
William Havey
2011-01-13 15:02:50 UTC
Permalink
A version issue very well may be involved. Have you said what version of
VxVM you've got running?

Because it is RAID5, perhaps the parity needs to be recalculated.
/etc/vx/bin/vxr5check
-g <dg> -iv <vol> will recalculate the parity for the entire vol.
I have no opprotunity to test this procedure but because it is in my notes,
at one time I must have done these steps. "Stopping" and fixing "empty" are
setting flags and are not destructive.



umount <vol>

vxvol -g dg stop vol

vxmend -g dg fix empty vol

vxvol -g dg start vol

/etc/vx/bin/vxr5check -g dg -iv vol
Post by upen
Post by William Havey
The man page for vxvol has an entry for "maint". vxvol -g <dg> maint
<vol>
Post by William Havey
will detach the volume. Try the command to see if it will attach the
Thanks for support, William.
I wonder if it is this is the version issue?
vxvol -g myapp-dg maint myapp-vxvol
VxVM vxvol INFO V-5-1-9632
raid5/vxvol - Perform raid5 usage type volume operations
Usage: raid5/vxvol [-o useopt] [-ZVq] keyword arg ...
init what vol object ...
set var=value ... vol ...
start vol ...
stop vol ...
resync vol ...
recover vol [subdisk]
Thanks
--
William (Bill) Havey
Symantec HA Professional
917 515-3385
upen
2011-01-13 15:39:10 UTC
Permalink
Post by William Havey
A version issue very well may be involved. Have you said what version of
VxVM you've got running?
Sorry, No. Here it is,

pkginfo -l VRTSvxfs VRTSvxmsa VRTSvxvm | grep VERSION
VERSION: 5.0,REV=5.0A55_sol
VERSION: 4.4-REV=build010_2006.03.02
VERSION: 5.0,REV=05.11.2006.17.55
Post by William Havey
umount <vol>
vxvol -g dg stop vol
vxmend -g dg fix empty vol
vxvol -g dg start vol
/etc/vx/bin/vxr5check -g dg -iv vol
-bash-3.00# vxvol -g myapp-dg stop myapp-vxvol
-bash-3.00# vxmend -g myapp-dg fix empty myapp-vxvol
-bash-3.00# vxvol -g myapp-dg start myapp-vxvol <--- This one
hasn't finished yet


vxtask list :
William Havey
2011-01-13 17:50:14 UTC
Permalink
Notice on the last line of the output of vxtask list the "RESYNC". The
parity is being calc'ed so the command to recalc paarity will not need to be
entered.

vxtask -l list will estimate the remaining time for the operation.

Also, I believe the volume can be mounted before the resync completes. Any
writes will slow done both I/O and Resync, so if you interested in
performance be patient.
Post by upen
Post by William Havey
A version issue very well may be involved. Have you said what version of
VxVM you've got running?
Sorry, No. Here it is,
pkginfo -l VRTSvxfs VRTSvxmsa VRTSvxvm | grep VERSION
VERSION: 5.0,REV=5.0A55_sol
VERSION: 4.4-REV=build010_2006.03.02
VERSION: 5.0,REV=05.11.2006.17.55
Post by William Havey
umount <vol>
vxvol -g dg stop vol
vxmend -g dg fix empty vol
vxvol -g dg start vol
/etc/vx/bin/vxr5check -g dg -iv vol
-bash-3.00# vxvol -g myapp-dg stop myapp-vxvol
-bash-3.00# vxmend -g myapp-dg fix empty myapp-vxvol
-bash-3.00# vxvol -g myapp-dg start myapp-vxvol <--- This one
hasn't finished yet
upen
2011-01-13 18:57:02 UTC
Permalink
Hi William,

RESYNC task got completed successfully however volume STATE was still
DETACH. I noticed you reply late and ran command to recalc parity once
RESYNC was over . It 's still running..

Thanks!
William Havey
2011-01-13 19:23:03 UTC
Permalink
You said in the first posting that the file system is mountable, didn't you?
If that is the case, DETACH is a bogus flag. To change it to ACTIVE requires
dumping configdb (vxconfigbackup), editing that file, then vxconfigrestore
to read the modified configdb back into the private region
Post by upen
Hi William,
RESYNC task got completed successfully however volume STATE was still
DETACH. I noticed you reply late and ran command to recalc parity once
RESYNC was over . It 's still running..
Thanks!
--
William (Bill) Havey
Symantec HA Professional
917 515-3385
upen
2011-01-13 20:25:18 UTC
Permalink
Ok, thanks for clarification. That'll help. I wouldn't worry about it
much now. Thanks for being patient with me and all the help!

Good day!
Post by William Havey
You said in the first posting that the file system is mountable, didn't you?
If that is the case, DETACH is a bogus flag. To change it to ACTIVE requires
dumping configdb (vxconfigbackup), editing that file, then vxconfigrestore
to read the modified configdb back into the private region
Post by upen
Hi William,
RESYNC task got completed successfully however volume STATE was still
DETACH. I noticed you reply late and ran command to recalc parity once
RESYNC was over . It 's still running..
Thanks!
--
William (Bill) Havey
Symantec HA Professional
917 515-3385
--
upen,
emerge -uD life (Upgrade Life with dependencies)
upen
2011-01-13 15:28:56 UTC
Permalink
-bash-3.00# modinfo | grep vx
25 1330ab0 3e4e0 297 1 vxdmp (VxVM 5.0MP3: DMP Driver)
27 7be00000 209248 298 1 vxio (VxVM 5.0MP3 I/O driver)
29 7bfe90f0 c78 299 1 vxspec (VxVM 5.0MP3 control/status driv)
213 7bbf30a0 cb0 295 1 vxportal (VxFS 5.0_REV-5.0MP3A25_sol port)
214 7aa00000 1d89e0 21 1 vxfs (VxFS 5.0_REV-5.0MP3A25_sol SunO)

-bash-3.00# vxvol -H
VxVM vxvol INFO V-5-1-9632
vxvol - Perform Volume Manager volume operations


Usage: vxvol [-g diskgroup] [-U usetype] [-f] [-o useopt] [-t
tasktag] [-Vq] keyword arg ...
Recognized keywords:
init what vol object ...
rdpol policy vol [plex]
set var=value ... vol ...
startall
stopall
start vol ...
stop vol ...
resync vol ...
recover vol [sd ...]
maint vol ...
noderecover vol ...
[-c ch_addopt] [-r rvg] assoc rvg|vset vol [primary_datavol] [index]
[-r rvg] aslog rvg vol
[-c ch_rmopt] dis vol [vset]
snapsync vol
Andrey Dmitriev
2011-01-12 23:13:38 UTC
Permalink
Open a ticket with Symantec :)?

Try vxvol start myapp-vxvol

Also, FYI,
http://docsrv.sco.com/cgi-bin/man/man?vxvol+1M

Andrey Dmitriev
Mentora Group


-----Original Message-----
From: veritas-vx-***@mailman.eng.auburn.edu [mailto:veritas-vx-***@mailman.eng.auburn.edu] On Behalf Of upen
Sent: Wednesday, January 12, 2011 5:10 PM
To: veritas-***@mailman.eng.auburn.edu
Subject: [Veritas-vx] (no subject)

Hello all,

some disks lost contact with solaris 10 system but the disks came back
online on their own. I used "vxreattach disk" to attach them to dg and
started raid 5 volume.

Voulme's kstate is Enabled however state is DETACH. It bothers me a lot.

In this state also I can mount the volume and perform rw operations on
the mounted volume.

How can I take care of DETACH STATE for this volume ?

vxprint -htr
Disk group: myapp-dg

DG NAME NCONFIG NLOG MINORS GROUP-ID
ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
CO NAME CACHEVOL KSTATE STATE
VT NAME RVG KSTATE STATE NVOLUME
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
EX NAME ASSOC VC PERMS MODE STATE
SR NAME KSTATE

dg myapp-dg default default 95000 1267475668.79.server

dm myapp-dg01 c1t2d0s2 auto 65536 143283520 SPARE
dm myapp-dg02 c1t3d0s2 auto 65536 143283520 -
dm myapp-dg03 c2t0d0s2 auto 65536 71061376 -
dm myapp-dg04 c2t1d0s2 auto 65536 71061376 -
dm myapp-dg05 c2t2d0s2 auto 65536 71061376 -
dm myapp-dg06 c2t8d0s2 auto 65536 71061376 -
dm myapp-dg07 c2t9d0s2 auto 65536 71061376 -
dm myapp-dg08 c2t10d0s2 auto 65536 71061376 -

v myapp-vxvol - ENABLED DETACH 355305600 RAID - raid5
pl myapp-vxvol-01 myapp-vxvol ENABLED ACTIVE 355305600 RAID 6/32 RW
sd myapp-dg02-01 myapp-vxvol-01 myapp-dg02 0 71061120 0/0 c1t3d0 ENA
sd myapp-dg03-01 myapp-vxvol-01 myapp-dg03 0 71061120 1/0 c2t0d0 ENA
sd myapp-dg04-01 myapp-vxvol-01 myapp-dg04 0 71061120 2/0 c2t1d0 ENA
sd myapp-dg05-01 myapp-vxvol-01 myapp-dg05 0 71061120 3/0 c2t2d0 ENA
sd myapp-dg06-01 myapp-vxvol-01 myapp-dg06 0 71061120 4/0 c2t8d0 ENA
sd myapp-dg07-01 myapp-vxvol-01 myapp-dg07 0 71061120 5/0 c2t9d0 ENA
pl myapp-vxvol-03 myapp-vxvol ENABLED LOG 5760 CONCAT - RW
sd myapp-dg08-UR-001 myapp-vxvol-03 myapp-dg08 0 5760 0 c2t10d0 ENA

Can someone throw some light on this issue?

Thanks,
A
_______________________________________________
Veritas-vx maillist - Veritas-***@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
upen
2011-01-13 00:08:23 UTC
Permalink
Post by Andrey Dmitriev
Open a ticket with Symantec :)?
I don't have support contract with Symantec.
Post by Andrey Dmitriev
Try vxvol start myapp-vxvol
That's already done, that's why KSTATE is ENABLED and I can mount the
volume as well with RW access.
Post by Andrey Dmitriev
Also, FYI,
http://docsrv.sco.com/cgi-bin/man/man?vxvol+1M
Yes I have taken look at many documents like this. I have tried
stopping and starting the volume again. Didn't help. I wonder if
putting volume in maint state and starting again will help. But not
sure how that will have to be done.

Thank you for continuing to help me.
Continue reading on narkive:
Loading...