VxVm Failure Issues

How to recover a volume who’s plex is in Disable and recover state. Very handy command reference

Step 1 : vxmend -g <dgname> fix stale <plex-name>
Step 2: vxmend -g <dgname> fix clean <plex-name>
Step 3: vxvol -g <dgname> start <volumename>
Step 4: fsck – /dev/vx/rdsk/<dgname>/<volumename>
Step 5: mount /dev/vx/dsk/<dgname>/<volumename> /<mount point>
________________________________________________________________________________
Because the state of the plex vol01-01 is RECOVER, this plex was in the ACTIVE state prior to the failure.
• Because the state of the plex vol01-02 is STALE, vol01-01 was the plex with the good data prior to the failure.
• Since the failure, no I/O could have occurred.
You can conclude that plex vol01-01 has the good data.

To resolve this problem, you run the following sequence of commands:

# vxmend fix stale vol01-01
# vxmend fix clean vol01-01
# vxrecover -s vol01
________________________________________________________________________________
Error:VxVM vxassist ERROR V-5-1-10128 Operation must be executed on master
Solution:
# vxdctl -c mode
mode: enabled: cluster active – SLAVE
master: masterserver
_______________________________________________________________________________
How to Import Didk Group
The PVT is completed on this host successfully… The disk was wiped out prematurely on this host. We have recovered the data..The procedure is as follows:

1. Run the following command to obtain the disk group ID (aka, dgid):
# vxdisk -s list | egrep “^Disk:|^dgname:|^dgid:|^$”
2. Recover the disk group via the disk group ID, i.e., dgid:
# vxdg import <disk_group_id>
example:
# vxdg import 951844539.1173.t1.veritas.com
3. start the volumes
# vxvol startall
_______________________________________________________________________________
Deport & Import dg

1) unmount and stop all volumes in the disk group on the first system
umount /vol1
vxvol -g <disk group name> stopall

2)vxdg deport <disk group name>

Go to second (2nd) server then
3) vxdg import <disk group name>

4) vxrecover -g <disk group name> -sb

-s start disabled volumes in the back ground (-b )
vg disable status and
—————————————————————————————————————————————-
Question: If one plex don’t have data, want to mirror the plex(volume) with out sync

Solution: vxvol -g <dgname> set sync=on

_______________________________________________________________________________
Issue: If vxdg list showing one of the dg is disabled status

solution: check volume,sd,plex status and lun status do according
1)if luns are fine volume is down , start volumes
vxvol – g dgname startall
2) if plex is off line
vxmend -g dgname pleaxname on
_______________________________________________________________________________
Newly added disk space cannot be seen in vxdg free and it keeps telling you it can’t allocate space to mirror or grow a volume. However; ‘vxassist maxgrow’ or ‘vxassist maxsize’ sees the disk space properly. You may also see a discrepancy in disk space available in vxdg free. How do I get everything in sync?

Exact Error Message

Cannot allocate space for xxxx block volume; Cannot allocate space to grow volume; Cannot allocate space to mirror xxxx block volume

Details:
After you’ve added a new LUN to the diskgroup in preparation of a resize, mirror, or new volume creation, VxVM complains that it cannot allocate space to perform the operation. In this example, it’s a resize. In other examples, ‘vxassist maxsize’ will show available space, but volume creation won’t succeed.

example syntax:
# vxassist -g datadg maxgrow testvol disk01
In this situation, it will report that the volume can be extended fine and sees that disk01 has available space. However; the operation fails when trying to resize the volume.

# vxdg -g datadg free
After further examination, the newly added LUN disk01 isn’t seen in ‘vxdg free’. This preventing the operation from succeeding.

To get everything in sync:
# /sbin/vxconfigd -k -x cleartempdir
You should now see disk01 in ‘vxdg free’ and the operations will succeed.
________________________________________________________________________________

Issue: monitor procedure did not complete within the expected time.

Solution:

1)check vxtask list , vxprint -ht commands outputs (fastness of display of output)
2)Check whether backup is running or not at that time
4) sar -u or sar -d —————————————–CPU & Disk ultization
3) view /var/VRTSvcs/log/engine_A.log ( check the time stamp error when it occured)
:$

________________________________________________________________________________
To check the
vxprint -ht | grep -i sync

vxtask -l list — check the how much time will take for sync
Task: 244 RUNNING
Type: ATCOPY
Operation: PLXATT Vol swapvol Plex swapvol-02 Dg rootdg
Started: Sat Nov 07 16:15:03 2009
Throttle: 0
Progress: 21.25% 4456448 of 20972736 Blocks
Work time: 2 minutes, 11 seconds (08:05 remaining)
# modinfo | egrep “qlc|emlx”;pkginfo -l VRTSvxvm | grep PSTAMP
42 78366000 30962a 273 1 emlxs (SunFC emlxs FCA v20070410-1.20g)
PSTAMP: Veritas-5.0_MP1_RP3.2:2007-08-28
Showing in CLAIMED state. Also last backups were successsfull.

VxVM
———
Backup configuration info —-/etc/vx/cbr/bk/<dgname>

Mantain host id inofrmation —/etc/vx/volboot

vxdiskadm

vxdg list

vxdisk list

vxprint -rth >>> Display Volume Layouts

vxdg init <dgn> disk01=c?t?d? >> Create diskgroup

vxdg -g <dgn> adddisk/rmdisk disk02=c?t?d? >>> To add/remove the initialised disk to/from the disk group

vxdg destroy <dgn> >> Destroy a disk group

vxassist -g <dgn> make <voln> 500m layout=concat/stripe/raid5 >>> To create the volume on the disk

vxassist -g <dgn> maxsize >>> To check total available size

vxassist -g <dgn> maxgrow <voln> >>> For separate volume

/usr/lib/vxvm/bin/vxresize -g <dgn> <voln> <+/- space(10g)> >>> To resize

vxvol -g <dgn> start <voln> >>> Check the volume details in the vxprint -th if it is disabled, execute the following command

newfs /dev/vx/rdsk/dgn/voln >>> To create the filesystem (UFS)

mkfs -f vxfs /dev/vx/rdsk/dgn/voln >>> To create the filesystem (VxFS)

Destroy the volume

unmount the file system
vxvol -g <dgname> stop <volume>
vxedit -g <dgname> -rf rm <volumename>

________________________________________________________________________________
resize files system noraml (concatination) only
vxresize -g <dg name> <volume name> -500m

Example(CRQ 84602)
vxresize -g sandg ora-data-ix001 +500m
vxresize -g sandg ora-data-ix002 +500m
vxresize -g sandg ora-data-tm002 +300m

In another way also we can find out increased file size in particular File System recently >>>
find / -mount -type f -mtime -1 -print | xargs ls -l
________________________________________________________________________________

To Findout the colume type i.e.,mirror / concatenation/stripe OR NOT
vxprint -g <dgn> -hvt

Example :
vxprint -g oraasfpspdg -hvt
OUTPUT :
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
v asfpspdatavl – ENABLED ACTIVE 734003200 SELECT asfpspdatavl-02 fsgen
pl asfpspdatavl-02 asfpspdatavl ENABLED ACTIVE 734003200 STRIPE 2/512 RW —————>>>>>>>>single plex that means not mirror AND STRIPE
sd 002oraasfpspdn-01 asfpspdatavl-02 002oraasfpspdn 0 51200000 0/0 EMC1_39 ENA
sd 002oraasfpspdn-03 asfpspdatavl-02 002oraasfpspdn 71680000 7168000 0/51200000 EMC1_39 ENA
sd 001oraasfpspdn-01 asfpspdatavl-02 001oraasfpspdn 0 141346048 0/58368000 EMC1_0 ENA
sd 006oraasfpspdn-01 asfpspdatavl-02 006oraasfpspdn 0 105281024 0/199714048 EMC1_31 ENA
sd 002oraasfpspdn-05 asfpspdatavl-02 002oraasfpspdn 79339520 62006528 0/304995072 EMC1_39 ENA
sd 003oraasfpspdn-01 asfpspdatavl-02 003oraasfpspdn 0 51200000 1/0 EMC1_38 ENA
sd 003oraasfpspdn-03 asfpspdatavl-02 003oraasfpspdn 71680000 7168000 1/51200000 EMC1_38 ENA
sd 004oraasfpspdn-01 asfpspdatavl-02 004oraasfpspdn 0 141346048 1/58368000 EMC1_2 ENA
sd 005oraasfpspdn-01 asfpspdatavl-02 005oraasfpspdn 0 141346048 1/199714048 EMC1_30 ENA
sd 003oraasfpspdn-05 asfpspdatavl-02 003oraasfpspdn 79339520 25941504 1/341060096 EMC1_38 ENA
dc asfpspdatavl_dco asfpspdatavl asfpspdatavl_dcl

================================================================================
vxdg -g <dgn> free ——–>>>>> TO KNOW THE FREE SPACE ON PARTICULAR DISKGROUP

Example: vxdg -g oraasfpspdg free
OUTPUT :
DISK DEVICE TAG OFFSET LENGTH FLAGS
003oraasfpspdn EMC1_38 EMC1_38 140983344 362704 –
006oraasfpspdn EMC1_31 EMC1_31 105281024 3424 –
006oraasfpspdn EMC1_31 EMC1_31 140936032 410016 –
007oraasfpspdn EMC1_13 EMC1_13 16128 141329920 –
501oraasfpspdn EMC2_5 EMC2_5 105281024 3424 –
501oraasfpspdn EMC2_5 EMC2_5 140936032 410016 –
502oraasfpspdn EMC2_14 EMC2_14 140983344 362704 –

================================================================================
vxdg destroy <dgn> >> Destroy a disk group

vxassist -g <dgn> make <voln> 500m layout=concat/stripe/raid5 >>> To create the volume on the disk
================================================================================
vxassist -g <dgn> maxsize >>> To check total ( MAXIMUM) available size for PARTICULAR DISKGROUP

Exapmle: # vxassist -g oraasfpspdg maxsize
OUTPUT :
Maximum volume size: 142880768 (69766Mb)

================================================================================
vxassit -g <dgn> maxsize layout=STRIPE/CONCATENATION/MIRROR —————–>>>> TO FINDOUT THE HOW MUCH SIZE TO BE EXTENDED
# vxassist -g oraasfpspdg maxsize layout=stripe
Maximum volume size: 3102720 (1515Mb)

================================================================================
vxassist -g <dgn> maxgrow <voln> —————->>>>> To Find how much size to grow a volume of a diskgroup(i.e Max Limit of Volume in size)

Example : # vxassist -g oraasfpspdg maxgrow asfpspdatavl
Output : Volume asfpspdatavl can be extended by 2377728 to: 736380928 (359561Mb)

================================================================================
To Findout the disk(i.e c0t0d0s2) for VXVM Device (i.e diskname conversion for veritas devicname to real diskname)

Example : # vxdisk list EMC1_38
OUTPUT :
Device: EMC1_38
devicetag: EMC1_38
type: auto
hostid: server
disk: name=003oraasfpspdn id=1204842484.242.au11qap9h0tels2
group: name=oraasfpspdg id=1184578252.83.au11qap9o0tels2
info: format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags: online ready private autoconfig noautoimport imported
pubpaths: block=/dev/vx/dmp/EMC1_38s2 char=/dev/vx/rdmp/EMC1_38s2
guid: {964d2736-1dd1-11b2-a058-00144f269149}
udid: EMC%5FSYMMETRIX%5F102890%5F9027B000
site: –
version: 3.1
iosize: min=512 (bytes) max=2048 (blocks)
public: slice=2 offset=65792 len=141346048 disk_offset=0
private: slice=2 offset=256 len=65536 disk_offset=0
update: time=1208696323 seqno=0.52
ssb: actual_seqno=0.0
headers: 0 240
configs: count=1 len=48144
logs: count=1 len=7296
Defined regions:
config priv 000048-000239[000192]: copy=01 offset=000000 enabled
config priv 000256-048207[047952]: copy=01 offset=000192 enabled
log priv 048208-055503[007296]: copy=01 offset=000000 enabled
lockrgn priv 055504-055647[000144]: part=00 offset=000000
Multipathing information:
numpaths: 4
c6t5006048452A79A82d125s2 state=enabled ——————–
c6t5006048452A79A8Cd125s2 state=enabled ———————
c8t5006048452A79A83d125s2 state=enabled ————————-
c8t5006048452A79A8Dd125s2 state=enabled ——————————

# echo | format | grep -i c6t5006048452A79A82d125

199. c6t5006048452A79A82d125 <EMC-SYMMETRIX-5771 cyl 36826 alt 2 hd 30 sec 128>

================================================================================
MORE EXAMPLE

# vxdisk list

Output:

DEVICE TYPE DISK GROUP STATUS
Disk_0 auto:none – – online invalid
Disk_1 auto:none – – online invalid
Disk_2 auto:none – – online invalid
Disk_3 auto:none – – online invalid
Disk_4 auto:none – – online invalid
Disk_5 auto:none – – online invalid
Disk_6 auto:none – – online invalid
Disk_7 auto:none – – online invalid
EMC0_0 auto:cdsdisk – – online
EMC0_1 auto:cdsdisk – – online
EMC0_2 auto:cdsdisk – – online
EMC0_3 auto:cdsdisk – – online
EMC0_4 auto:cdsdisk – – online
EMC0_5 auto:cdsdisk – – online
EMC0_6 auto:cdsdisk – – online
EMC0_7 auto:cdsdisk – – online
EMC0_8 auto:cdsdisk – – online
EMC0_9 auto:cdsdisk – – online
EMC1_0 auto:cdsdisk 001oraasfpspdn oraasfpspdg online
EMC1_1 auto:cdsdisk 017oraabmorpdn oraabmorpdg online
EMC1_2 auto:cdsdisk 004oraasfpspdn oraasfpspdg online
EMC1_3 auto:cdsdisk 002oraasfmopdn oraasfmopdg online
EMC1_4 auto:cdsdisk 003oraasfmopdn oraasfmopdg online
EMC1_5 auto:cdsdisk 011oraabmorpdn oraabmorpdg online
EMC1_6 auto:cdsdisk 010oraabmorpdn oraabmorpdg online
EMC1_7 auto:cdsdisk 001au11qap9h0tels2dn au11qap9h0tels2dg online
EMC1_8 auto:cdsdisk – – online
EMC1_9 auto:cdsdisk – – online
EMC1_10 auto:cdsdisk 008oraasfmopdn oraasfmopdg online
EMC1_11 auto:cdsdisk 017oraabmrbpdn oraabmrbpdg online
EMC1_12 auto:cdsdisk – – online
EMC1_13 auto:cdsdisk 007oraasfpspdn oraasfpspdg online
EMC1_14 auto:cdsdisk 004oraasfptpdn oraasfptpdg online
EMC1_15 auto:cdsdisk – – online
EMC1_16 auto:cdsdisk – – online
EMC1_17 auto:cdsdisk 006oraabmrbpdn oraabmrbpdg online
EMC1_18 auto:cdsdisk 005oraabmorpdn oraabmorpdg online
EMC1_19 auto:cdsdisk 006oraabmorpdn oraabmorpdg online
EMC1_20 auto:cdsdisk 002oraabmrbpdn oraabmrbpdg online
EMC1_21 auto:cdsdisk 007oraabmrbpdn oraabmrbpdg online
EMC1_22 auto:cdsdisk 005oraabmrbpdn oraabmrbpdg online
EMC1_23 auto:cdsdisk 003oraabmrbpdn oraabmrbpdg online
EMC1_24 auto:cdsdisk 009oraabmrbpdn oraabmrbpdg online
EMC1_25 auto:cdsdisk 008oraabmrbpdn oraabmrbpdg online

________________________________________________________________________________
/opt/VRTS/bin/vxlicins – install veritas licence key
or
/opt/VRTS/bin/vxli* – get all

snap shot backup checking (running or not)
vxprint -lp |grep -i SNAP

________________________________________________________________________________

# vxconfigd -k
# vxdctl enable
# vxdctl mode
mode: enabled

# vxdg list
NAME STATE ID
rootdg enabled 1075769849.1025.nus104
RNE1BPSAN enabled 1139099076.5346.nus772

# vxdg import RNE1APSAN
vxvm:vxdg: ERROR: Disk group RNE1APSAN: import failed: No valid disk found containing disk group
# csh
karri# cd /tmp
karri# ls -l *bcv*
-rw-r–r– 1 root other 22753 Jun 4 00:02 export_bcv.out
-rw-r–r– 1 root other 13043 Jun 4 00:37 import_bcv.out
-rw——- 1 root other 515072 Dec 1 2008 nus104_bcv.tar
karri# grep vxdg import_bcv.out
+ vxdg list RNE1APSAN
vxvm:vxdg: ERROR: Disk group RNE1APSAN: No such disk group
+ vxdg -f -C import RNE1APSAN
vxvm:vxdg: ERROR: Disk group RNE1APSAN: import failed: vxconfigd is currently disabled
karri# vxdg -f -C import RNE1APSAN
karri# vxdg list
NAME STATE ID
rootdg enabled 1075769849.1025.nus104
RNE1APSAN enabled 1139050300.5250.nus772
RNE1BPSAN enabled 1139099076.5346.nus772

karri# vxinfo -g RNE1APSAN
AP_ix005 fsgen Startable
AP_ix004 fsgen Startable
AP_ix003 fsgen Startable
AP_da009 fsgen Startable
AP_da008 fsgen Startable
karri# vxvol -g RNE1APSAN startall
karri# vxinfo -g RNE1APSAN
AP_ix005 fsgen Started
AP_ix004 fsgen Started
AP_ix003 fsgen Started
AP_da009 fsgen Started
AP_da008 fsgen Started

karri# mountall
/dev/md/rdsk/d204 already mounted
/dev/md/rdsk/d205 already mounted
/dev/vx/rdsk/varcrash already mounted
/dev/vx/rdsk/appsstats already mounted
/dev/vx/rdsk/oraadmin already mounted
/dev/vx/rdsk/oraproduct already mounted
/dev/vx/rdsk/oraprodv920 already mounted
/dev/md/rdsk/d206 already mounted
checking ufs filesystems
/dev/vx/rdsk/RNE1APSAN/AP_Work: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_ix005: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_ix004: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_ix003: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_da009: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_da008: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_da007: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_da006: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_da005: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_tm001: 7 files, 1969266 used, 84317 free
/dev/vx/rdsk/RNE1APSAN/AP_tm001: (13 frags, 10538 blocks, 0.0% fragmentation)
/dev/vx/rdsk/RNE1APSAN/AP_rp001: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_sy001: SUMMARY INFORMATION BAD (SALVAGED)
/dev/vx/rdsk/RNE1APSAN/AP_sy001: 7 files, 614778 used, 401525 free
/dev/vx/rdsk/RNE1APSAN/AP_sy001: (13 frags, 50189 blocks, 0.0% fragmentation)
/dev/vx/rdsk/RNE1APSAN/AP_rd002: 9 files, 417050 used, 1636533 free
/dev/vx/rdsk/RNE1APSAN/AP_rd002: (13 frags, 204565 blocks, 0.0% fragmentation)
/dev/vx/rdsk/RNE1APSAN/AP_rd001: 9 files, 417050 used, 1636533 free
/dev/vx/rdsk/RNE1APSAN/AP_rd001: (13 frags, 204565 blocks, 0.0% fragmentation)
/dev/vx/rdsk/RNE1APSAN/AP_rb001: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_ix002: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_ix001: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_da004: 10 files, 8042442 used, 214787 free
/dev/vx/rdsk/RNE1APSAN/AP_da004: (11 frags, 26847 blocks, 0.0% fragmentation)
/dev/vx/rdsk/RNE1APSAN/AP_da003: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_da002: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_da001: is stable.
/dev/vx/rdsk/RNE1APSAN/AP_Archive: is stable.
mount: /dev/md/dsk/d204 is already mounted, /opt is busy,
or the allowable number of mount points has been exceeded
mount: /dev/md/dsk/d205 is already mounted, /home is busy,
or the allowable number of mount points has been exceeded
mount: /tmp already mounted
mount: /dev/vx/dsk/varcrash is already mounted, /var/crash is busy,
or the allowable number of mount points has been exceeded
mount: /dev/vx/dsk/appsstats is already mounted, /apps/stats is busy,
or the allowable number of mount points has been exceeded
mount: /dev/vx/dsk/oraadmin is already mounted, /ora/admin is busy,
or the allowable number of mount points has been exceeded
mount: /dev/vx/dsk/oraproduct is already mounted, /ora/product is busy,
or the allowable number of mount points has been exceeded
mount: /dev/vx/dsk/oraprodv920 is already mounted, /ora/product/v920 is busy,
or the allowable number of mount points has been exceeded
mount: /dev/md/dsk/d206 is already mounted, /ora/product/emagent10g is busy,
or the allowable number of mount points has been exceeded
karri# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d200 2055705 1278573 715461 65% /
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
/dev/md/dsk/d203 1527116 708852 757180 49% /var
swap 2746608 24 2746584 1% /var/run
swap 1572864 38576 1534288 3% /tmp
/dev/md/dsk/d204 1018382 660661 296619 70% /opt
/dev/md/dsk/d205 493688 133623 310697 31% /home
/vol/dev/dsk/c0t6d0/pbl5_sol8_701_sparc/s5
30 4 24 15% /cdrom/pbl5_sol8_701_sparc/s5
/vol/dev/dsk/c0t6d0/pbl5_sol8_701_sparc/s4
30 4 24 15% /cdrom/pbl5_sol8_701_sparc/s4
/vol/dev/dsk/c0t6d0/pbl5_sol8_701_sparc/s3
30 4 24 15% /cdrom/pbl5_sol8_701_sparc/s3
/vol/dev/dsk/c0t6d0/pbl5_sol8_701_sparc/s2
30 4 24 15% /cdrom/pbl5_sol8_701_sparc/s2
/vol/dev/dsk/c0t6d0/pbl5_sol8_701_sparc/s1
269719 253160 16559 94% /cdrom/pbl5_sol8_701_sparc/s1
/vol/dev/dsk/c0t6d0/pbl5_sol8_701_sparc/s0
54 54 0 100% /cdrom/pbl5_sol8_701_sparc/s0
/dev/vx/dsk/varcrash 1524463 10 1463475 1% /var/crash
/dev/vx/dsk/appsstats
1524463 1302355 161130 89% /apps/stats
/dev/vx/dsk/oraadmin 480751 66634 366042 16% /ora/admin
/dev/vx/dsk/oraproduct
413951 97200 275356 27% /ora/product
/dev/vx/dsk/oraprodv920
4128430 3348510 738636 82% /ora/product/v920
/dev/md/dsk/d206 1436342 32191 1346698 3% /ora/product/emagent10g
/dev/vx/dsk/RNE1APSAN/AP_Archive
8257229 6420131 1754526 79% /ora/data/RNE1AP/archive
/dev/vx/dsk/RNE1APSAN/AP_da001
7874541 7581394 214402 98% /ora/data/RNE1AP/da001
/dev/vx/dsk/RNE1APSAN/AP_da002
6193038 6044634 86474 99% /ora/data/RNE1AP/da002
/dev/vx/dsk/RNE1APSAN/AP_da004
8257229 8042442 132215 99% /ora/data/RNE1AP/da004
/dev/vx/dsk/RNE1APSAN/AP_da003
8257229 8093642 81015 100% /ora/data/RNE1AP/da003
/dev/vx/dsk/RNE1APSAN/AP_ix001
7874541 7683850 111946 99% /ora/data/RNE1AP/ix001
/dev/vx/dsk/RNE1APSAN/AP_ix002
8257229 8093642 81015 100% /ora/data/RNE1AP/ix002
/dev/vx/dsk/RNE1APSAN/AP_rd001
2053583 417050 1615998 21% /ora/data/RNE1AP/rd001
/dev/vx/dsk/RNE1APSAN/AP_rb001
2053583 1049114 983934 52% /ora/data/RNE1AP/rb001
/dev/vx/dsk/RNE1APSAN/AP_rd002
2053583 417050 1615998 21% /ora/data/RNE1AP/rd002
/dev/vx/dsk/RNE1APSAN/AP_sy001
1016303 614778 391362 62% /ora/data/RNE1AP/sy001
/dev/vx/dsk/RNE1APSAN/AP_rp001
8257229 8093650 81007 100% /ora/data/RNE1AP/rp001
/dev/vx/dsk/RNE1APSAN/AP_tm001
2053583 1969266 63782 97% /ora/data/RNE1AP/tm001
/dev/vx/dsk/RNE1APSAN/AP_da005
8256877 7991193 183116 98% /ora/data/RNE1AP/da005
/dev/vx/dsk/RNE1APSAN/AP_da006
8256877 7683858 490451 95% /ora/data/RNE1AP/da006
/dev/vx/dsk/RNE1APSAN/AP_da008
8256877 9 8174300 1% /ora/data/RNE1AP/da008
/dev/vx/dsk/RNE1APSAN/AP_da007
8256877 8093625 80684 100% /ora/data/RNE1AP/da007
/dev/vx/dsk/RNE1APSAN/AP_da009
8256877 9 8174300 1% /ora/data/RNE1AP/da009
/dev/vx/dsk/RNE1APSAN/AP_ix004
8256877 8093649 80660 100% /ora/data/RNE1AP/ix004
/dev/vx/dsk/RNE1APSAN/AP_ix003
8256877 8093625 80684 100% /ora/data/RNE1AP/ix003
/dev/vx/dsk/RNE1APSAN/AP_ix005
8256877 3073593 5100716 38% /ora/data/RNE1AP/ix005
/dev/vx/dsk/RNE1APSAN/AP_Work
6193038 1095447 5035661 18% /ora/data/RNE1AP/work

================================================================================
# vxdg list
NAME STATE ID
karri_dg enabled,cds 1231293234.529.karri
ora_cdb004_PRDROT_dg enabled,cds 1231467099.760.hans
ora_cdb006_PRDBAM_dg enabled,cds 1231473501.932.hans
ora_cdb007_PRDMOB_dg enabled,cds 1231478278.1132.hans
ora_cdb008_PRDBUL_dg enabled,cds 1231730135.666.hans

# vxsnap -g ora_cdb004_PRDROT_dg -xv list
NAME DG OBJTYPE SNAPTYPE PARENT PARENTDG SNAPDATE CHANGED_DATA SYNCED_DATA
data001_vl ora_cdb004_PRDROT_dg vol – – – – – – – 936G (100%)
PFIdata001_vl_c0 ora_cdb004_PRDROT_dg vol fullinst data001_vl ora_cdb004_PRDROT_dg 2010/05/24 22:03 282.3M (0.0%) 936G (100%)
index001_vl ora_cdb004_PRDROT_dg vol – – – – – – – 393G (100%)
PFIindex001_vl_c0 ora_cdb004_PRDROT_dg vol fullinst index001_vl ora_cdb004_PRDROT_dg 2010/05/24 22:03 78M (0.0%) 393G (100%)
dbfra001_vl ora_cdb004_PRDROT_dg vol – – – – – – – 160G (100%)
snap_dbfra001_vl ora_cdb004_PRDROT_dg vol fullinst dbfra001_vl ora_cdb004_PRDROT_dg 2009/03/02 12:55 80.2G (50.2%) 160G (100%)
================================================================================
hans # vxlicrep -s

Symantec License Manager vxlicrep utility version 3.02.16.0
Copyright (C) 1996-2006 Symantec Corporation. All rights reserved.

Creating a report on all VERITAS products installed on this system

License Key = 3GC9-OPK6-S4Z9-KO47-666P-836P-8UFP
Product Name = VERITAS Storage Foundation Standard
License Type = DEMO
Demo End Date = Mon Aug 10 00:00:00 2009
(expired -377.6 days ago).
Key = Invalid, Key EXPIRED -377 days ago

License Key =
Product Name = VERITAS Volume Manager
License Type = DEMO
Demo End Date = Mon Aug 10 00:00:00 2009
(expired -377.6 days ago).
License Key =
Product Name = VERITAS File System
License Type = DEMO
Demo End Date = Mon Aug 10 00:00:00 2009
(expired -377.6 days ago).
License Key = B4EE-XEAO-JTF2-T4OR-UR6P-DCZP-PPPP-P82X-NC
Product Name = VERITAS Volume Manager
License Type = DEMO
Demo End Date = Mon Aug 10 00:00:00 2009
(expired -377.6 days ago).
Key = Invalid, Key EXPIRED -377 days ago

License Key = 3GEV-AA8O-R66H-8USL-4O43-J6PP-ZCP3
Product Name = VERITAS File System
License Type = DEMO
Demo End Date = Mon Aug 10 00:00:00 2009
(expired -377.6 days ago).
Key = Invalid, Key EXPIRED -377 days ago

Issue: VxVM vxdmpadm ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible

bash-2.03# uname -a
SunOS hans 5.8 Generic_117350-44 sun4u sparc SUNW,Sun-Fire-V440
bash-2.03# uptime
3:42am up 200 day(s), 1:46, 4 users, load average: 5.61, 5.32, 3.95
bash-2.03# modinfo | grep -i vx
21 10218123 1b4f4 236 1 vxdmp (VxVM 3.5s_p3.5 DMP Driver)
22 102310b7 11b6a8 237 1 vxio (VxVM 3.5s_p3.5 I/O driver)
24 103378a2 80f 238 1 vxspec (VxVM 3.5s_p3.5 control/status)
133 78457663 a5b 239 1 vxportal (VxFS 3.5_REV-MP3d portal driver)
134 784dc000 1103cd 16 1 vxfs (VxFS 3.5_REV-MP3d,PID=113206-11)
bash-2.03#
vxconfigd is not running ———————>
bash-2.03# ps -eaf | grep -i vx
root 569 1 0 Jul 20 ? 6:39 /opt/VRTSob/bin/vxsvc -r /opt/VRTSob/config/Registry
bash-2.03#

bash-2.03# vxdctl mode
mode: enabled
bash-2.03# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c1t0d0s2 sliced – – error
c1t1d0s2 sliced disk01 rootdg online
c1t2d0s2 sliced – – error
c1t3d0s2 sliced disk02 rootdg online
c4t17d207s2 sliced hanss19 hanssandg online
c4t17d208s2 sliced hanss20 hanssandg online
c4t17d209s2 sliced hanss21 hanssandg online
c6t18d207s2 sliced – – online
c6t18d208s2 sliced – – online
c6t18d209s2 sliced – – online
bash-2.03#
bash-2.03# vxconfigd -k -m disable -x syslog
bash-2.03# ps -eaf |grep vx
root 569 1 0 Jul 20 ? 6:39 /opt/VRTSob/bin/vxsvc -r /opt/VRTSob/config/Registry
root 24668 1 1 03:44:36 ? 0:00 vxconfigd -k -m disable -x syslog
bash-2.03# vxdctl init
bash-2.03# vxdctl initdmp
bash-2.03# vxdctl enable
bash-2.03# vxdctl mode
mode: enabled

Disk Errors

1)
vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none – – online invalid
c2t0d0s2 auto:none – – online invalid
c2t6d0s2 auto:none – – online invalid
fabric_50 auto:cdsdisk fabric_11 ocsrawdg online shared
. . .
fabric_78 auto:cdsdisk fabric_28 ocsrawdg online shared
fabric_79 auto – – error
fabric_80 auto:cdsdisk – – online

for online invalid —> not intialized in VXVM
for error

check :

# vxdisk -e list |egrep ‘fabric_79|fabric_80’
# prtvtoc /dev/vx/rdmp/fabric_79
# prtvtoc /dev/vx/rdmp/fabric_80
# vxdisk list fabric_79
# vxdisk list fabric_80
# vxdmpadm listenclosure all
# vxdmpadm listctlr all

know the SF version you are using ?
# modinfo |grep -i vx

Also give a try on these steps:
— since fabric_79 is a fresh disk, I hope it doesn’t have any data…. so delete slice 6 using format utility
— Label the disk using format utility after deleting slice 6
— rescan OS tree using “devfsadm -Cv” (notice any errors)
— rescan veritas tree using “vxdctl enable”
— Now see if disk still shows in error state or no..
1. Ensure the event source daemon is not running so it won’t recreate disk while you’re trying to cleanup
# ps -ef |grep vxesd
If it is running, stop it
# vxddladm stop eventsource
# ps -ef |grep vxesd
2. Remove disks from vxdisk list and the underlying dmp devices
# vxdisk rm fabric_79
# ls -la /dev/vx/*dmp/fabric_79* ### ensure this just lists the fabric_79 devices/slices
# rm /dev/vx/*dmp/fabric_79*
# ls -la /dev/vx/*dmp/fabric_79* ### should not find anything
3. Relabel as EFI
# format -e c8t60A98000486E5A7153345A4471373748d0
format> label
[will give you option for SMI or EFI label. select EFI label, follow prompts]
format> q
# prtvtoc /dev/rdsk/c8t60A98000486E5A7153345A4471373748d0s0
### should now see slice 8 for EFI label
4. Now this disk has correct label, rebuild dmp dev tree, rescan into vxvm
# vxdctl initdmp
# vxdctl enable
# vxdisk list
format> label
[0] SMI Label
[1] EFI Label
Specify Label type[0]: 1
Warning: This disk has an SMI label. Changing to EFI label will erase all
current partitions.
Continue? y
format> q