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

Error Message

From

Meaning

Memory allocation failure

PITC

iiadm ran out of memory.

Must be super-user to execute

Kernel

The user issued a remote mirror command but does

 

 

not have superuser privileges. All remote mirror

 

 

commands require superuser privileges.

must specify full set details for enable command

no matching SNDR sets found in config

Not a compact dependent shadow

Not all Instant Image volumes are in a disk group

not a valid number, nust be a decimal between 1 and <max>

Not primary, cannot sync %s:%s and %s:%s

NULL struct knetconfig passed down from user program

NULL struct netbuf passed down from user program for %s

Operation not possible, disk queue %s is not empty.

RM

The user attempted to enable a set using the shost:svol

 

format. All parameters for a set must be specified.

RM

The set specified for the command cannot be found in

 

the current configuration. Check the set to ensure that

 

it matches one of the configured sets. Use sndradm -

 

i to view the sets configured sets.

PITC

The user attempted to attach an overflow volume to a

 

set that is not a compact dependent 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: No volume name was specified.

 

DSW_ENOTFOUND: The set could not be found in the

 

kernel.

PITC

All volumes (master, shadow, and bitmap) must be in

 

the same cluster device group.

RM

The number entered is out of the allowed range or is

 

not a number.

Kernel

An update, full sync, or reverse sync command was

 

issued on the secondary host. These command can be

 

issued only on the primary host. Log in to the primary

 

host and issue the request.

Kernel

The remote mirror software could not get network

 

information for the remote mirror set.

Kernel

The remote mirror software could not get network

 

information for the remote mirror set.

Kernel

Disk queue was not empty when the current operation

 

was attempted. This usually occurs when the user

 

attempts to disable.

Out

of memory

PITC

iiadm ran out of memory.

Out

of memory creating lookup table

PITC

iiadm ran out of memory.

 

 

 

 

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

Page 42
Image 42
Sun Microsystems 3.2 User attempted to enable a set using the shostsvol, Set specified for the command cannot be found

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.