TABLE 3-1Error Messages for the Sun StorEdge Availability Suite 3.2 Software (Continued)

Error Message

 

 

From

Meaning

Cannot enable %s:%s ==> %s:%s,

Kernel

A set being enabled or resumed has a secondary

secondary in

use in

another set

 

volume that is already in use as a secondary volume

 

 

 

 

 

for another remote mirror set. A volume cannot be

 

 

 

 

 

enabled as a secondary volume if it is already in use as

 

 

 

 

 

a secondary volume by another remote mirror set.

Cannot

enable

master

volume

PITC

iiadm attempted to put the master volume under SV

 

 

 

 

 

control during an enable operation, but failed.

Cannot

enable

shadow

volume

PITC

iiadm attempted to put the shadow volume under SV

 

 

 

 

 

control during an enable operation, but failed.

Cannot reverse sync %s:%s <== %s:%s, set is in queuing mode

Change request denied, don’t understand request version

Change request denied, volume mirror is up

changing queue parameters may only be done on a primary SNDR host

Cluster list access failure

cluster name is longer than <MAX> characters

config error: neither <host1> nor <host2> is localhost

Kernel

A reverse sync has been requested on a set that is in

 

queuing mode. Put the set into logging mode and then

 

the issue the reverse sync command for the set.

Kernel

A request was sent from one remote mirror host to the

 

other, and the version of the software was not

 

understood by the receiving host. Verify that both

 

hosts are running compatible versions of the remote

 

mirror software.

Kernel

The user asked to sync a remote mirror set, and the

 

secondary host has refused the sync event.

RM

The queue parameters for the async I/O queue, both

 

memory-based and disk-based, can be changed only

 

on the primary host.

PITC

iiadm was unable to retrieve a list of cluster groups

 

from the kernel. Possible errors:

 

EFAULT: The kernel module tried to read out-of-

 

bounds. File a bug against iiadm

 

ENOMEM: The kernel module ran out of memory.

RM

The cluster resource tag is too long for the remote

 

mirror software to accept.

RM

The current host is neither the primary nor secondary

 

host for the remote mirror set. Verify that the hostname

 

of the system has not been changed since the remote

 

mirror set was enabled.

Chapter 3 Error Messages 23

Page 33
Image 33
Sun Microsystems 3.2 Kernel Set being enabled or resumed has a secondary, Secondary volume by another remote mirror set

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.