Sun Microsystems 3.2 manual Checking Log Files, Improving Performance

Page 12

Checking Log Files

You can check the status of the point-in-time copy software by examining two system log files:

■/var/opt/SUNWesm/ds.log

The /var/opt/SUNWesm/ds.log file contains timestamped messages about the point-in-time copy software, including error messages and informational messages. For example:

Mar 05 15:56:16 scm: scmadm cache enable succeeded

Mar 05 15:56:16 ii: iiboot resume cluster tag <none>

■/var/adm/messages

The /var/adm/messages file contains timestamped messages about the point-in-time copy software, including general system error and informational messages. For example:

Mar 5 16:21:24 doubleplay pseudo: [ID 129642 kern.info] pseudo-device: ii0

Mar 5 16:21:24 doubleplay genunix: [ID 936769 kern.info] ii0 is /pseudo/ii@0

Improving Performance

If the Sun StorEdge Availability Suite software is used with a filesystem, tuning the number of SV threads might produce better performance.

When a filesystem flushes its cache, it generates many parallel write operations. The SV’s default setting of 32 threads could produce a bottleneck. You can increase the number of SV threads. The maximum number of threads allowed is 1024.

Note – Each thread consumes 32k of memory.

The sv_threads value is in the /usr/drv/conf/sv.conf file. Because the file is read when a module loads, changes to the sv_threads value do not take effect until you reboot the system.

2 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003

Page 11 Page 13
Image 12
Page 11 Page 13
Contents Sun Microsystems, Inc Please Recycle Contents Error Messages Preface Before You Read This BookUsing Unix Commands How This Book Is OrganizedShell Prompts Typographic ConventionsShell Shell superuserRelated Documentation Accessing Sun Documentation Contacting Sun Technical SupportSun Welcomes Your Comments Page Troubleshooting Checklist Check for installation errorsReboot Check the log file contentsChecking Log Files Improving PerformanceSafeguarding the Vtoc Information Page Remote Mirror Software Troubleshooting Tips Troubleshooting Log Files and Services Check the integrity of the link Check for common errorsChecking Log Files Checking That the rdc Service Is Running If the /dev/rdc Link Is Not Created Checking the Integrity of the Link Testing with ifconfig Nws822# snoop -d hme0 port rdc Correcting Common User Errors Enabled Software on Only One HostWrong Volume Set Name Specified Using the dsstat Command Incorrectly To Find the Volume Set Name Accommodating Memory RequirementsRemote Mirror Software Troubleshooting Tips Page Iiadm was expecting a number to be on the command Line. This happens when the copy parameters optionIs used but the arguments for units and delay are Contains the volumes does not match the cluster tagOverflow volume could not be attached to Specified set. Possible errorsDsweempty No overflow volume was specified Dsweinuse The overflow volume is already beingVolume requested as a bitmap for the remote Mirror set is already configured to be used byVolume requested as a remote mirror bitmap Volume is already configured to be a volume used byRemote mirror set cannot be found in the configuration Database. The set is not configured. Check the entry forErrors Primary volume has a file system mounted on itKernel Set being enabled or resumed has a secondary Volume that is already in use as a secondary volumeFor another remote mirror set. a volume cannot be Enabled as a secondary volume if it is already in use asCopy or update operation could not be initiated Possible errorsDsweempty No set was specified on the command Dsweoffline One or more volumes in the set isAn overflow volume couldn’t be initialized. Possible Dsweinuse The volume that was specified is alreadyVolume Dswersrvfail The kernel was unable to accessKernel Request to disable the disk queue is already Unsuccessfully before attempting to disable the diskIiadm command must be issued on the other Where the iiadm command was issuedDisk queue volume specified for Reconfiguration operation is already in use byRemote mirror software as a data volume or bitmap Iiadm -ecommand expected dep or indCould not enable volume. Possible errors New sets can be enabledDsweempty One of the volumes names master Dsweinuse One of the volumes master, shadowIiadm had a problem detaching the overflow volume From a set. Possible errorsDsweodependency The overflow volume is still Going from logging mode to replicating modeCould not import shadow volume. Possible errors Sets can be enabledDsweempty One of the volume names is blank. File a Dsweinuse One of the volumes is already in use byCould not join shadow volume back to the set. Possible Dsweempty a volume was missing on the commandTrying to join the volume is not in the exported state Dsweinvalbmp The bitmap volume is not bigUser attempted to enable a set using the shostsvol Set specified for the command cannot be foundCurrent configuration. Check the set to ensure that It matches one of the configured sets. Use sndradmIiadm could not get a list of overflow volumes from Kernel. Possible errorsVolume the user specified to attach to a compact Master, shadow, or bitmap volumeDisk queue replace command can also be used to Size of the secondary volume. Verify thatSecondary volume is not in an error state and can be AccessedUser attempted to perform a copy or update Volume specified as the shadow volume is alreadyUse as an attached overflow volume Use as a shadow for a different master volumeUser attempted to enable a set in which Volume was already enabled, but with a differentVolume in the remote mirror set Dswenotfound Could not find specified volumeDuring an enable operation, iiadm tried to validate Bitmap device, but could not get access to itMaster device, but could not get access to it During a reset operation, iiadm was unable to findBe determined. Verify the settings SunCluster could not find the specified disk serviceCould not find remote mirror group in configuration Could not find remote mirror set in configurationLookup of the set ID in the configuration database for Volume specified for the bitmap could not beOpened. The volume might not exist or is already Iiadm attempted to access the configuration fileOne or more volumes in a group copy or update Command failed. Possible errorsSame as Update failed meaning but for a specific During a reset, iiadm tried to updateVolumes are not all in the same cluster device group Volume vol is not being managed byIiadm detected that the master, shadow, and bitmap As required by the point-in-time copy softwareRelated Error Messages

3.2 specifications

Sun Microsystems 3.2, often referred to as SunOS 3.2, was a notable release of the Sun operating system that emerged during the rapidly evolving landscape of computer technology in the early 1980s. This operating platform was designed specifically for Sun Workstations, utilizing the robust hardware architecture developed by Sun Microsystems. The introduction of SunOS 3.2 marked a significant step forward in the development of UNIX-like operating systems optimized for entrepreneurship and scientific applications.

One of the main features of SunOS 3.2 was its adherence to the Berkeley Software Distribution (BSD) model, which allowed for advanced networking capabilities, enhanced performance, and efficient resource management. BSD's influence provided SunOS 3.2 with TCP/IP networking protocols, allowing users to connect to other devices seamlessly and manage network resources easily. This feature was crucial during a time when networking was becoming increasingly vital for organizations.

The system's support for virtual memory was another innovative characteristic. SunOS 3.2 utilized demand paging, which allowed programs to use more memory than was physically installed on their machines, significantly improving multitasking and overall system responsiveness. This capability was particularly advantageous for enterprises that relied on large-scale computations and data analysis.

SunOS 3.2 also introduced support for the Sun Window System, which meant users could utilize graphical user interfaces for interacting with applications, moving away from purely text-based command interfaces. This transition paved the way for more intuitive user experiences in the realm of computing, making powerful UNIX capabilities more accessible.

The inclusion of software utilities such as the C shell (csh) and a variety of development tools further strengthened SunOS 3.2’s position as a suitable platform for developers. The system provided robust development environments for programming in languages like C and assembly, catering to custom application requirements across different industries.

Lastly, security features were integrated into SunOS 3.2 to safeguard sensitive data and enhance system integrity. Permission settings and user authentication mechanisms were refined, allowing organizations to securely manage their computing resources.

In summary, SunOS 3.2 represented a landmark evolution in operating systems, showcasing a blend of advanced networking, memory management, graphical user interface, development tools, and security—elements that defined a generation of computing within the high-performance ecosystem of Sun Microsystems.
Top Page Image Contents