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

Error Message

From

Meaning

Bitmap reconfig failed %s:%s

Kernel

A request to reconfigure the bitmap on the local host

 

 

has failed. This can happen for two reasons:

 

 

• The old bitmap cannot be read from to obtain

 

 

needed information.

 

 

• The new bitmap cannot be reserved because the

 

 

volume is not accessible or is already in use. Verify

 

 

that the new bitmap volume is accessible and is not

 

 

already in use.

bitmap <vol> is already in use by

RM

The volume requested as a bitmap for the remote

StorEdge Network Data Replicator

 

mirror set is already configured to be used by the

 

 

remote mirror software.

bitmap <vol> is in use by Instant

RM

The volume requested as a remote mirror bitmap

Image

 

volume is already configured to be a volume used by

 

 

the point-in-time copy software.

bitmap <vol> is in use by SCSI

RM

The volume requested as a remote mirror bitmap

Target Emulation

 

volume is already configured for use by STE (SCSI

 

 

Target Emulation).

Bitmap volume is already an

PITC

The volume that was specified as the bitmap volume

overflow volume

 

during an enable operation is already being used by

 

 

another set as an overflow volume.

Bitmap volume is not a character

PITC

The volume that was specified as the bitmap volume

device

 

during an enable operation is a block device and not a

 

 

character device.

bitmap volume name must start with

PITC

The volume that was specified as the bitmap volume

/dev

 

during an enable or import operation does not start

 

 

with /dev.

both <phost> and <shost> are local

RM

The set specifies the same host as both primary and

 

 

secondary. The primary and secondary hosts must be

 

 

different.

Cannot add %s:%s ==> %s:%s to group %s

Cannot change disk queue %s, Must be in logging mode

Can not check volume against mount table

Kernel

The set being added to a group cannot be added.

 

Typically, this happens because the set being added is

 

of a different type (sync or async) than the sets already

 

in the group.

Kernel

A disk queue cannot be added to or removed from a

 

set if it is not in logging mode. Place the set into

 

logging mode and then attempt to add or remove the

 

disk queue.

PITC

The iiadm operation attempted to determine whether

 

a volume on the command line belongs to a mounted

 

filesystem . The test for this has failed.

Chapter 3 Error Messages 21

Page 31
Image 31
Sun Microsystems 3.2 manual Volume requested as a bitmap for the remote, Mirror set is already configured to be used 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.