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

Error Message

 

 

From

Meaning

The volume

%s is

already in use

Kernel

The data volume in the remote mirror set is already in

 

 

 

 

 

 

use as a bitmap volume or a disk queue volume. Use a

 

 

 

 

 

 

different data volume.

Too many volumes

given

for update

PITC

iiadm ran out of memory.

Unable

to

access

bitmap

 

PITC

During an enable operation, iiadm tried to validate

 

 

 

 

 

 

the bitmap device, but could not get access to it.

Unable

to

access

master

volume

PITC

During an enable operation, iiadm tried to validate

 

 

 

 

 

 

the master device, but could not get access to it.

Unable

to

access

set in

core

PITC

During a reset operation, iiadm was unable to find the

 

 

 

 

 

 

set listed in the kernel.

Unable

to

access

shadow

volume

PITC

During an enable operation, iiadm tried to validate

 

 

 

 

 

 

the shadow device, but could not get access to it.

unable to access <vol>: <error>

unable to add "<host>" to configuration storage: <error>

Unable to add interface %s to %s

unable to add "<set>" to configuration storage: <error>

unable to allocate memory for cluster tag

unable to allocate pair_list array for <rdc_max_sets> sets

Unable to allocate <X> bytes for bitmap file <vol>

unable to ascertain environment

RM

The data volume cannot be accessed. Verify that the

 

data volume has been entered correctly and that it

 

exists on the system.

RM

An error has occurred preventing remote mirror from

 

accessing the configuration storage while trying to

 

update the options field.

Kernel

The remote mirror software was unable to add host

 

information to its configuration. Verify that the system

 

is not running low on memory.

RM

An error has occurred that prevents the remote mirror

 

software from accessing the configuration storage

 

database when trying to enable <set>.

RM

System is running low on available memory.

RM

System is running out of memory.

RM

The system is running low on available memory.

PITC

iiadm tried to determine whether the host is part of a

 

cluster, but was unable to do so.

unable

to ascertain environment

RM

The remote mirror software was not able to determine

 

 

 

if the system is part of a SunCluster configuration.

unable to clear autosync value in

RM

Autosync could not be turned off for the remote mirror

config

for SNDR set <shost>:<svol>

 

set in the configuration file because of an error writing

 

 

 

to the configuration database.

unable to determine disk group name

PITC

iiadm tried to find out to which cluster device group a

for %s

 

 

volume belonged, but was unable to do so.

 

 

 

 

Chapter 3 Error Messages 37

Page 47
Image 47
Sun Microsystems 3.2 During an enable operation, iiadm tried to validate, Bitmap device, but could not get access to it

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.