Sun Microsystems 3.2 manual Set does not have a disk queue attached when, Replace operation, Name

Page 46

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

Error Message

From

Meaning

SNDR set does not have a disk

RM

Set does not have a disk queue attached when

queue

 

attempting either a queue remove operation or a queue

 

 

replace operation.

SNDR: The volume ’<vol2>’ has been configured previously as ’<vol1>’. Re-enter command with the latter name.

SNDR: ’<vol1>’ and ’<vol2>’ refer to the same device

Stat failed

SV-disable failed

RM

The user attempted to enable a set in which the

 

volume was already enabled, but with a different

 

name.

RM

A physical device cannot be used for more than one

 

volume in the remote mirror set.

PITC

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: Could not find specified volume in

 

kernel.

PITC

iiadm tried to perform svadm -don a volume. See

 

the ds.log file for more information.

SV-enable failed

PITC

iiadm tried to perform svadm -eon a volume. See

 

 

the ds.log file for more information.

Target of copy/update is mounted, unmount it first

The bitmap %s is already in use

The remote state of %s:%s ==> %s:%s prevents this operation

The state of %s:%s ==> %s:%s prevents this operation

PITC

If the shadow in a master-to-shadow copy or update

 

operation or the master in a shadow-to-master copy or

 

update operation is mounted, it cannot be copied to.

Kernel

The bitmap requested for the remote mirror set being

 

enabled is already in use as a bitmap for another set.

 

Enable the set and specify a different volume for the

 

bitmap.

Kernel

The user attempted to do a sync or reverse sync while

 

the secondary volume is mounted. First unmount the

 

secondary volume and then issue the sync or reverse

 

sync request.

Kernel

The set the user is attempting to sync is part of an

 

advanced configuration. The state of one of the other

 

sets in the configuration prevents this sync from

 

occurring for one of the following reasons:

 

• Another set in a one-to-many configuration is

 

currently doing a reverse sync.

 

• A reverse sync is being requested for a set in a one-

 

to-many configuration and at least one of the other

 

sets is not in logging mode.

 

• A set is already syncing.

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

Image 46
Contents Sun Microsystems, Inc Please Recycle Contents Error Messages Preface Before You Read This BookUsing Unix Commands How This Book Is OrganizedShell Shell PromptsTypographic Conventions Shell superuserRelated Documentation Contacting Sun Technical Support Accessing Sun DocumentationSun Welcomes Your Comments Page Reboot Troubleshooting ChecklistCheck for installation errors Check the log file contentsChecking Log Files Improving PerformanceSafeguarding the Vtoc Information Page Remote Mirror Software Troubleshooting Tips Troubleshooting Log Files and Services Check the integrity of the link Check for common errorsChecking 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 Correcting Common User Errors Enabled Software on Only One HostWrong Volume Set Name Specified Using the dsstat Command Incorrectly To Find the Volume Set Name Accommodating Memory RequirementsRemote Mirror Software Troubleshooting Tips Page Is used but the arguments for units and delay are Iiadm was expecting a number to be on the commandLine. This happens when the copy parameters option Contains the volumes does not match the cluster tagDsweempty No overflow volume was specified Overflow volume could not be attached toSpecified set. Possible errors Dsweinuse The overflow volume is already beingVolume requested as a remote mirror bitmap Volume requested as a bitmap for the remoteMirror set is already configured to be used by Volume is already configured to be a volume used byErrors Remote mirror set cannot be found in the configurationDatabase. The set is not configured. Check the entry for Primary volume has a file system mounted on itFor another remote mirror set. a volume cannot be Kernel Set being enabled or resumed has a secondaryVolume that is already in use as a secondary volume Enabled as a secondary volume if it is already in use asDsweempty No set was specified on the command Copy or update operation could not be initiatedPossible errors Dsweoffline One or more volumes in the set isVolume An overflow volume couldn’t be initialized. PossibleDsweinuse The volume that was specified is already Dswersrvfail The kernel was unable to accessIiadm command must be issued on the other Kernel Request to disable the disk queue is alreadyUnsuccessfully before attempting to disable the disk Where the iiadm command was issuedRemote mirror software as a data volume or bitmap Disk queue volume specified forReconfiguration operation is already in use by Iiadm -ecommand expected dep or indDsweempty One of the volumes names master Could not enable volume. Possible errorsNew sets can be enabled Dsweinuse One of the volumes master, shadowDsweodependency The overflow volume is still Iiadm had a problem detaching the overflow volumeFrom a set. Possible errors Going from logging mode to replicating modeDsweempty One of the volume names is blank. File a Could not import shadow volume. Possible errorsSets can be enabled Dsweinuse One of the volumes is already in use byTrying to join the volume is not in the exported state Could not join shadow volume back to the set. PossibleDsweempty a volume was missing on the command Dsweinvalbmp The bitmap volume is not bigCurrent configuration. Check the set to ensure that User attempted to enable a set using the shostsvolSet specified for the command cannot be found It matches one of the configured sets. Use sndradmVolume the user specified to attach to a compact Iiadm could not get a list of overflow volumes fromKernel. Possible errors Master, shadow, or bitmap volumeSecondary volume is not in an error state and can be Disk queue replace command can also be used toSize of the secondary volume. Verify that AccessedUse as an attached overflow volume User attempted to perform a copy or updateVolume specified as the shadow volume is already Use as a shadow for a different master volumeVolume in the remote mirror set User attempted to enable a set in whichVolume was already enabled, but with a different Dswenotfound Could not find specified volumeMaster device, but could not get access to it During an enable operation, iiadm tried to validateBitmap device, but could not get access to it During a reset operation, iiadm was unable to findCould not find remote mirror group in configuration Be determined. Verify the settingsSunCluster could not find the specified disk service Could not find remote mirror set in configurationOpened. The volume might not exist or is already Lookup of the set ID in the configuration database forVolume specified for the bitmap could not be Iiadm attempted to access the configuration fileSame as Update failed meaning but for a specific One or more volumes in a group copy or updateCommand failed. Possible errors During a reset, iiadm tried to updateIiadm detected that the master, shadow, and bitmap Volumes are not all in the same cluster device groupVolume vol is not being managed by As required by the point-in-time copy softwareRelated 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.