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

Error Message

From

Meaning

Disable pending on diskq %s, try

Kernel

A request to disable the disk queue is already in

again later

 

progress. Verify that the previous request has

 

 

completed successfully. If it has, this request is no

 

 

longer valid. If it has not, wait for it to complete

 

 

unsuccessfully before attempting to disable the disk

 

 

queue.

disk service, <ctag>, is active on node "<hostname>" Please re-issue the command on that node

disk service, %s, is active on node "%s"; Please re-issue the command on that node

RM

The remote mirror set being operated on is not active

 

on the current node in the cluster.

PITC

The iiadm command must be issued on the other

 

node of the cluster. The disk group that the user is

 

attempting to operate on is not active on the node

 

where the iiadm command was issued.

diskq name is longer than <MAX> characters

disk queue <diskq2> does not match <diskq1> skipping set

RM

The device specified for the disk queue volume is too

 

long for remote mirror to accept.

RM

The user tried to enable a set into a group that has a

 

disk queue, but the user specified a disk queue that

 

does not match the group’s disk queue.

diskqueue <diskq> is incompatible

RM

The user tried to enable a set into a group that has a

 

 

disk queue, but the user specified a disk queue that

 

 

does not match the group’s disk queue.

Disk queue %s is already in use

Disk queue %s operation not possible, set is in replicating mode

Disk queue does not exist for set %s:%s ==> %s:%s

disk queue <diskq> is incompatible with existing queue

disk queue <diskq> is not in disk group "<ctag>"

Disk queue operations on synchronous sets not allowed

Kernel

The volume for the disk queue being added to the set

 

or group is already in use as a data volume, bitmap

 

volume, or disk queue. Use a different volume for the

 

disk queue.

Kernel

The user attempted to perform disk queue

 

maintenance on a set while the set is replicating.

Kernel

The user attempted to perform disk queue

 

maintenance on a set that does not have a disk queue.

RM

The user tried to enable a set into a group that has a

 

disk queue, but the user specified a disk queue that

 

does not match the group’s disk queue.

RM

The user tried to enable a disk queue that does not

 

reside in the same cluster resource group in which the

 

volume and bitmap reside.

Kernel

An attempt to enable a sync set with a disk queue, or

 

to add a disk queue to a sync set, has been made. Sync

 

sets cannot have disk queues attached to them.

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

Page 36
Image 36
Sun Microsystems 3.2 Kernel Request to disable the disk queue is already, Progress. Verify that the previous request has

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.