[Orca-users] Re: Orcallator on Solaris 10

[Dmitry Berezin]

Liston,

Unfortunately I don't have a Solaris 10 box yet, so I can't try this out...
However, we use EMC TimeFinder on some of our Solaris 8 servers and have no
problems with orcallator.se when volumes disappear and reappear on the
system.
You are correct about not finding RAWDISK code in the current releases of
orcallator.se - it has been removed.
>From your snippet it appears that the problem is in the diskinfo.se that
comes with SE Toolkit. It is being included in p_iostat_class.se (also comes
with SE) that is included in orcallator.se. What version of SE are you
using?
Try devfsadm -C (I believe it works the same on Solaris 10 as on 8). Also,
check for broken links in /dev/dsk.

  -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 orca at bias.org
> Sent: Tuesday, September 27, 2005 4:26 PM
> To: orca-users at orcaware.com
> Subject: [Orca-users] Re: Orcallator on Solaris 10
> 
> 
> Should have done more research before last night to list on segmentation
> error for orcallator... but here is more info now.
> 
> It looks like I did have problems in March 2005 on this server with
> orcallator getting segmentation errors.  I even wrote the list on this
> thinking it was caused by Veritas 4.1 install.  After complete erase of
> all my disk paths through reboot, it appeared to solve the issue and
> orcallator was working again.
> 
> I saw a few comments about MAX_RAWDISKS and USE_RAWDISK in the
> orcallator.se file as resolution to my issues.  There is no rawdisk
> reference in the version I have (r497 and r412) so that does not appear to
> be at issue.
> 
> Although I'm still not sure how, I am thinking that my disk paths coming
> and going is the culprit here.  We do a lot of moving around of volumes
> via snapshots and clones, so disk that appear today may not appear ever
> again.
> 
> Does anyone else do a lot of diskpath altering on their systems?  Do you
> have problems?
> 
> I did a "-d DWATCH_OS" option on the se run and got the following tail
> before is does a segmentation fault:
> 
> break;
> return sderr(STRUCTURE);
> count++;
> ld = readdir(dirp<18446744071543194240>)
> if (count<27> == GLOBAL_diskinfo_size<150>)
> dp = *((dirent_t *) ld<18446744071543217808>)
> if (dp.d_name<c3t61d91s1> == <.> || dp.d_name<c3t61d91s1> == <..>)
> if (!(dp.d_name<c3t61d91s1> =~ <s0$>))
> ld = readdir(dirp<18446744071543194240>)
> if (count<27> == GLOBAL_diskinfo_size<150>)
> dp = *((dirent_t *) ld<18446744071543217840>)
> if (dp.d_name<emcpower1a> == <.> || dp.d_name<emcpower1a> == <..>)
> if (!(dp.d_name<emcpower1a> =~ <s0$>))
> ld = readdir(dirp<18446744071543194240>)
> if (count<27> == GLOBAL_diskinfo_size<150>)
> dp = *((dirent_t *) ld<18446744071543217872>)
> if (dp.d_name<emcpower1b> == <.> || dp.d_name<emcpower1b> == <..>)
> if (!(dp.d_name<emcpower1b> =~ <s0$>))
> ld = readdir(dirp<18446744071543194240>)
> if (count<27> == GLOBAL_diskinfo_size<150>)
> dp = *((dirent_t *) ld<18446744071543217904>)
> Segmentation Fault
> 
> 
> I'm think I may need to rebuilt the paths again, but certainly would like
> to find a non-reboot option to this.
> 
> I may also alter orcallator.se to completly eliminate gathering disk info,
> since load/cpu/network/etc would be better than nothing.
> 
> Thanks,
> Liston
> _______________________________________________
> Orca-users mailing list
> Orca-users at orcaware.com
> http://www.orcaware.com/mailman/listinfo/orca-users