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

Error Message

 

 

 

From

Meaning

disk queue volume

<vol>

must

not

RM

The disk queue volume specified for the

match any primary

SNDR

volume

or

 

reconfiguration operation is already in use by the

bitmap

 

 

 

 

remote mirror software as a data volume or bitmap

 

 

 

 

 

volume.

don't understand shadow type

DSWIOC_LISTLEN

Dual copy failed, offset:%s

Duplicate volume specified

PITC

The iiadm -ecommand expected dep or ind.

PITC iiadm tried to get a count of the number of sets recognized by the kernel, but failed. This is a bug in

iiadm.

Kernel A sync or reverse sync was started but could not complete, for one of the following reasons:.

The user issued a logging request manually, causing the sync or reverse sync to abort.

The network link between the primary and the secondary host failed, causing the sync or reverse sync to stop.

The primary or secondary volume encountered an error and the remote mirror software was unable to read or write to the volume.

In a Sun Cluster environment, a failover of the resource group might have been issued, causing the sync ot reverse sync to be stopped.

PITC

A command that can take multiple shadow volume

 

names (like update or copy) detected that a shadow

 

volume was specified more than once.

either

<phost>:<pfile>

or

RM

The command was issued on a system that is not the

<shost>:<sfile>

is

not

local

 

primary or secondary host for the specified set. Verify

 

 

 

 

 

 

the command is being issued on the proper system.

either

<phost>:<pvol>

or

 

 

<shost>:<svol>

is

not

local

 

 

Empty

string

 

 

 

Kernel

An enable or resume request for a remote mirror set

 

 

 

 

 

 

was issued but a required field was not filled in when

the request was received in the kernel. This is not something the user can control.

Chapter 3 Error Messages 27

Page 37
Image 37
Sun Microsystems 3.2 manual Disk queue volume specified for, Reconfiguration operation is already in use by

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.