Sponsored Content
Operating Systems Solaris Serial Split Brain detected in solaris10 Post 302409841 by upengan78 on Friday 2nd of April 2010 07:15:08 PM
Old 04-02-2010
Smilie

Quote:
Originally Posted by reborg
What kind of setup is this? A cluster or have you somehow connected two non-clustered nodes to the same storage?

---------- Post updated 2010-04-03 at 12:01 AM ---------- Previous update was 2010-04-02 at 11:58 PM ----------

Also can you post the output of:

Code:
vxdg -o alldgs list

Hello,

Thanks for reply.

This is a single machine (v440) connected via scsi cable to only ESM on storedge D2. Other scsi port is terminated using LVD/SE terminator. No cluster software on the v440 as well as no such intention.

Code:
 vxdg -o alldgs list
VxVM vxdg ERROR V-5-1-776 Option alldgs not recognized, recognized options are:
        failfast - set the failfast timeout for the disk (msec)
        verify - verifies that the specified disk group task can be performed
                without violating any storage-specific guidelines,
                but does not perform the task
        override - performs the  disk  group  task  and  ignores  any
                storage-specific   guidelines
        remove - removes the objects involved in a move/split/join from
                thisdiskgroup
        complete - perform recovery by retrying original operation
        clean - clear any move/split/join-related internal flags
        expand  - select additional objects that reside on same disks
        dgtype - select dg type (private, shared, san)
        clearreserve - clear reservations before import
        groupreserve - import with group reserve
        listreserve - show group reserve information with list command
        ejectkey - eject host membership
        dgid - need to use dgid for the dg to be initialized
        selectcp - Select cp on this disk
        site - Site based import
        noreonline - Don't reonline disks
        coordinator - dg disks reserved as coordinator disks




        site - disk group site name
        tag -  disk group tag name[=value]
        source - disk group tag source
        useclonedev - import clone disks
        updateid - update ids when importing clone disks
        addmirror - Add mirror on the new site
        rmmirror - Remove mirror on the site being removed
        overridessb - Override SSB on reattaching a disk/site
        alldisks - Reattach a site only if all disks are online
        autotagging - Autotaging for newly added disks

 

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Brain Bench Certification

Hi, Can anybody provide me Pointers to Practice tests or any Material to prepare for Brainbench certification in Unix Shell Scripting? Also how good is this Certification for UNIX programmers. Is it worth it? I'm planning to take this certification in 2 weeks. Kindly let me know all the pros... (0 Replies)
Discussion started by: pavan_emani
0 Replies

2. Programming

C Brain Teaser

Dear Gurus, I have encountered a C question, which I thought of sharing with you. This question was asked by one of my technical training staff...Though my training was over I'm still thinking of a solution for this.. Write a C program to do a small task(lets say just simply printing a "Hello... (34 Replies)
Discussion started by: vrk1219
34 Replies

3. Programming

Brain Teaser Extended

Hi Gurus, To the Brain Teaser, if I add another condition, say the executable should not be altered, how the program should be altered? (no perl please, purely C). I forgot to mention this condition my staff had mentioned. ( forgot then and got now :D ) The program executed the first time... (4 Replies)
Discussion started by: vrk1219
4 Replies

4. Ubuntu

Ubuntu 9.04 Serial application to telnet to serial device

Hello! I am working on an application which reads environmental instruments which have serial ports. The application requires a serial port to be present to talk to the device (i.e. /dev/ttyS0 ). In some instances the environmental devices will be 100's of yards away from the computer, so a... (5 Replies)
Discussion started by: mvona
5 Replies

5. What is on Your Mind?

The Human Brain project

A global group of scientists are spending the next ten years and a billion dollars to try and develop a computer simulation of the brain: https://www.humanbrainproject.eu/ I always found it fascinating that the brain can understand itself. This almost sounds like in a few years the computer... (0 Replies)
Discussion started by: figaro
0 Replies
voldiskadd(8)						      System Manager's Manual						     voldiskadd(8)

NAME
voldiskadd - Adds one or more disks for use with the Logical Storage Manager SYNOPSIS
/usr/sbin/voldiskadd disk-address-list DESCRIPTION
The voldiskadd utility sets up new disks that are added to the system after the initial system installation and configures the disks for use by the Logical Storage Manager. A valid disk label must exist on the disk before using the voldiskadd utility. One or more disks may be specified using a disk-address-list. Disk addresses in the list have the form dskn (for the entire disk) or dsknp (for a specific partition). When specifying multiple disks, use a space between entries. Disk address names relate directly to device names in the /dev/disk directory. For example, here are some valid voldiskadd disk-address-list specifications: # voldiskadd dsk1 # voldiskadd dsk2 dsk3a The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadd. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadd utility prompts the user for a disk group name and disk media name for the disks. If a new disk group name is specified, that disk group is created for the new disks. If no disk group name is specified, the disks are left as unassigned replacement disks for future use. If an existing disk group name is specified, the user is prompted for whether the disks should be designated as spares for the disk group. If a disk is found to already contain non-Logical Storage Manager partitioning, the user is asked whether the disk should be encapsulated. Encapsulation turns each partition of the disk into a volume. A disk should be encapsulated if it contains file systems or data that should not be overwritten. If encapsulation is not desired for a disk, the disk can be initialized as a new disk for use by the Logical Storage Manager. For new disks, all space on the disk becomes free space in the disk's disk group. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. The voldiskadd utility supports the following general classes of actions: Initializing a disk with reserved regions and partitions. Disk initialization is performed by calling voldisksetup command. Adding a disk to an existing disk group. This operation can be performed independently of the initialization of the disk drive to add a disk's storage space to a disk group's free space pool. The volassist command may subsequently allocate from that free space. The disk can also be added as a hot spare device. Creating new disk groups in which to import new disks. If no disk group exists for importing disks, the option of creating the disk group is offered. Encapsulating disks that have exist- ing contents. This is the default action for disks that do not have a valid, existing Logical Storage Manager private region, but that do have a disk label. Encapsulation is performed by calling volencap. Reconnecting a drive that was temporarily inaccessible. This situation is detected automatically, by noting that the specified drive has a disk ID that matches a disk media record with no currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes referring the disk are restarted. This reattach action is performed by calling the volrecover script. ERRORS
You may receive the following messages when using the voldiskadd command: Initialization of disk device special-device failed. Error: special-device or an overlapping partition is open. This message indicates that the partition you specified or an overlapping partition on the disk is actively in use. The partition could be a mounted UFS or AdvFS filesystem, initialized as an LSM disk or used as a swap device. special-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data. Would you like to continue?? [y,n,q,?] (default: n) This message indicates that the fstype of a partition or an overlapping partition is set in the disk label. The voldiskadd command prints this message to warn that a disk partition may have valid data which could be destroyed. If you are sure that the disk partition does not have valid data and that the partition can be added to LSM, you can ignore the warning message by entering y at the prompt. The voldiskadd command will proceed to initialize the disk partition and add it to LSM. FILES
A list of disks to exclude from use by voldiskadd. SEE ALSO
disklabel(8), volassist(8), voldisk(8), voldiskadm(8), voldisksetup(8), voldg(8), volintro(8) voldiskadd(8)
All times are GMT -4. The time now is 08:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy