Sun Microsystems 3.2 Iiadm could not get a list of overflow volumes from, Kernel. Possible errors

Page 43

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

Error Message

From

Meaning

Overflow list access failure

PITC

iiadm could not get a list of overflow volumes from

 

 

the kernel. Possible errors:

 

 

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

 

 

bound. File a bug against iiadm.

 

 

ENOMEM: The kernel module ran out of memory.

Overflow volume is already in an

PITC

During an attach operation, iiadm determined that the

InstantImage group

 

volume the user specified to attach to a compact

 

 

dependent set is already in use by another set as a

 

 

master, shadow, or bitmap volume.

overflow volume name must start

PITC

The overflow volume must exist in the /dev directory

with /dev

 

tree

Overflow volume not in a disk group

PITC

The user attempted to attach a volume to a set, but the

 

 

set's volumes are part of a cluster device group and the

 

 

overflow volume is not.

Overflow volume not in same disk

PITC

The user attempted to attach a volume to a set, but the

group as shadow set members

 

set's volumes are in a different cluster device group

 

 

than the overflow volume.

Recovery bitmaps not allocated

Request not serviced, %s is currently being synced.

Reset shadow failed

Kernel

A full copy, update, sync, or reverse sync operation has

 

been requested but the bitmap on the primary host

 

cannot be accessed. Verify that the bitmap volume is a

 

valid volume and is not in an error state.

Kernel

The user attempted to sync the remote mirror set, or

 

put the remote mirror set into logging mode, while a

 

previous sync request is being set up. If the user issued

 

a second sync request, the user must first put the

 

remote mirror set into logging mode and then issue the

 

sync. If the user issued a logging request, the user

 

must first wait for the sync request to finish setting up

 

and then issue the logging request. This stops the sync

 

and places the remote mirror set into logging mode.

PITC

iiadm could not reset 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: No set was specified to reset.

 

DSW_ENOTFOUND: The specified set could not be found

 

in the kernel.

 

EINVAL: Bitmap volume is invalid.

 

DSW_ERSRVFAIL: The kernel could not access one of

 

the volumes.

 

DSW_EHDRBMP: Could not set up bitmap header.

Chapter 3 Error Messages 33

Page 42 Page 44
Image 43
Page 42 Page 44
Contents Sun Microsystems, Inc Please Recycle Contents Error Messages Before You Read This Book PrefaceHow This Book Is Organized Using Unix CommandsShell superuser Shell PromptsTypographic Conventions ShellRelated Documentation Contacting Sun Technical Support Accessing Sun DocumentationSun Welcomes Your Comments Page Check the log file contents Troubleshooting ChecklistCheck for installation errors RebootImproving Performance Checking Log FilesSafeguarding the Vtoc Information Page Remote Mirror Software Troubleshooting Tips Check the integrity of the link Check for common errors Troubleshooting Log Files and ServicesChecking Log Files Checking That the rdc Service Is Running If the /dev/rdc Link Is Not Created Checking the Integrity of the Link Testing with ifconfig Nws822# snoop -d hme0 port rdc Enabled Software on Only One Host Correcting Common User ErrorsWrong Volume Set Name Specified Using the dsstat Command Incorrectly Accommodating Memory Requirements To Find the Volume Set NameRemote Mirror Software Troubleshooting Tips Page Contains the volumes does not match the cluster tag Iiadm was expecting a number to be on the commandLine. This happens when the copy parameters option Is used but the arguments for units and delay areDsweinuse The overflow volume is already being Overflow volume could not be attached toSpecified set. Possible errors Dsweempty No overflow volume was specifiedVolume is already configured to be a volume used by Volume requested as a bitmap for the remoteMirror set is already configured to be used by Volume requested as a remote mirror bitmapPrimary volume has a file system mounted on it Remote mirror set cannot be found in the configurationDatabase. The set is not configured. Check the entry for ErrorsEnabled as a secondary volume if it is already in use as Kernel Set being enabled or resumed has a secondaryVolume that is already in use as a secondary volume For another remote mirror set. a volume cannot beDsweoffline One or more volumes in the set is Copy or update operation could not be initiatedPossible errors Dsweempty No set was specified on the commandDswersrvfail The kernel was unable to access An overflow volume couldn’t be initialized. PossibleDsweinuse The volume that was specified is already VolumeWhere the iiadm command was issued Kernel Request to disable the disk queue is alreadyUnsuccessfully before attempting to disable the disk Iiadm command must be issued on the otherIiadm -ecommand expected dep or ind Disk queue volume specified forReconfiguration operation is already in use by Remote mirror software as a data volume or bitmapDsweinuse One of the volumes master, shadow Could not enable volume. Possible errorsNew sets can be enabled Dsweempty One of the volumes names masterGoing from logging mode to replicating mode Iiadm had a problem detaching the overflow volumeFrom a set. Possible errors Dsweodependency The overflow volume is stillDsweinuse One of the volumes is already in use by Could not import shadow volume. Possible errorsSets can be enabled Dsweempty One of the volume names is blank. File aDsweinvalbmp The bitmap volume is not big Could not join shadow volume back to the set. PossibleDsweempty a volume was missing on the command Trying to join the volume is not in the exported stateIt matches one of the configured sets. Use sndradm User attempted to enable a set using the shostsvolSet specified for the command cannot be found Current configuration. Check the set to ensure thatMaster, shadow, or bitmap volume Iiadm could not get a list of overflow volumes fromKernel. Possible errors Volume the user specified to attach to a compactAccessed Disk queue replace command can also be used toSize of the secondary volume. Verify that Secondary volume is not in an error state and can beUse as a shadow for a different master volume User attempted to perform a copy or updateVolume specified as the shadow volume is already Use as an attached overflow volumeDswenotfound Could not find specified volume User attempted to enable a set in whichVolume was already enabled, but with a different Volume in the remote mirror setDuring a reset operation, iiadm was unable to find During an enable operation, iiadm tried to validateBitmap device, but could not get access to it Master device, but could not get access to itCould not find remote mirror set in configuration Be determined. Verify the settingsSunCluster could not find the specified disk service Could not find remote mirror group in configurationIiadm attempted to access the configuration file Lookup of the set ID in the configuration database forVolume specified for the bitmap could not be Opened. The volume might not exist or is alreadyDuring a reset, iiadm tried to update One or more volumes in a group copy or updateCommand failed. Possible errors Same as Update failed meaning but for a specificAs required by the point-in-time copy software Volumes are not all in the same cluster device groupVolume vol is not being managed by Iiadm detected that the master, shadow, and bitmapRelated Error Messages

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.
Top Page Image Contents