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

Error Message

 

From

Meaning

Shadow

group

%s is suspended

PITC

The user attempted to perform a copy or update

 

 

 

 

operation on a group with one or more suspended sets.

 

 

 

 

The %s parameter identifies the first set found in the

 

 

 

 

group that is suspended.

Shadow

group

suspended

PITC

The user attempted to perform a copy or update

 

 

 

 

operation on a suspended set.

Shadow volume is already an

PITC

During an enable operation, iiadm discovered that the

overflow volume

 

volume specified as the shadow volume is already in

 

 

 

 

use as an attached overflow volume.

Shadow

volume

is already configured

PITC

During an enable operation, iiadm discovered that the

 

 

 

 

volume specified as the shadow volume is already in

 

 

 

 

use as a shadow for a different master volume.

Shadow Volume is currently mounted

PITC

iiadm could not disable the set because the shadow

and dependent

on the master volume

 

volume is mounted and part of an independent set and

 

 

 

 

the copy has not yet completed.

Shadow volume is mounted, unmount

PITC

During an enable operation, iiadm discovered that the

it first

 

 

volume specified as the shadow volume is currently

 

 

 

 

mounted.

Shadow volume is not a character

PITC

During an enable operation, iiadm discovered that the

device

 

 

 

shadow volume is a block device and not a character

 

 

 

 

or a raw device.

shadow volume name must start with /dev

Shadow volume not in a disk group

Size of Primary %s:%s(%s) must be less than or equal to size of Secondary %s:%s(%s)

SNDR: can’t stat <vol>

PITC

The shadow volume must exist in the /dev directory

 

tree.

PITC

During an attach operation, iiadm determined that the

 

set to which the user is attaching an overflow volume

 

is neither in a cluster device group nor in a local

 

(l.hostname) group.

Kernel

The user set up a remote mirror set in which the

 

secondary volume is smaller than the primary volume.

 

The secondary volume must be equal to or larger than

 

the primary volume but the size is not checked until a

 

sync is issued for the remote mirror set. The user must

 

either disable the remote mirror set on the primary

 

host and decrease the size of the primary volume so

 

that it is equal to or smaller than the secondary

 

volume, or disable the remote mirror set on the

 

secondary host and increase the size of the secondary

 

volume so that it is equal to or larger than the primary

 

volume.

RM

The volume specified cannot be accessed by the

 

system.

Chapter 3 Error Messages 35

Page 45
Image 45
Sun Microsystems 3.2 User attempted to perform a copy or update, Operation on a group with one or more suspended sets

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.