Some VCS plexes disabled after power outage
Hi all, I'm running the Veritas Storage Foundation Standard HA 5.0MP3 under Suse Linux Enterprise Server 11 on two Oracle X6270 servers. There was a power outage, causing an immediate brutal shutdown of both servers. After power was restored, the server on which the Oracle service group was active ("db1-hasc") could not boot at all (mainboard failure). The other server ("db2-hasc") booted, but reported during boot that cluster cannot start, and that manual reseeding might be needed to start it, so I started the cluster from the working server db2-hasc using command gabconfig -x (found it after some googling). In the meantime, the failed server db1-hasc was fixed and cluster is now working (all service groups online, but on the db2-hasc, the one which started successfully after power outage). No attempt has been made yet to try to switchover any of the service groups (except network service groups which are online) to the db1-hasc server. However, I have noticed some problems with several volumes in disk group "oracledg": db2-hasc# vxprint -g oracledg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg oracledg oracledg - - - - - - dm oracled01 - - - - NODEVICE - - dm oracled02 sdb - 335462144 - - - - v archvol fsgen ENABLED 62914560 - ACTIVE - - pl archvol-01 archvol DISABLED 62914560 - NODEVICE - - sd oracled01-02 archvol-01 DISABLED 62914560 0 NODEVICE - - pl archvol-02 archvol ENABLED 62914560 - ACTIVE - - sd oracled02-02 archvol-02 ENABLED 62914560 0 - - - v backupvol fsgen ENABLED 167772160 - ACTIVE - - pl backupvol-01 backupvol DISABLED 167772160 - NODEVICE - - sd oracled01-03 backupvol-01 DISABLED 167772160 0 NODEVICE - - pl backupvol-02 backupvol ENABLED 167772160 - ACTIVE - - sd oracled02-03 backupvol-02 ENABLED 167772160 0 - - - v dbovol fsgen ENABLED 62914560 - ACTIVE - - pl dbovol-01 dbovol DISABLED 62914560 - NODEVICE - - sd oracled01-01 dbovol-01 DISABLED 62914560 0 NODEVICE - - pl dbovol-02 dbovol ENABLED 62914560 - ACTIVE - - sd oracled02-01 dbovol-02 ENABLED 62914560 0 - - - db2-hasc# vxprint -htg oracledg DG NAME NCONFIG NLOG MINORS GROUP-ID ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK CO NAME CACHEVOL KSTATE STATE VT NAME RVG KSTATE STATE NVOLUME V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE DC NAME PARENTVOL LOGVOL SP NAME SNAPVOL DCO EX NAME ASSOC VC PERMS MODE STATE SR NAME KSTATE dg oracledg default default 0 1265259474.12.db1-HASc dm oracled01 - - - - NODEVICE dm oracled02 sdb auto 65536 335462144 - v archvol - ENABLED ACTIVE 62914560 SELECT - fsgen pl archvol-01 archvol DISABLED NODEVICE 62914560 CONCAT - WO sd oracled01-02 archvol-01 oracled01 62914560 62914560 0 - NDEV pl archvol-02 archvol ENABLED ACTIVE 62914560 CONCAT - RW sd oracled02-02 archvol-02 oracled02 62914560 62914560 0 sdb ENA v backupvol - ENABLED ACTIVE 167772160 SELECT - fsgen pl backupvol-01 backupvol DISABLED NODEVICE 167772160 CONCAT - WO sd oracled01-03 backupvol-01 oracled01 125829120 167772160 0 - NDEV pl backupvol-02 backupvol ENABLED ACTIVE 167772160 CONCAT - RW sd oracled02-03 backupvol-02 oracled02 125829120 167772160 0 sdb ENA v dbovol - ENABLED ACTIVE 62914560 SELECT - fsgen pl dbovol-01 dbovol DISABLED NODEVICE 62914560 CONCAT - WO sd oracled01-01 dbovol-01 oracled01 0 62914560 0 - NDEV pl dbovol-02 dbovol ENABLED ACTIVE 62914560 CONCAT - RW sd oracled02-01 dbovol-02 oracled02 0 62914560 0 sdb ENA Does anyone have some ideas on how to recover the disabled plexes/subdisks? Or which other commands to run to ascertain the current state of the cluster, in order to have a clear(er) picture what is wrong and which steps to take to remedy the problem? If so, I would appreciate if you can share any tips/suggestions. The physical disks seem fine (no errors reported in ILOM diagnostics). Thanks, /HrvojeSolved2.2KViews4likes9Commentswould vxvm mirroring activities take lower priority than normal write activity before it is synced up?
hi, I have a question here, hoping someone could point out perhaps. is a vxvm mirroring event (before it is sync-ed up) takes lower priority than a normal I/O data write? the reason I am asking is because if during vxvm mirror setup, would it slow down normal data I/O it would make sense to lower the priority of these writes than normal data I/O I would think. thanks in advance.Solved868Views3likes1Commentunable to remove a disabled dmp path without reboot on solaris 10
here is my problem, i have a dmpnode, and one of the 2 WWN has been rearranged from the array side. so it generated the some disabled paths. my problem is how to remove these disabled paths without disrupting the current vxfs mounts. at the moment, cfgadm sees these paths as failing even though format sees them as offline. luxadm -e offline $path didn't help.4KViews3likes6CommentsTroubleshooting volume performance in Storage Foundation
Hi, all. We have released a set of articles about troubleshooting volume performance in Storage Foundation. Here is the link: "Troubleshooting volume performance in Veritas Storage Foundation" http://www.symantec.com/docs/TECH202712 Since this is a broad topic, the "technote" is actually a set of about a dozen article that have been organized into a logical tree structure, with TECH202712 at its "root." Let us know what you think! Regards, Mike755Views3likes0CommentsVxFS volume wont go online
Hello, I create a SAN volume and want to create a VxFS volume but the volume manager disables the device again and again. Apr 30 15:41:20 cassia last message repeated 1 time Apr 30 15:41:22 cassia vxdmp: [ID 736771 kern.notice] NOTICE: VxVM vxdmp V-5-0-148 enabled path 31/0x240 belonging to the dmpnode 205/0x40 Apr 30 15:41:22 cassia vxdmp: [ID 899070 kern.notice] NOTICE: VxVM vxdmp V-5-0-147 enabled dmpnode 205/0x40 Apr 30 15:41:22 cassia vxdmp: [ID 480808 kern.notice] NOTICE: VxVM vxdmp V-5-0-112 disabled path 31/0x240 belonging to the dmpnode 205/0x40 due to open failure Apr 30 15:41:22 cassia vxdmp: [ID 824220 kern.notice] NOTICE: VxVM vxdmp V-5-0-111 disabled dmpnode 205/0x40 Apr 30 15:41:23 cassia vxdmp: [ID 275047 kern.notice] NOTICE: VxVM vxdmp V-5-3-1062 dmp_restore_node: Unstable path 31/0x240 will not be available for I/O until 300 seconds Apr 30 15:41:23 cassia vxdmp: [ID 238993 kern.notice] NOTICE: VxVM vxdmp 0 dmp_tur_temp_pgr: open failed: error = 6 dev=0xcd/0x42 Apr 30 15:41:23 cassia vxdmp: [ID 954821 kern.notice] NOTICE: VxVM vxdmp V-5-3-1061 dmp_restore_node: The path 31/0x240 has not yet aged - 299 Apr 30 15:41:23 cassia last message repeated 1 time It is a Solaris box. What could be the cause? Cheers Marlen3.3KViews3likes5CommentsIssue while Extending file system in vxvm
Hi, I have a case as below, Please extend below file systems from 30G to 50G on server island. /dev/vx/dsk/VRP_PRD_ora_data_dg/sapdata2 30G 15G 14G 52% /oracle/VRP/sapdata2 /dev/vx/dsk/VRP_PRD_ora_data_dg/sapdata4 30G 15G 14G 51% /oracle/VRP/sapdata4 /dev/vx/dsk/VRP_PRD_ora_data_dg/sapdata1 30G 14G 15G 49% /oracle/VRP/sapdata1 /dev/vx/dsk/VRP_PRD_ora_data_dg/sapdata3 30G 27G 2.7G 91% /oracle/VRP/sapdata3 root@myers# vxdisk -o alldgs -e list DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR emcpower22s2 auto VRP_PRD_sapcent_dg01 VRP_PRD_sapcent_dg online emcpower22c - emcpower23s2 auto emcpower23s2 VRP_PRD_ora_data_dg online emcpower23c - emcpower24s2 auto emcpower24s2 VRP_PRD_ora_data_dg online emcpower24c - emcpower25s2 auto emcpower25s2 VRP_PRD_ora_data_dg online emcpower25c - emcpower26s2 auto emcpower26s2 VRP_PRD_ora_data_dg online emcpower26c - emcpower27s2 auto emcpower27s2 VRP_PRD_ora_bin_dg online emcpower27c - emcpower28s2 auto VRP_PRD_ora_arch_dg01 VRP_PRD_ora_arch_dg online emcpower28c - ====================================================================================== These are the 4 new luns of 30 GB assigned by Storage. 57. emcpower29e <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@29 58. emcpower30a <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@30 59. emcpower33a <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@33 60. emcpower34b <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@34 ==================================================================== When I tried to label them they are giving errors as, 57. emcpower29e <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@29 58. emcpower30a <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@30 59. emcpower33a <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@33 60. emcpower34b <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@34 Specify disk (enter its number): 57 selecting emcpower29e [disk formatted] Disk not labeled. Label it now? y Warning: error writing VTOC. Warning: no backup labels Write label failed FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> - execute <cmd>, then return =========================================================================== There are 4 luns emcpower29e,emcpower30a,emcpower33a,emcpower34b which is require to initilize it and add them to the VRP_PRD_ora_data_dg diskgroup to increase filesystem to 20 GB more. Shall I have to proceed with the disk initilization in vxvm without labeling it or Please help me to proceed step by step activities required for this. Thanks,Solved3.7KViews2likes24CommentsMigrating VxVM volumes from a V240 to a T4-2 Ldom
Hi all, I have a V240 running Solaris 10U08 with VxVM 6.0.000 that I need to migrate to a Solaris T4-2 Ldom (LDM 3.1). I have loaded the software that is in source onto the LDOM and presented the required SAN LUNs that match source into the guest LDOM but when I try to set up a disk (LUN) in VxVM using vxdisksetup I get: "ERROR V-5-2-43 c0d3: Invalid disk device for vxdisksetup". I have tried using vxdisk init c0d3s2 and get: "Disk sector size is not supported" and tried vxdisk init c0d3s2 format=sliced and get: "Disk VTOC does not list private partition" Don't know xhat else to try !!!1.8KViews2likes8CommentsDMP and MPxIO doubt
All the LUNs are under vxvm. If I want to use MPxIO instead of DMP for those LUNs, what is the proper method to do it? I have seen a method saying that we need to delete dmp/rdmp directories... is it required? Should I disable DMP in any way or I just need to enable MPxIO via stmsboot -e with out disabling DMP ? ?Solved990Views2likes1Commentlibadm.so.1: version `SUNW_1.2' not found
I m new to the vertias volume manager. For practice, I have installed the vxvm on solaris 64 bit os using virtualbox. I have created volume group and trying to format filesystem with vxfs, the below error is getting. can you please fix the issue. still you need any more information please let me know bash-3.00# mkfs -F vxfs /dev/vx/rdsk/dg1/vol1 ld.so.1: mkfs: fatal: libadm.so.1: version `SUNW_1.2' not found (required by file /usr/lib/fs/vxfs/mkfs) ld.so.1: mkfs: fatal: libadm.so.1: open failed: No such file or directory Killed bash-3.00# cat /etc/release Solaris 10 10/08 s10x_u6wos_07b X86 Copyright 2008 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 27 October 2008 bash-3.00# mkfs -F vxfs /dev/vx/rdsk/dg1/vol1 ld.so.1: mkfs: fatal: libadm.so.1: version `SUNW_1.2' not found (required by file /usr/lib/fs/vxfs/mkfs) ld.so.1: mkfs: fatal: libadm.so.1: open failed: No such file or directory Killed bash-3.00# pkginfo -l VRTSvxvm PKGINST: VRTSvxvm NAME: Binaries for VERITAS Volume Manager by Symantec CATEGORY: system ARCH: i386 VERSION: 6.0.100.000,REV=08.01.2012.11.29 BASEDIR: / VENDOR: Symantec Corporation DESC: Virtual Disk Subsystem PSTAMP: 6.0.100.000-GA-2012-08-01 INSTDATE: Apr 18 2013 21:09 HOTLINE: http://www.symantec.com/business/support/assistance_care.jsp STATUS: completely installed FILES: 841 installed pathnames 41 shared pathnames 116 directories 346 executables 425545 blocks used (approx) bash-3.00# !find find / -name libadm.so.1 -print 2>/dev/null /usr/lib/amd64/libadm.so.1 /usr/lib/libadm.so.1 /lib/amd64/libadm.so.1 /lib/libadm.so.1 bash-3.00# cat /etc/release Solaris 10 10/08 s10x_u6wos_07b X86 Copyright 2008 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 27 October 2008 bash-3.00# vxdisk list DEVICE TYPE DISK GROUP STATUS c0d0s2 auto:none - - online invalid c0d1s2 auto:none - - online invalid disk_0 auto:cdsdisk d1 dg1 online disk_1 auto:cdsdisk d2 dg1 online disk_2 auto:none - - online invalid disk_3 auto:none - - online invalid bash-3.00# vxprint -vht Disk group: dg1 V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE DC NAME PARENTVOL LOGVOL SP NAME SNAPVOL DCO EX NAME ASSOC VC PERMS MODE STATE v vol1 - ENABLED ACTIVE 102400 SELECT - fsgen pl vol1-01 vol1 ENABLED ACTIVE 102400 CONCAT - RW sd d1-01 vol1-01 d1 0 102400 0 disk_0 ENA bash-3.00#Solved5.9KViews2likes8Comments