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

Error Message

From Meaning

Join failed

List failed

local tag "<ltag>" is longer than CFG_MAX_BUF (x)

Master and bitmap are the same device

Master and shadow are the same device

Master volume is already an overflow volume

PITC

Could not join shadow volume back to the 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: A volume was missing on the command

 

line.

 

DSW_ENOTFOUND: The set could not be found in the

 

kernel.

 

DSW_ENOTEXPORTED: The set to which the user is

 

trying to join the volume is not in the exported state.

 

DSW_EINVALBMP: The bitmap volume is not big

 

enough to handle the master volume.

 

DSW_ERSRVFAIL: The kernel module was unable to

 

access the bitmap volume.

 

DSW_EOPEN: The kernel module was unable to access

 

the shadow volume.

PITC

Could not get a list of volumes from the kernel.

 

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 when

 

attempting to perform the operation.

RM

The l.<hostname> tag generated for the ctag to use

 

to mark the remote mirror set as local is too long. This

 

results if a long host name is returned from the call to

 

uname.

PITC

During an enable operation, iiadm discovered that the

 

master volume and the bitmap volume are the same.

PITC

During an enable operation, iiadm discovered that the

 

master volume and the shadow volume are the same

PITC

During an enable operation, iiadm discovered that the

 

volume specified as the master is already in use as an

 

overflow volume.

Master volume is not a character

PITC

During an enable operation, iiadm discovered that the

device

 

master volume is a block device and not a character or

 

 

raw device.

master volume name must start with

PITC

The master volume must exist in the /dev directory

/dev

 

tree.

Memory allocation error

PITC

iiadm ran out of memory.

 

 

 

Chapter 3 Error Messages 31

Page 41
Image 41
Sun Microsystems 3.2 Could not join shadow volume back to the set. Possible, Dsweempty a volume was missing on the 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.