deleting rlink that's having "secondary_config_err" flag
hello, in my VCS global cluster my ORAGrp resource group is partially online since my rvgres is offline, i am suspecting the issue in the below rlink. i am trying to dissociate thi rlink(below:rlk_sys1-DB-rep_DB_r) and dettach it in order to delete it but i am not able to succeed. below are some output from the system. root@sys2# vxprint -P Disk group: DBhrDG TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 rl rlk_sys1-DB-rep_DB_r DB_rvg CONNECT - - ACTIVE - - rl rlk_sys1-rep_DB-rvg DB-rvg ENABLED - - PAUSE - - root@sys2# vxrlink -g DBhrDG dis rlk_sys1-rep_DB-rvg VxVM VVR vxrlink ERROR V-5-1-3520 Rlink rlk_sys1-rep_DB-rvg can not be dissociated if it is attached root@sys2# vxrlink -g DBhrDG det rlk_sys1-rep_DB-rvg VxVM VVR vxrlink ERROR V-5-1-10128 Operation not allowed with attached rlinks root@sys2# vxedit -g DBhrDG rm rlk_sys1-rep_DB-rvg VxVM vxedit ERROR V-5-1-3540 Rlink rlk_sys1-rep_DB-rvg is not disabled, use -f flag root@sys2# vxedit -g DBhrDG -f rm rlk_sys1-rep_DB-rvg VxVM vxedit ERROR V-5-1-3541 Rlink rlk_sys1-rep_DB-rvg is not dissociated root@sys2# vxprint -Vl Disk group: DBhrDG Rvg: DB-rvg info: rid=0.1317 version=0 rvg_version=41 last_tag=11 state: state=CLEAN kernel=DISABLED assoc: datavols=(none) srl=(none) rlinks=rlk_sys1-rep_DB-rvg exports=(none) vsets=(none) att: rlinks=rlk_sys1-rep_DB-rvg flags: closed secondary disabled detached passthru logging device: minor=26012 bdev=343/26012 cdev=343/26012 path=/dev/vx/dsk/DBhrDG/DB-rvg perms: user=root group=root mode=0600 Rvg: DB_rvg info: rid=0.1386 version=13 rvg_version=41 last_tag=12 state: state=ACTIVE kernel=ENABLED assoc: datavols=sys1_DB_Process,sys1_DB_Script,... srl=sys1_DB_SRL rlinks=rlk_sys1-DB-rep_DB_r exports=(none) vsets=(none) att: rlinks=rlk_sys1-DB-rep_DB_r flags: closed secondary enabled attached logging device: minor=26014 bdev=343/26014 cdev=343/26014 path=/dev/vx/dsk/DBhrDG/DB_rvg perms: user=root group=root mode=0600 please advise regards1.5KViews0likes4CommentsVXVM gives trouble in solaris11.2
Hi, I have installed VXVM6.0.1SF with trial version on Solaris11.2 inVMWare workstation. While installing the installer asked to set lwp_default and stksize to 0x8000. I have done it and completed installation successfully without any issue. After reboot also no issue. But if i give df -h command then immediately system going to kernel panic and starts rebooting and while booting it throws warning in lwp_default and stksize. Also i can see logs to run the vxkeyless setnone. This also done. Need any work around to fix this issue. Regards, vinothtvSolved1.3KViews1like1CommentReplacing/Restoring Failed Drive
Yestarday, I had two drives in my storage san fail. The san monitor reports that all the physical drives are fine. bash-2.03# vxdisk list | grep AMS AMS_WMS0_0 auto:cdsdisk remote996006 remote9960 online AMS_WMS0_1 auto:cdsdisk remote996004 remote9960 online AMS_WMS0_2 auto:cdsdisk remote996013 remote9960 online AMS_WMS01_0 auto - - error AMS_WMS01_1 auto - - error AMS_WMS01_2 auto:cdsdisk remote996012 remote9960 online AMS_WMS012_0 auto:cdsdisk remote996008 remote9960 online AMS_WMS012_1 auto:cdsdisk remote996002 remote9960 online AMS_WMS012_2 auto:cdsdisk remote996011 remote9960 online AMS_WMS0123_0 auto:cdsdisk remote996007 remote9960 online AMS_WMS0123_1 auto:cdsdisk remote996001 remote9960 online AMS_WMS0123_2 auto:cdsdisk remote996010 remote9960 online - - remote996003 remote9960 failed was:AMS_WMS01_1 - - remote996005 remote9960 failed was:AMS_WMS01_0 The devices on lines 5/6 are new. A result of me attempting to repair the two failed drives at the bottom. So far i've unmounted the volumes associated with the drives, but there are 11 more mounts attached to the Disk Group. Being new, I'm not sure what processes and systems are using those volumes and am reluctant to unmount them at the moment. I followed several guides trying to determine the cause of the problem and/or to restore the two disks. Here's some of the results of my effort so far. > vxprint -htg remote9960 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 NVOLUME KSTATE STATE 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 dg remote9960 default default 126000 1032204684.1590.aeneas dm remote996001 AMS_WMS0123_1 auto 2048 1677616896 - dm remote996002 AMS_WMS012_1 auto 2048 1677616896 - dm remote996003 - - - - NODEVICE dm remote996004 AMS_WMS0_1 auto 2048 1677616896 - dm remote996005 - - - - NODEVICE dm remote996006 AMS_WMS0_0 auto 2048 1677616896 - dm remote996007 AMS_WMS0123_0 auto 2048 1258212096 - dm remote996008 AMS_WMS012_0 auto 2048 1258212096 - dm remote996010 AMS_WMS0123_2 auto 2048 2094367888 - dm remote996011 AMS_WMS012_2 auto 2048 2094367888 - dm remote996012 AMS_WMS01_2 auto 2048 2094367888 - dm remote996013 AMS_WMS0_2 auto 2048 2094367888 - v rem-01 - DISABLED ACTIVE 1921724416 SELECT - fsgen pl rem-01-02 rem-01 DISABLED NODEVICE 1921843200 STRIPE 4/64 RW sd remote996004-01 rem-01-02 remote996004 36096 480460800 0/0 AMS_WMS0_1 ENA sd remote996003-01 rem-01-02 remote996003 36096 480460800 1/0 - NDEV sd remote996002-01 rem-01-02 remote996002 36096 480460800 2/0 AMS_WMS012_1 ENA sd remote996001-01 rem-01-02 remote996001 36096 480460800 3/0 AMS_WMS0123_1 ENA v rem-02 - DISABLED ACTIVE 1921724416 SELECT - fsgen pl rem-02-02 rem-02 DISABLED NODEVICE 1921843200 STRIPE 4/64 RW sd remote996004-02 rem-02-02 remote996004 480496896 480460800 0/0 AMS_WMS0_1 ENA sd remote996003-02 rem-02-02 remote996003 480496896 480460800 1/0 - NDEV sd remote996002-02 rem-02-02 remote996002 480496896 480460800 2/0 AMS_WMS012_1 ENA sd remote996001-02 rem-02-02 remote996001 480496896 480460800 3/0 AMS_WMS0123_1 ENA v rem-03 - DISABLED ACTIVE 1000341504 SELECT - fsgen pl rem-03-01 rem-03 DISABLED NODEVICE 1000396800 STRIPE 2/64 RW sd remote996006-02 rem-03-01 remote996006 106826496 419443200 0/0 AMS_WMS0_0 ENA sd remote996008-03 rem-03-01 remote996008 1176381696 80755200 0/419443200 AMS_WMS012_0 ENA sd remote996005-02 rem-03-01 remote996005 106826496 419443200 1/0 - NDEV sd remote996007-03 rem-03-01 remote996007 1176381696 80755200 1/419443200 AMS_WMS0123_0 ENA v rem-04 - DISABLED ACTIVE 1921724416 SELECT - fsgen pl rem-04-02 rem-04 DISABLED NODEVICE 1921843200 STRIPE 4/64 RW sd remote996004-03 rem-04-02 remote996004 960957696 480460800 0/0 AMS_WMS0_1 ENA sd remote996003-03 rem-04-02 remote996003 960957696 480460800 1/0 - NDEV sd remote996002-03 rem-04-02 remote996002 960957696 480460800 2/0 AMS_WMS012_1 ENA sd remote996001-03 rem-04-02 remote996001 960957696 480460800 3/0 AMS_WMS0123_1 ENA v rem-08 - ENABLED ACTIVE 2097152000 SELECT rem-08-01 fsgen pl rem-08-01 rem-08 ENABLED ACTIVE 2097177600 STRIPE 2/64 RW sd remote996008-01 rem-08-01 remote996008 36096 1048588800 0/0 AMS_WMS012_0 ENA sd remote996007-01 rem-08-01 remote996007 36096 1048588800 1/0 AMS_WMS0123_0 ENA v rem-30 - DISABLED ACTIVE 1887436800 SELECT - fsgen pl rem-30-01 rem-30 DISABLED NODEVICE 1887436800 STRIPE 2/64 RW sd remote996006-03 rem-30-01 remote996006 526269696 943718400 0/0 AMS_WMS0_0 ENA sd remote996005-03 rem-30-01 remote996005 526269696 943718400 1/0 - NDEV v rem-40 - ENABLED ACTIVE 2097152000 SELECT rem-40-01 fsgen pl rem-40-01 rem-40 ENABLED ACTIVE 2097254400 STRIPE 4/64 RW sd remote996013-01 rem-40-01 remote996013 36096 524313600 0/0 AMS_WMS0_2 ENA sd remote996012-01 rem-40-01 remote996012 36096 524313600 1/0 AMS_WMS01_2 ENA sd remote996011-01 rem-40-01 remote996011 36096 524313600 2/0 AMS_WMS012_2 ENA sd remote996010-01 rem-40-01 remote996010 36096 524313600 3/0 AMS_WMS0123_2 ENA v rem-41 - ENABLED ACTIVE 2097152000 SELECT rem-41-01 fsgen pl rem-41-01 rem-41 ENABLED ACTIVE 2097254400 STRIPE 4/64 RW sd remote996013-02 rem-41-01 remote996013 524349696 524313600 0/0 AMS_WMS0_2 ENA sd remote996012-02 rem-41-01 remote996012 524349696 524313600 1/0 AMS_WMS01_2 ENA sd remote996011-02 rem-41-01 remote996011 524349696 524313600 2/0 AMS_WMS012_2 ENA sd remote996010-02 rem-41-01 remote996010 524349696 524313600 3/0 AMS_WMS0123_2 ENA v rem-42 - ENABLED ACTIVE 2097152000 SELECT rem-42-01 fsgen pl rem-42-01 rem-42 ENABLED ACTIVE 2097254400 STRIPE 4/64 RW sd remote996013-03 rem-42-01 remote996013 1048663296 524313600 0/0 AMS_WMS0_2 ENA sd remote996012-03 rem-42-01 remote996012 1048663296 524313600 1/0 AMS_WMS01_2 ENA sd remote996011-03 rem-42-01 remote996011 1048663296 524313600 2/0 AMS_WMS012_2 ENA sd remote996010-03 rem-42-01 remote996010 1048663296 524313600 3/0 AMS_WMS0123_2 ENA v rem-43 - ENABLED ACTIVE 2085427200 SELECT rem-43-01 fsgen pl rem-43-01 rem-43 ENABLED ACTIVE 2085427200 STRIPE 4/64 RW sd remote996013-04 rem-43-01 remote996013 1572976896 521356800 0/0 AMS_WMS0_2 ENA sd remote996012-04 rem-43-01 remote996012 1572976896 521356800 1/0 AMS_WMS01_2 ENA sd remote996011-04 rem-43-01 remote996011 1572976896 521356800 2/0 AMS_WMS012_2 ENA sd remote996010-04 rem-43-01 remote996010 1572976896 521356800 3/0 AMS_WMS0123_2 ENA v rimg02 - DISABLED ACTIVE 944793600 SELECT - fsgen pl rimg02-01 rimg02 DISABLED NODEVICE 944793600 STRIPE 4/64 RW sd remote996004-04 rimg02-01 remote996004 1441418496 236198400 0/0 AMS_WMS0_1 ENA sd remote996003-04 rimg02-01 remote996003 1441418496 236198400 1/0 - NDEV sd remote996002-04 rimg02-01 remote996002 1441418496 236198400 2/0 AMS_WMS012_1 ENA sd remote996001-04 rimg02-01 remote996001 1441418496 236198400 3/0 AMS_WMS0123_1 ENA > dxadm Select an operation to perform: 5 Select a removed or failed disk [<disk>,list,q,?] remote996003 VxVM ERROR V-5-2-1985 No devices are available as replacements for remote996003. Select a removed or failed disk [<disk>,list,q,?] remote996005 VxVM ERROR V-5-2-1985 No devices are available as replacements for remote996005. I attemped to reattached the failed disk: bash-2.03# /etc/vx/bin/vxreattach -c remote996003 VxVM vxdisk ERROR V-5-1-537 Device remote996003: Not in the configuration VxVM vxdisk ERROR V-5-1-558 Disk remote996003: Disk not in the configuration bash-2.03# /etc/vx/bin/vxreattach -c remote996005 VxVM vxdisk ERROR V-5-1-537 Device remote996005: Not in the configuration VxVM vxdisk ERROR V-5-1-558 Disk remote996005: Disk not in the configuration bash-2.03# vxdisk clearimport AMS_WMS01_1 VxVM vxdisk ERROR V-5-1-531 Device AMS_WMS01_1: clearimport failed: Disk device is offline I think this part is where I created the two duplicate devices. From this point, I'm going to have to step back and seek out guidance before I cause further problems.Solved2.8KViews0likes6CommentsSFHA Solutions 6.2: Symantec Storage plug-in for OEM 12c
Symantec Storage plug-in for OEM12c enables you to view and manage the Storage Foundation and VCS objects through the Oracle Enterprise Manager 12c (OEM), which has a graphical interface. It works with the Symantec Storage Foundation and High Availability 6.2 product suite. The Symantec Storage plug-in allows you to: SmartIO: manage Oracle database objects using SmartIO. Snapshot: create point-in-time copies (Storage Checkpoint, Database FlashSnap, Space-optimized Snapshot, and FileSnap) of Oracle databases using SFDB features Cluster: vew cluster-specific information. You can get the plug-in by downloading the attached file. For more information about installing and using the plug-in, download the attached Application Note. Terms of use for this information are found in Legal Notices.3.1KViews1like0CommentsHow to use fsdb to repair VxFS file system?
The symantec offcial Manaul page of fsdb command is very simple with little information about its usage. Is there any guide to use fsdb command on all OS platform (i.e. AIX, HPUX ,Linux etc...) ? How to use fsdb to repair VxFS file system? My ultimate question is how to repair VxFS file system when it's damaged using fsdb and all other relevant command tools? Thanks in advance !Solved1.7KViews0likes2CommentsHow to extend Disk in VXVM
HI, I have 1 Lun with size 120GB, on that LUN we have 1 Disk group with 4 DB volume, now i want to extend the size of "DISK" not DG nor Volume.Can i extend Disk size from 120 G B to 200 GB??? If yes, thn please share POA also... Thanks in Advance...Solved2.2KViews0likes5CommentsStorage Migration
Hi, We are planning for storage Migration from EMC utility 2 to utility 3 storage, all the filesystem are vxfs we are planning to mirror the old disk and new disk and sync the data and remove the old disk from mirror. Whether the new LUN size should be the same for creating the mirror and sync the data.Solved1.4KViews0likes4CommentsCollection from VRTSexplorer
Dear All I have some enviornments of SFHA and VCS installed on Linux and Solaris servers. I have output of VRTSexplorer logs for every system. As the VRTSexplorer contains almost everything collected, I wanted to know if is it possible to get the following output of these requirements 1. Which license and version and sub-version is installed on system? like for example if version 5.0 is installed which patch version is installed ? I want something except "vxlicrep" 2. If in the case of Replication, which file will give output of Bandwidth limit if it is configured. 3. If in the case of Replication, which file will give output of packet size if it is configured. Any suggession will be appreciated. Assume I just have VRTSexplorer and investigating logs and need to know the following. Regards2.2KViews0likes4CommentsMount HP-UX VXFS 6 filesystem on Redhat Linux Server?
Here goes: I have a need to migrate a numebr of large files from several servers to a linux based system from HP-UX 11.23. The data resides on VXFS version 6 filesystems on san storage. I have found LVM tools that allow me to make the MVM structures visible as disks that show up in device mapper on the linux side and I can run strings and dd on the luns and they SEEM to contain the appropriate data. The data itself is in Intersystems Cache database chunks. If I can get the actual files copied over, I can do an endian conversion on them and start using them immediately in the new environment. My problem is transport. I have several 32 GB file that need to be moved and while I haven't done time tests, I am assuming the actual migration time may be prohibitive. I have downloaded a trial of Storage Essentials and installed it on the linux server, but after I make the logical volume visible, I getthe following error when trying to perform the mount: UX:vxfs mount.vxfs: ERROR: V-3-25584: /dev/mapper/vg1220625654-lvol1 is not a supported device UX:vxfs mount.vxfs: ERROR: V-3-24996: Unable to get disk layout version Any help is appreciated. I have been searching high and low on the web, but can't seem to find any current threads about this. There are some older ones about freevxfs that used toexist for linux, but they all said it doesn't work with newer versions of vxfs filesystems. Thanks!Solved2.7KViews1like2Comments