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

Error Message

From Meaning

Copy failed

Could not create rdc_config process

PITC

A copy or update operation could not be initiated.

 

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 on the command

 

line.

 

DSW_ENOTFOUND: The specified set could not be found

 

in the kernel.

 

DSW_ECOPYING: A copy is already in progress, or a

 

partial copy was aborted and the new copy request

 

does not match the aborted one.

 

DSW_EOFFLINE: One or more volumes in the set is

 

offline.

 

DSW_EINCOMPLETE: The shadow is exported or

 

imported.

 

DSW_EINUSE: The set is PID-locked by another

 

process.

 

DSW_ERSRVFAIL: The kernel was unable to access one

 

or more volumes in the set.

 

DSW_EOPACKAGE: Another package (for example:,

 

RDC) told the point-in-time copy software not to

 

perform the copy operation.

 

DSW_EIO: The kernel had a problem reading or writing

 

one of the volumes in the set.

Kernel

The user has issued a sync for a remote mirror set and

 

the process could not be started for the set. The system

 

is probably low on resources. Check the amount of

 

memory and threads available.

Could not open file %s:%s on

Kernel The user issued a sync command and the primary host

remote node

could not reach the secondary host. Verify that the link

 

from the primary to the secondary host is operating

 

and that none of the ports used by the remote mirror

 

are blocked by a firewall or in use by another

 

application.

 

 

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

Page 34
Image 34
Sun Microsystems 3.2 Copy or update operation could not be initiated, Possible errors, Line, Kernel, Offline, Imported

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.