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

Error Message

From Meaning

Abort failed

Allocation of bitmap device %s failed

Attach failed

Bad host specified

Bad set specified

Bitmap in use

PITC iiadm could not abort a copy or update operation on 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.

DSW_ENOTFOUND: The specified set does not exist.

Kernel Remote mirror could not use the bitmap requested to enable or resume a remote mirror set. This could happen for one of these reasons:

The bitmap is not accessible. Verify that the specified bitmap volume exists and is accessible.

The volume requested for use as the bitmap is already in use. Verify that the volume is not already in use as a remote mirror data volume or bitmap volume, or as a point-in-time copy master volume, shadow volume, or bitmap volume.

PITC

The overflow volume could not be attached to the

 

specified set. Possible errors:

 

ENOMEM: The kernel module ran out of memory.

 

DSW_EEMPTY: No overflow volume was specified.

 

DSW_EINUSE: The overflow volume is already being

 

used by point-in-time copy software in a different

 

capacity (master, shadow, bitmap).

 

DSW_ENOTFOUND: The set that the user is trying to

 

attach to does not exist.

 

DSW_EALREADY: The set already has an overflow

 

volume attached.

 

DSW_EWRONGTYPE: The set is not compact-dependent.

 

DSW_ERSRVFAIL: The kernel module could not get

 

access to the overflow volume.

 

DSW_EHDRBMP: The set's bitmap could not be read.

RM

A remote mirror command was issued referring to a

 

set in abbreviated format, but a mistake was made. The

 

format did not specify the set in the format: shost:svol.

PITC

The volume that was specified as the bitmap volume

 

during an enable operation is already being used by

 

another set.

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

Page 30
Image 30
Sun Microsystems 3.2 Overflow volume could not be attached to, Specified set. Possible errors, Attach to does not exist

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.