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

Error Message

From Meaning

Create overflow failed

ctag "<ctag2>" is does not match disk group name "<ctag1>" of volume <vol>

ctags <ctag1> and <ctag2> do not match

PITC

An overflow volume couldn’t be initialized. 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 overflow volume was specified.

 

DSW_EINUSE: The volume that was specified is already

 

being used by the point-in-time copy software in

 

another capacity.

 

DSW_EIO: The kernel was unable to write to the

 

volume.

 

DSW_ERSRVFAIL: The kernel was unable to access the

 

volume.

RM

The cluster resource tag given for a set is different from

 

the configured cluster resource tag.

RM

The set specified contains both the syntax ‘-C

 

ctag1’ and ’... C ctag2’. This error indicates the

 

values specifed for ctag1 and ctag2 do not match.

device name is longer than <MAX>

RM

The name for the primary data volume, primary

characters

 

bitmap volume, secondary data volume, or secondary

 

 

bitmap volume is too long for the remote mirror

 

 

software.

Disable failed

PITC

iiadm was unable to disable one or more sets. 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.

 

 

DSW_ENOTFOUND: The specified set could not be found

 

 

in the kernel.

 

 

DSW_EDEPENDENCY: An attempt was made to disable

 

 

an independent set, but the set is not yet independent.

 

 

DSW_EOPACKAGE: Another package (for example:

 

 

RDC) told the point-in-time copy software not to

 

 

disable the set.

 

 

DSW_ERSRVFAIL: The kernel could not access the

 

 

shadow or bitmap volumes.

 

 

 

Chapter 3 Error Messages 25

Page 35
Image 35
Sun Microsystems 3.2 An overflow volume couldn’t be initialized. Possible, Being used by the point-in-time copy software

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.