10 More Discussions You Might Find Interesting
1. AIX
Good afternoon!
Help with a solution
I have AIX 7.1
works through vios
I expanded Lun
that it is necessary to make that aix saw this change and to expand the section lvm
Sorry for my English (1 Reply)
Discussion started by: iformats
1 Replies
2. Solaris
Hi All
I am having VxVm on two Solaris hosts. host1 is using disk group dgHR. right now this server went down due to hardware fault. Not I need to import this dgHR into host2 server. Please let me know the procedure for the same. (1 Reply)
Discussion started by: amity
1 Replies
3. Solaris
Dear all,
i want to get the LUN ID for some disks in solaris 10
what commands options for the MPXIO and inq i want these utilities only
because i don't have solution enabler or powerpath
BR, (1 Reply)
Discussion started by: maxim42
1 Replies
4. AIX
Hi,
I am not getiting lun id information on VIO Server. I have used the command fget_config command.
just showing # prompt.
I would like know wheather any other command is there equiv of fget_config
which will display lun id? (4 Replies)
Discussion started by: manoj.solaris
4 Replies
5. Solaris
How to share a diskgroup in veritas. (1 Reply)
Discussion started by: padmaja
1 Replies
6. Solaris
I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer.
thanks (4 Replies)
Discussion started by: uuontario
4 Replies
7. Solaris
hey guys i got this in my logs what does this mean: (1 Reply)
Discussion started by: sbn
1 Replies
8. Solaris
Hello experts..
I am unable to import a disk group using vxdg . Is there any other command to import a disk group..
Thanks in advance.. (4 Replies)
Discussion started by: younus_syed
4 Replies
9. AIX
I have been ask to write a script to show what phyical disks are linked to what luns. By host name. I was hoping someone had some ideas on how to do this. I am from a linux background and am struggling a bit here...lol...I have been given one command to help me out....lsmap..Anyhelp would be... (3 Replies)
Discussion started by: jameszak
3 Replies
10. Red Hat
Hello,
I'm trying to help a guy out on a VMWARE server, running what looks like a cut down version of redhat? 2.4.9-vmnix2 ...
Bascially the box serves vm clients via allocating a LUN from a SAN.. to cut a long story short, I need to find out which SAN the luns are comming from (could be 1... (0 Replies)
Discussion started by: itsupplies
0 Replies
vxdco(1M) vxdco(1M)
NAME
vxdco - perform operations on DCO objects and DCO volumes
SYNOPSIS
vxdco [-g diskgroup] att volume dco
vxdco [-g diskgroup] attlogvol dco dco_volume
vxdco [-g diskgroup] [-o rm] dis dco
vxdco [-g diskgroup] [-o rm] dislogvol dco
vxdco [-g diskgroup] -o force enable dco
DESCRIPTION
Note: The vxdco command can only be used with version 0 DCOs and DCO volumes. It cannot be used with version 20 DCOs and DCO volumes.
The vxdco command is used to manipulate version 0 data change objects (DCO objects or DCOs) and DCO volumes that allow the use of Persis-
tent FastResync with volumes.
The att operation attaches a DCO object, dco, to a volume, volume. If the DCO object has an associated DCO volume, you can use the command
vxvol set fmr=on volume to enable Persistent FastResync on the volume after the att operation has completed.
The attlogvol operation associates a DCO volume, dco_volume, with a DCO object, dco. If the DCO object is already attached to a volume,
you can use the command vxvol set fmr=on volume to enable Persistent FastResync on the volume after the attlogvol operation has completed.
The dis operation dissociates a DCO object, dco, from a volume, and disables FastResync on that volume. If the -o rm option is specified,
the DCO object, the DCO volume, its plexes and associated subdisks are removed in the same operation.
The dislogvol operation dissociates a DCO volume from a DCO object, dco, and disables FastResync on the parent volume. If the -o rm option
is specified, the DCO volume, its plexes and associated subdisks are removed in the same operation.
If an error occurs while reading or writing a DCO volume, it is detached and the badlog flag is set on the DCO. (You can use one of the
options -a, -F or -m to vxprint to check if the badlog flag is set on a DCO.) The -o force enable operation clears the badlog flag on the
DCO.
The following command sequence demonstrates how to recover the DCO volume that tracks the top-level volume vol1 in the disk group egdg:
vxdco -g egdg -o force enable vol1_dco
vxvol -g egdg stop vol1
vxvol -g egdg start vol1
Here vol1_dco is the DCO associated with vol1.
Caution: Only use the -o force enable operation if you are certain that no writes have gone to the volume since the error occurred that
caused its DCO volume to become detached. Otherwise, data corruption may result.
The -g diskgroup option specifies the disk group to which the parent volume, DCO object, and DCO volume belong.
You can use the make keyword to vxassist to create a volume with an attached DCO object and DCO volume. You can also use the addlog key-
word to vxassist to create and add a DCO object and DCO volume to an existing volume. vxdco may then be used to dissociate a DCO object
from its parent volume, and subsequently reattach it if the DCO object and DCO volume have not been removed.
The vxdco command is also used by vxassist and vxplex to handle the DCO objects and DCO volumes that are associated with volumes. The
vxmake command is used to create DCO objects, which can be specified using output from vxprint.
Note: When using disk group move, split and join (see vxdg(1M)) to move volumes or snapshot volumes between disk groups, take care to
ensure that the DCO volumes accompany their parent volumes.
EXIT CODES
The vxdco utility exits with a non-zero status if the attempted operation fails. A non-zero exit code is not a complete indicator of the
problems encountered, but rather denotes the first condition that prevented further execution of the utility.
See vxintro(1M) for a list of standard exit codes.
NOTES
When a volume is attached to a DCO as its log volume, its device nodes are deleted. If vxdco dislogvol is subsequently used to dissociate
the log volume from the DCO, the device nodes are not recreated.
SEE ALSO
vxassist(1M), vxdg(1M), vxintro(1M), vxmake(1M), vxplex(1M), vxprint(1M), vxvol(1M)
VxVM 5.0.31.1 24 Mar 2008 vxdco(1M)