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

Error Message

From

Meaning

Overflow list access failure

PITC

iiadm could not get a list of overflow volumes from

 

 

the kernel. Possible errors:

 

 

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

 

 

bound. File a bug against iiadm.

 

 

ENOMEM: The kernel module ran out of memory.

Overflow volume is already in an

PITC

During an attach operation, iiadm determined that the

InstantImage group

 

volume the user specified to attach to a compact

 

 

dependent set is already in use by another set as a

 

 

master, shadow, or bitmap volume.

overflow volume name must start

PITC

The overflow volume must exist in the /dev directory

with /dev

 

tree

Overflow volume not in a disk group

PITC

The user attempted to attach a volume to a set, but the

 

 

set's volumes are part of a cluster device group and the

 

 

overflow volume is not.

Overflow volume not in same disk

PITC

The user attempted to attach a volume to a set, but the

group as shadow set members

 

set's volumes are in a different cluster device group

 

 

than the overflow volume.

Recovery bitmaps not allocated

Request not serviced, %s is currently being synced.

Reset shadow failed

Kernel

A full copy, update, sync, or reverse sync operation has

 

been requested but the bitmap on the primary host

 

cannot be accessed. Verify that the bitmap volume is a

 

valid volume and is not in an error state.

Kernel

The user attempted to sync the remote mirror set, or

 

put the remote mirror set into logging mode, while a

 

previous sync request is being set up. If the user issued

 

a second sync request, the user must first put the

 

remote mirror set into logging mode and then issue the

 

sync. If the user issued a logging request, the user

 

must first wait for the sync request to finish setting up

 

and then issue the logging request. This stops the sync

 

and places the remote mirror set into logging mode.

PITC

iiadm could not reset the 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 reset.

 

DSW_ENOTFOUND: The specified set could not be found

 

in the kernel.

 

EINVAL: Bitmap volume is invalid.

 

DSW_ERSRVFAIL: The kernel could not access one of

 

the volumes.

 

DSW_EHDRBMP: Could not set up bitmap header.

Chapter 3 Error Messages 33

Page 43
Image 43
Sun Microsystems 3.2 Iiadm could not get a list of overflow volumes from, Kernel. Possible errors, Overflow volume is not

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.