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

Error Message

From Meaning

Update failed

Update of %s failed

PITC

One or more volumes in a group copy or update

 

command failed. 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.

 

EINVAL: User is performing a shadow-to-master copy,

 

but two or more shadows are of the same master.

 

DSW_EIO: The kernel had a problem reading or writing

 

one of the volumes in the set.

PITC

Same as Update failed meaning but for a specific

 

volume.

Update

of config failed

PITC

During a reset, iiadm tried to update the

 

 

 

configuration file to indicate that the set is now online,

 

 

 

but failed to do so.

Version

failed

PITC

iiadm queried the kernel for the version of the code it

 

 

 

was running, but failed. Possible errors:

 

 

 

EFAULT: The kernel module tried to read out-of-

 

 

 

bounds. File a bug against iiadm

<vol> is already configured as an

RM

The master, shadow, or bitmap volume in the ndr_ii

SNDR bitmap

 

entry is already configured as a remote mirror bitmap

 

 

 

volume.

<vol> is not a character device

Volume is not in an InstantImage group

Volume is part of an InstantImage group

RM

The volume specified is not a character device.

PITC

A volume specified on the command line does not

 

belong to a point-in-time copy set.

PITC

The user attempted to initialize an overflow volume,

 

but the volume is in use as a master, shadow, or

 

bitmap

volumes and bitmaps must not match RM

The same volume has been specified for both the data

 

volume and the bitmap volume.

 

 

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

Page 50
Image 50
Sun Microsystems 3.2 One or more volumes in a group copy or update, Command failed. Possible errors, But failed to do so

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.