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

Error Message

From

Meaning

SNDR set does not have a disk

RM

Set does not have a disk queue attached when

queue

 

attempting either a queue remove operation or a queue

 

 

replace operation.

SNDR: The volume ’<vol2>’ has been configured previously as ’<vol1>’. Re-enter command with the latter name.

SNDR: ’<vol1>’ and ’<vol2>’ refer to the same device

Stat failed

SV-disable failed

RM

The user attempted to enable a set in which the

 

volume was already enabled, but with a different

 

name.

RM

A physical device cannot be used for more than one

 

volume in the remote mirror set.

PITC

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 volume name was specified

 

DSW_ENOTFOUND: Could not find specified volume in

 

kernel.

PITC

iiadm tried to perform svadm -don a volume. See

 

the ds.log file for more information.

SV-enable failed

PITC

iiadm tried to perform svadm -eon a volume. See

 

 

the ds.log file for more information.

Target of copy/update is mounted, unmount it first

The bitmap %s is already in use

The remote state of %s:%s ==> %s:%s prevents this operation

The state of %s:%s ==> %s:%s prevents this operation

PITC

If the shadow in a master-to-shadow copy or update

 

operation or the master in a shadow-to-master copy or

 

update operation is mounted, it cannot be copied to.

Kernel

The bitmap requested for the remote mirror set being

 

enabled is already in use as a bitmap for another set.

 

Enable the set and specify a different volume for the

 

bitmap.

Kernel

The user attempted to do a sync or reverse sync while

 

the secondary volume is mounted. First unmount the

 

secondary volume and then issue the sync or reverse

 

sync request.

Kernel

The set the user is attempting to sync is part of an

 

advanced configuration. The state of one of the other

 

sets in the configuration prevents this sync from

 

occurring for one of the following reasons:

 

• Another set in a one-to-many configuration is

 

currently doing a reverse sync.

 

• A reverse sync is being requested for a set in a one-

 

to-many configuration and at least one of the other

 

sets is not in logging mode.

 

• A set is already syncing.

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

Page 46
Image 46
Sun Microsystems 3.2 Set does not have a disk queue attached when, Attempting either a queue remove operation or a queue

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.