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 -
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
-bash-3.00# modinfo | grep vx
25 1330ab0 3e4e0 297 1 vxdmp (VxVM 5.0MP3: DMP Driver)
27 7be0 209248 298 1 vxio (VxVM 5.0MP3 I/O driver)
29 7bfe90f0c78 299 1 vxspec (VxVM 5.0MP3 control/status driv)
213 7bbf30a0cb0 295 1 vxportal (VxFS 5.0_REV-5.0MP3A25_sol port)
214
Greetings,
I believe I should have sent this to the veritas-vx group instead.
We are running Vertias FS 5.0 MP3 on our systems, and utilize FlashSnap on some
of them. We take a snap of our production data and mount it to our backup
server and perform a local backup there. We are looking into
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
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
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!
On 1/13/11, William Havey bbha...@gmail.com wrote:
You said in the first posting that the file system is mountable, didn't you?
If that is the case,
