[Orca-users] Orca problems on Solaris 8 with SAN support

[Dmitry Berezin]

David,

 

I think the problem that you are having is caused by the orcallator.se RAW_DISK code. I think it is unnecessary complex and inefficient (where it loops through the disk information array created in diskinfo.se instead of using the search function supplied in diskinfo.se). Also, diskinfo.se has its own bugs :-(. Try commenting out USE_RAWDISK as Blair suggested.

I'm currently working on a few improvements to the orcallator.se and RAW_DISK is one of the things that I'm looking at. I will post my code to Orca-dev forum after I'm done with testing.

 

  Good luck,

 

  -Dmitry.  

 

-----Original Message-----
From: orca-users-bounces+dberezin=acs.rutgers.edu at orcaware.com [mailto:orca-users-bounces+dberezin=acs.rutgers.edu at orcaware.com] On Behalf Of David Ross
Sent: Friday, April 23, 2004 3:28 PM
To: orca-users at orcaware.com
Subject: [Orca-users] Orca problems on Solaris 8 with SAN support

 

We're trying to use Orca 0.27, with orcallator.se v1.37 on Solaris 8, using SE Toolkit 3.3.

We have it running on about 100 servers right now, no problem, except for one server we have now built with Sun's SAN Foundation Kit installed. 

 

Orcallator will not start - it segmentation faults.  Running SE Toolkit with th "-d" option shows this:

---

if (j<75> > <0>)
if (strncmp(first_name<ssd9>, short_name<md100>, first_len<4>) == <0>)
if (strcmp(RAW_disk[0].short_name[0]<s>, short_name<md100>) == <0>)
j++;
strcpy(short_name<md100>, GLOBAL_disk_info[76].short_name<(nil)>)
Segmentation Fault
---

 

The disks uses the SAN stuff look very different than they used to (world-wide names), which may be the problem.

Here is "format" output:

---

root at pf5d9:/usr/local/orca/bin <mailto:root at pf5d9:/usr/local/orca/bin> > format
Searching for disks...done

 


AVAILABLE DISK SELECTIONS:
       0. c11t60020F200000EF2D4071BF2A00073353d0 <SUN-T300-0201 cyl 58523 alt 2 hd 14 sec 128>
          /scsi_vhci/ssd at g60020f200000ef2d4071bf2a00073353
       1. c11t60020F200000EF2D40688A1A000723D8d0 <SUN-T300-0201 cyl 42136 alt 2 hd 7 sec 128>
          /scsi_vhci/ssd at g60020f200000ef2d40688a1a000723d8
       2. c11t60020F200000EF2D407189BB00011A5Ed0 <SUN-T300-0201 cyl 58523 alt 2 hd 14 sec 128>
          /scsi_vhci/ssd at g60020f200000ef2d407189bb00011a5e
       3. c11t60020F200000F5CD4073C175000D429Ed0 <SUN-T300-0201 cyl 23408 alt 2 hd 7 sec 128>
          /scsi_vhci/ssd at g60020f200000f5cd4073c175000d429e
       4. c11t60020F200000F5CD40441C8F00046208d0 <SUN-T300-0201 cyl 42136 alt 2 hd 7 sec 128>
          /scsi_vhci/ssd at g60020f200000f5cd40441c8f00046208
       5. c11t60020F200000F5CD40718FAF000EF21Cd0 <SUN-T300-0201 cyl 28090 alt 2 hd 7 sec 128>
          /scsi_vhci/ssd at g60020f200000f5cd40718faf000ef21c
       6. c11t60020F200000F5CD40718FEC000E2308d0 <SUN-T300-0201 cyl 42136 alt 2 hd 7 sec 128>
          /scsi_vhci/ssd at g60020f200000f5cd40718fec000e2308
       7. c11t60020F200000F5CD407194CB0002FE4Cd0 <SUN-T300-0201 cyl 58523 alt 2 hd 14 sec 128>
          /scsi_vhci/ssd at g60020f200000f5cd407194cb0002fe4c
       8. c11t60020F200000F5CD4071876C000AC718d0 <SUN-T300-0201 cyl 46818 alt 2 hd 14 sec 128>
          /scsi_vhci/ssd at g60020f200000f5cd4071876c000ac718
---

 

Can you help me figure this out?  I'm not sure what to do.  

Thanks!

 

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT1130884.txt
URL: </pipermail/orca-users/attachments/20040426/b016e5d2/attachment.txt>