From: Tim Bingham (binghamt@upstate.edu)
Date: Mon Aug 11 2003 - 13:44:18 EDT
Hello,
I have Veritas Volume Manager 3.5 on a 420R running Solaris 7. I'm
trying to connect two disks defined on an IBM ESS Shark through an
Emulex LP8000 HBA.
I can see the disks correctly and configure them in VM without a problem.
At boot time though, the polling of the disks takes quite a while and
Veritas VM starts before the second LUN is probed. VM declares the
second disk is missing and starts the process of moving data around
to recreate the mirrors on the lost device. Once the system is booted
to where I can login, I can issue a "vxdctl enable" and that
rediscovers the disk and I can add it back into the disk group but
it's too late.
Is there a way to discover the disks earlier in the boot process, or
a way to delay the start of VM? The volumes on the disks in question
are not part of rootdg. I tried forceloading the lpfc driver for the
HBA in /etc/system but that didn't speed up polling of the disks. I
set up persistent bindings in lpfc.conf to assign the disks to target
17, then made sure the lines
name="sd" parent="lpfc" target=17 lun=0;
name="sd" parent="lpfc" target=17 lun=1;
appeared in sd.conf. I also tried putting sleep processes in init.d
to delay the startup scripts for VM, but they delayed everything,
including the polling of the HBA, so everything happened in the same
order, just later.
Any help would be appreciated! I've been wrestling with this one for
a while and I'm starting to get crunched on time.
Thanks,
Tim
-- ooooooooooooooooooooooooooooooooooo Tim Bingham SUNY Upstate Medical University Syracuse, NY 13210 binghamt@upstate.edu _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:26:55 EDT