How to check Multipath in veritas

1. Check What is Enclosure name from storage in server

root# vxdmpadm listctlr all
CTLR-NAME ENCLR-TYPE STATE ENCLR-NAME
=====================================================
c1 Disk ENABLED Disk
c0 Disk ENABLED Disk
c5 TagmaStore-USP ENABLED TagmaStore-USP1
c2 TagmaStore-USP ENABLED TagmaStore-USP1
c5 TagmaStore-USP ENABLED TagmaStore-USP0
c2 TagmaStore-USP ENABLED TagmaStore-USP0

2. Check multipath a disk, if PATHS =4 that indicates a disk already multipath, if PATHS = 2 that is single path.


root# vxdmpadm getdmpnode enclosure=TagmaStore-USP0
NAME STATE ENCLR-TYPE PATHS ENBL DSBL ENCLR-NAME
=========================================================================
c2t50060E80047F6B41d8s2 ENABLED TagmaStore-USP 4 4 0 TagmaStor e-USP0
c2t50060E80047F6B41d11s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B45d16s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B45d15s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B41d1s2 ENABLED TagmaStore-USP 4 4 0 TagmaStor e-USP0
c2t50060E80047F6B41d3s2 ENABLED TagmaStore-USP 4 4 0 TagmaStor e-USP0
c5t50060E80047F6B55d7s2 ENABLED TagmaStore-USP 4 4 0 TagmaStor e-USP0
c2t50060E80047F6B45d17s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d19s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B41d13s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B41d42s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d30s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d18s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B45d14s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B41d43s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B41d2s2 ENABLED TagmaStore-USP 4 4 0 TagmaStor e-USP0
c5t50060E80047F6B51d34s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B41d4s2 ENABLED TagmaStore-USP 4 4 0 TagmaStor e-USP0
c2t50060E80047F6B41d9s2 ENABLED TagmaStore-USP 4 4 0 TagmaStor e-USP0
c2t50060E80047F6B41d10s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B41d5s2 ENABLED TagmaStore-USP 4 4 0 TagmaStor e-USP0
c5t50060E80047F6B55d48s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B45d46s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B41d6s2 ENABLED TagmaStore-USP 4 4 0 TagmaStor e-USP0
c5t50060E80047F6B51d23s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d20s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d27s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d21s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B41d12s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d24s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d25s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d29s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d28s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B45d44s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d37s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d40s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d32s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B41d0s2 ENABLED TagmaStore-USP 4 4 0 TagmaStor e-USP0
c5t50060E80047F6B51d38s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d35s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B45d47s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d22s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B45d52s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B45d45s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d33s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B45d50s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d26s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B45d49s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d31s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d39s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d36s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c5t50060E80047F6B51d41s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
c2t50060E80047F6B45d51s2 ENABLED TagmaStore-USP 4 4 0 TagmaSto re-USP0
root#

3. A disk already multipath, done
Read More..

Removing Volume, disk and disk group Veritas

1. Umount Filesystem
/dev/vx/dsk/datadg/oravl01 5.0G 18M 4.7G 1% /data1/oravl01

root # umount /data1/data1

2. remove the volume
root # vxassist -g datadg remove volume oravl01

3. Observe this disk group configuration information
root # vxprint -g datadg -htr


4.Destroy the datadg disk group
root# vxdg destroy datadg

5. observe the status of the disk device
root # vxdisk -o alldgs list

done
Read More..

VxVM vxdisksetup ERROR V-5-2-0

How to change Type auto:SVM to auto:cdsdisk in veritas.

1. Check disk
root # vxdisk list
DEVICE TYPE DISK GROUP STATUS
disk_0 auto:none - - online invalid
disk_1 auto:none - - online invalid
disk_2 auto:cdsdisk datakudg01 datakudg online
disk_3 auto:SVM - - SVM
disk_4 auto:cdsdisk datadg01 datadg online

2. Try initialized disk_3 under SVM to veritas
root # /etc/vx/bin/vxdisksetup -i disk_3
VxVM vxdisksetup ERROR V-5-2-0 Disk disk_3 is in use by SVM. Slice(s) 2 and 6 contain SVM (or former) metadata.
If you still want to initialize this device for VxVM use, please delete the metadata by running 'metadb' command if it is still active, and then remove the SVM signature from each of these slice(s) as follows:
dd if=/dev/zero of=/dev/vx/rdmp/disk_3s[n] oseek=16 bs=512 count=1
[n] is the slice number.


For solve this case :
1. using dd command
root # dd if=/dev/zero of=/dev/vx/rdmp/disk_3s2 oseek=16 bs=512 count=1
1+0 records in
1+0 records out

2. Try to initialize
root # /etc/vx/bin/vxdisksetup -i disk_3

3. Check status disk
vxdisk list
DEVICE TYPE DISK GROUP STATUS
disk_0 auto:none - - online invalid
disk_1 auto:none - - online invalid
disk_2 auto:cdsdisk datakudg01 datakudg online
disk_3 auto:cdsdisk - - online
disk_4 auto:cdsdisk datadg01 datadg online

done
Read More..

Adding size volume existing in veritas

Today i have request from customer for add size mountpoint in veritas environment, Ok lets begin..

Name Disk Group : serverdg
Name Volume : logging

1. Check free size in disk group serverdg

root # vxassist -g serverdg maxsize
Maximum volume size: 472766464 (230843Mb)

2. Add size 5 Gb as requested by user
root # vxresize -g rb34dg log 5g
UX:vxfs fsadm: ERROR: V-3-23544: sectors must be >= 62914561 as they are currently in use.
VxVM vxresize ERROR V-5-1-7514 Problem running fsadm command for volume log, in diskgroup serverdg
root #
Based on the description on the web Symantec, error V-3-23544 (The vxresize command will produce the V-3-23544 error message when the target size is too small for file space currently in use.) resolution : Adjust the resize command plus '+' sign.

root # vxresize -g rb34dg log +5g
UX:vxfs fsadm: ERROR: V-3-20340: attempt to resize /dev/vx/rdsk/serverdg/logging failed with errno 28
UX:vxfs fsadm: ERROR: V-3-23643: Retry the operation after freeing up some space
VxVM vxresize ERROR V-5-1-7514 Problem running fsadm command for volume log, in diskgroup serverdg
root #

ehm..check size filesystem :
root # df -h | grep log
/dev/vx/dsk/serverdg/logging 30G 30G 0K 100% /productions/var/log

ok..for solving this case, first must be clean up filesystem until below 100% from application customer side..after that execute again a command vxresize.
root # vxresize -g rb34dg log +5g
root #
root # df -h | grep log
/dev/vx/dsk/serverdg/logging 35G 30G 5.3G 85% /productions/var/log Read More..