Storage Resource Manager Enterprise Edition Installation Guide

C–26 Storage Resource Manager Enterprise Edition
SRM Troubleshooting Guide
The number of concurrent scans can be adjusted in the agentconfig file with directive
“MAX_CONC_FILE_SCANS.”
Why aren’t CD-ROMs or Mounted NFS Partitions Scanned?
The SRM Unix agent only scans local, “standard” file systems. In both these cases, it
might be useful to display that the partitions are available, but it does not make sense
to scan their files (especially on NFS, it could cause network performance problems).
Why is the “/tmp” File System Not Scanned on My Solaris
System?
The SRM Unix agent only scans local, “standard” file systems. The “/tmp” partition
on Solaris is a special beast (which is associated with swap space), and does not
occupy disk in the same way UFS or VxFS file systems do. The entire “/tmp” partition
goes away on each system boot. (“/tmp” is a standard partition on other support UNIX
flavors.)
“srmagent/tcp: Unknown Service”
This occurs when NIS (previously known as YP, or “Yellow Pages”) is used to resolve
service names. Note that /etc/inetd.conf contains a service name (not a port) which
must be resolved. The SRM/UNIX installation assumes the name can be resolved by
consulting the /etc/services file. There have been situations, notably on HP-UX when
even though /etc/services is updated, it is not consulted.
The workaround for this is to put the SRM port (default 11125) into the NIS database.
“/usr/sbin/diskinfo -v /dev/rdsk/c4t1d0 Failed.”
This is not really an error; it occurs when a trace file is created because TRACESEV
has a values of “ANY,” “MED,” or “LOW.” The agent is tracing the fact that a disk
shows up in the /dev/rdsk directory, but is apparently not configured.
“semget ret=-1 for key 109d #sems=1 flag=25b6 errno=2 No
Such File or Directory.”
This is not really an error; it occurs when a trace file is created for another reason. It is
specific to handling of semaphores (to enforce MAX_CONC_FILE_SCANS) on AIX
4.1.