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

Error Message

 

From

Meaning

cannot find SNDR

set

RM

Remote mirror set cannot be found in the configuration

<shost>:<svol> in

config

 

database. The set is not configured. Check the entry for

 

 

 

errors.

Cannot reconfig %s:%s to %s:%s, Must be in logging mode

Cannot reconfigure sync/async on members of a group

Kernel

An operation has been requested that requires the

 

remote mirror set to be in logging mode. Put the

 

remote mirror set into logging mode and then request

 

the reconfiguration.

Kernel

The user attempted to reconfigure the mode of a set

 

that is in a group. The set must be removed from the

 

group before its mode can be reconfigured.

cannot replace disk queue <diskq1> with <diskq2>

can not start reverse sync as a file system is mounted on <vol>

RM

Look at check_diskqueue(cfg, qvol, group_arg);

RM

The primary volume has a file system mounted on it.

 

Unmount the file system on the primary volume and

 

then issue the reverse sync command.

can not start sync as SNDR set <shost>:<svol> is not logging

can not use current config for bitmap reconfiguration

RM

The remote mirror set must be in logging mode on the

 

primary host before a sync can be started. If the

 

primary site is in an error state, fix the error and then

 

place the primary site into logging mode for this set.

 

Then reissue the forward sync command.

RM

A single set must be specified for bitmap operations.

 

The default configuration cannot be used for these

 

operations.

can not use current config for disk queue operations

can not use a config file for disk queue operations

can not use current config for enable command

Can't export a mounted volume

RM

An individual set or group must be specified when

 

issuing disk queue operations. A single disk queue

 

operation cannot operate on all sets configured or all

 

sets in a file.

RM

A set must be specified when issuing an enable

 

command. An enable command cannot operate on the

 

default configuration.

PITC

A volume cannot belong to a mounted file system

 

before it is exported.

Can't

get memory for list enquiry

PITC

iiadm ran out of memory.

Can't

open sort program

PITC

The iiadm operation is attempting to sort output

 

 

 

before displaying it but cannot find the sort utility

 

 

 

(typically found in /usr/bin/sort).

 

 

 

 

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

Page 32
Image 32
Sun Microsystems 3.2 Remote mirror set cannot be found in the configuration, Errors, Then issue the reverse sync command

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.