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

Error Message

From

Meaning

Reverse sync needed, cannot sync

Kernel

The user requested a forward sync operation for a

%s:%s

==>

%s:%s

 

remote mirror set which needs a reverse sync. This

 

 

 

 

occurs when a previous reverse sync does not

 

 

 

 

complete successfully or because the primary volume

 

 

 

 

was damaged and had to be replaced. Issue a reverse

 

 

 

 

sync for the set.

%s:%s ==> %s:%s already has a disk

Kernel

A set cannot contain more than one disk queue. To add

queue

attached

 

a new disk queue, remove the old disk queue first. The

 

 

 

 

disk queue replace command can also be used to

 

 

 

 

accomplish this task.

%s:%s

has

invalid size

Kernel

The remote mirror software could not determine the

(%s)..cannot proceed

 

size of the secondary volume. Verify that the

 

 

 

 

secondary volume is not in an error state and can be

 

 

 

 

accessed.

%s:%s

==>

%s:%s is already enabled

Kernel

The user attempted to enable a remote mirror set using

 

 

 

 

the same secondary volume and secondary host as a

 

 

 

 

remote mirror set that is already enabled. Specify a

 

 

 

 

different secondary volume or secondary host for the

 

 

 

 

new set.

%s ==>

%s

not already enabled

Kernel

The user has tried to do an operation on a set that is

 

 

 

 

not enabled. Verify that the proper set has been

specified to sndradm and then verify that the set is enabled using sndradm -i.

Set Copy Parameters failed

set <shost>:<svol> neither sync nor async

set <shost>:<svol> not found in config

PITC

iiadm could not modify the copy units and delay

 

values for the specified 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 for the parameters

 

DSW_ENOTFOUND: The specified set was not found in

 

the kernel.

 

EINVAL: The delay or units value is out of range.

RM

The mode of the set specified in the configuration file

 

is incorrect. This occurs whenthe user inserts a set into

 

the configuration manually, using dscfg with an

 

incorrect mode tag.

RM

The specified set is not in the current configuration.

 

Use sndradm -ito verify that the set is in the current

 

configuration.

Shadow

and bitmap are the same

PITC

During an enable operation, iiadm discovered that the

device

 

 

shadow volume and the bitmap volume are the same.

 

 

 

 

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

Page 44
Image 44
Sun Microsystems 3.2 manual Kernel Set cannot contain more than one disk queue. To add, Accomplish this task, Accessed

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.