Hi Looking at your modinfo strings, it appears you are using an unpatched version. 199 7bba8000 26920 269 1 vxdmp (VxVM 4.1z: DMP Driver) 209 7ae00000 2115c8 270 1 vxio (VxVM 4.1z I/O driver) 210 7bfdce30 13f0 271 1 vxspec (VxVM 4.1z control/status driver)
Is the problem observed with the latest patches ? (Use support.veritas.com to look up the maintenance packs) http://support.veritas.com/docs/272714 <http://support.veritas.com/docs/272714> cheers tony ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ashish madhavan Sent: 30 October 2007 02:51 To: veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] VxVM 4.1, vxconfigd issue Hi, Thanks for all the replies, I think I have got to know why this is happening with help from Mark. vxconfigd in debug mode shows that it fails after it finds a symmetrix VCM device. So I tried to exclude it from Vxvm's view by creating a /etc/vx/disks.exclude file but still it dumps on reaching this disk. Below are some outputs : 1. "vxinstall" failed, so did the installer from SF cd #vxdctl mode mode: not-running 2. #modinfo |grep vx 199 7bba8000 26920 269 1 vxdmp (VxVM 4.1z: DMP Driver) 209 7ae00000 2115c8 270 1 vxio (VxVM 4.1z I/O driver) 210 7bfdce30 13f0 271 1 vxspec (VxVM 4.1z control/status driver) 3. "vxconfigd -x 2 -k -x log -x logfile=/tmp/vxconfigd.out" In this output file I could see VX gets stuck at disk "c3t5006048ACCD1E3C0d2" which is a symmetrix VCM.It fails with "VxVM vxconfigd ERROR V-5-1-0 Bus error - core dumped" I tried to avoid VX from seeing this disk by creating a "disks.exclude". Except 15 disks I have included rest of the disks in "disks.exclude" #cat /etc/vx/disks.exclude c3t5006048ACCD1E3C0d2 c3t5006048ACCD1E3C0d317 c3t5006048ACCD1E3C0d318 c3t5006048ACCD1E3C0d319 c3t5006048ACCD1E3C0d320 c3t5006048ACCD1E3C0d321 c3t5006048ACCD1E3C0d322 c3t5006048ACCD1E3C0d323 c3t5006048ACCD1E3C0d324 c3t5006048ACCD1E3C0d325 :::: :::: c3t5006048ACCD1E3C0d1302 c3t5006048ACCD1E3C0d1303 c3t5006048ACCD1E3C0d1304 But still vxconfigd searches for all the disks and fails at "c3t5006048ACCD1E3C0d2" . Is there any way to overcome the VCM disk from being scanned by VX? Any help is appreciated. I do not have the luxury of getting a call raised with veritas :( Thanks, Ashish ________________________________ From: [EMAIL PROTECTED] To: veritas-vx@mailman.eng.auburn.edu; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [Veritas-vx] VxVM 4.1, vxconfigd issue Date: Mon, 29 Oct 2007 16:24:45 +0000 Thanks for your replies Dmitry and Mark. I had forgotten to run vxinstall. But even after I had it could not start vxconfigd.So I removed all VRTS packages did a reconfig boot and re-installed Veritas using the storage foundation 4.1 "installer" script which does the configuration and installation. Even this failed during configuration stage.... ::: Starting vxconfigd for VxVM on linbgm011 ..................................................................... Failed :::: None of the target systems can be configured because 1) its previous configuration was restored, 2) the vxconfigd daemon is not running properly, or 3) VxVM is already configured. Use the vxdctl(1M) command to configure the default disk group after the installation is completed. Press [Return] to continue: Volume Manager default disk group setup and daemon startup vxconfigd on linbgm011 is not available; installer cannot set the default disk group. As vxconfigd is not enabled on linbgm011, VxVM daemons will not be started. Is vxconfigd failing due to the large number of luns? Thanks, Ashish ________________________________ > Date: Mon, 29 Oct 2007 17:09:08 +0300 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > CC: veritas-vx@mailman.eng.auburn.edu > Subject: Re: [Veritas-vx] VxVM 4.1, vxconfigd issue > > Hello, > > Have you tried to use vxinstall to do things like creating volboot, removing > install-db, etcetera? > > ashish madhavan wrote: > > > > Hi, > > > > I have a Sun 220R to which I have assigned 1000 luns of 45 Mb (this is > > to simulation a case) from a symmetrix. Host details are - > > > > 1. SunOS 5.10 Generic_118833-36 > > 2. Veritas 4.1 > > 3. HBA = LP10000 > > > > After installing vxvm 4.1 I removed the install-db and issued a > > reconfiguration boot.After the boot VX daemons are not active. I tried > > to manually start it, but gives the below error - > > > > #vxconfigd > > V-5-1-7607 vxvm:vxconfigd: WARNING: File /etc/vx/array.info doesn't exist. > > Generating file /etc/vx/array.info. > > > > VxVM vxconfigd ERROR V-5-1-0 Bus error - core dumped > > linbgm011#vxdctl init > > vxdctl: Configuration daemon is not accessible > > > > linbgm011#ls -l /etc/vx/array.info > > /etc/vx/array.info: No such file or directory > > > > > > The only "vx" processes running are : > > #ps -ef|grep vx > > root 176 1 0 18:21:42 ? 0:00 /sbin/vxesd > > root 493 1 0 18:22:18 ? 0:03 /opt/VRTSob/bin/vxsvc > > -r /opt/VRTSob/config/Registry -e > > > > > > Am I missing something? > > > > Thanks, > > Ashish > > > > > > ------------------------------------------------------------------------ > > Search from any Web page with powerful protection. Get the FREE Windows > > Live Toolbar Today! Try it now! <http://toolbar.live.com/?mkt=en-in> > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu > > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx > > > -- > Dmitry Glushenok <[EMAIL PROTECTED]> > Jet Infosystems > Tel: +7 (495) 411 76 04 > Fax: +7 (495) 411 76 05 ________________________________ Call friends with PC-to-PC calling -- FREE Try it now! <http://get.live.com/messenger/overview> ________________________________ Check out some new online services at Windows Live Ideas-so new they haven't even been officially released yet. Try it! <http://www.msnspecials.in/windowslive/>
_______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
