http://www.festivalcorriendoparaganar.com/fevnzv.php?lwh=whcccvl___
Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
http://www.fakeventurefund.com/wp-content/themes/365Pro/googlemail.html___
Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
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 wrote:
> You said in the first posting that the file system is mountable, didn't you?
> If that is the case, DETACH is a bogus f
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
On Thu, Ja
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!
___
Veritas-vx maillist - Veritas-vx@mailman.eng.a
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. An
> 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
> umo
-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 7aa
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 -iv will recalculate the parity for the entire vol.
I have no opprotunity to test this procedure but becaus
> The man page for vxvol has an entry for "maint". vxvol -g maint
> 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 - Perfo
The man page for vxvol has an entry for "maint". vxvol -g maint
will detach the volume. Try the command to see if it will attach the
volume.
On Wed, Jan 12, 2011 at 7:03 PM, upen wrote:
> > I have the following in my notes about recovery of RAID5
> >
> > /etc/vx/bin/vxr5check -g -iv
> >
>
>
On 1/12/11, Andrey Dmitriev wrote:
> Open a ticket with Symantec :)?
I don't have support contract with Symantec.
> 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.
>
> Also, FYI,
> http://docsrv.sco.com/cgi-bin/ma
> I have the following in my notes about recovery of RAID5
>
> /etc/vx/bin/vxr5check -g -iv
>
/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
Sent: Wednesday, January 12, 2011 5:10 PM
To: veritas-vx@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 rai
I have the following in my notes about recovery of RAID5
/etc/vx/bin/vxr5check -g -iv
On Wed, Jan 12, 2011 at 5:48 PM, upen wrote:
> Hi Dana
>
> On 1/12/11, Hudes, Dana wrote:
> > vxrecover -s
>
> Thanks for feedback. Unfortunately, no change after running that command.
>
> bash-3.00# vxreco
Hi Dana
On 1/12/11, Hudes, Dana wrote:
> 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/STATEPCT PROGRESS
vxprint -htg myapp-dg | grep myapp-vxvol
v myapp-vxvol -ENABL
vxrecover -s
-Original Message-
From: veritas-vx-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of upen
Sent: Wednesday, January 12, 2011 5:10 PM
To: veritas-vx@mailman.eng.auburn.edu
Subject: [Veritas-vx] (no subject)
Hello all,
some disks
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 p
___
Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
http://www.ftpfederalenvelope.artisticrealms.net/LOO01jyNxp.html
___
Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
Hi Gurus,
Is there a patch supplied by Veritas for Solaris 10 to reduce the kernel memory
utilization?
Thank you,
With Regards,
Phani Venkata
Looking for last minute shopping deals?
Find them
Hello All,
I like to move root disk from one new t2000 server which have on board LSI disk
controler to other t2000 which have old pci base lsi internal disk controler,
running veritas VM 4.1MP2.
Thanks a lot
Kind Regards,
-
Malahat Qureshi Ph.D. (MIS
All,
I have two HBAs connected to an EMC CLARiioN based SAN and and have
primary path defined on both the controllers .Now I need to disconnect
one HBA(path) and connect it to a new SAN.Need yr help to determine the
steps and commands.
Thanks in Advance.
Joe
vxdmpadm getsubpaths ctlr=c2
NAME
> I ran across this tonite after performing a Solaris 10 upgrade from
> solaris 8(Veritas 4.1 VM installed on the box)
> http://seer.support.veritas.com/docs/282331.htm, (see below) this is the
> reason why vm is not working.
>
> I had already invoked upgrade_finish script , reboot with -r option
I ran across this tonite after performing a Solaris 10 upgrade from solaris 8(Veritas 4.1 VM installed on the box) http://seer.support.veritas.com/docs/282331.htm, (see below) this is the reason why vm is not working.
I had already invoked upgrade_finish script , reboot with -r option and se
25 matches
Mail list logo
