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

Error Message

From Meaning

Failed to detach overflow volume

Failed to move group in kernel

failed to update autosync for SNDR set <shost>:<svol>

<file> contains no matching SNDR sets

found matching ndr_ii entry for <vol>

Group config does not match kernel

PITC

iiadm had a problem detaching the overflow volume

 

from a set. 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.

 

DSW_EEMPTY: No set was specified to detach from.

 

DSW_ENOTFOUND: The set to detach from does not

 

exist.

 

DSW_EODEPENDENCY: The overflow volume is still in

 

use by the set that the user attempted to detach it from.

 

DSW_ERSRVFAIL: Could not access the bitmap header

 

to record the overflow detach.

 

DSW_EHDRBMP: Could write the bitmap header to

 

record the overflow detach.

PITC

Could not move the set from one group to another.

 

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.

 

DSW_EEMPTY: iiadm failed to fill in the group name.

 

This is a bug.

RM

Autosync could not be activated for the set when

 

going from logging mode to replicating mode.

RM

The configuration file specified with the -fswitch

 

contains no valid remote mirror sets.

RM

There is already an ndr_ii entry for this remote

 

mirror set.

PITC

The groups in dscfg are different from the groups in

 

the kernel.

Group does not exist or has no members

Group list access failure

group name is longer than <MAX> characters

hostname is longer than <MAX> characters

PITC

An invalid group was specified for a group-based

 

command. For example: copy, update, and abort

PITC

Could not retrieve the list of sets belonging to a group

 

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 group name specified is too long for the remote

 

mirror software to accept.

RM

The host name specified is too long for the remote

 

mirror software.

Chapter 3 Error Messages 29

Page 39
Image 39
Sun Microsystems 3.2 Iiadm had a problem detaching the overflow volume, From a set. Possible errors, Exist, This is a bug

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.