電腦筆記本

VEA can not start in RHEL 6.X

從 Storage Foundation 5.x 起, VEA 已不內含在套件中了，所以需要另外單獨下載安裝
RHEL 6.X 起，預設都是x64了，所以少裝了許多 32bit library
導致了 32bit 的程式 VEA 啟動失敗

原來在 VEA Readme File 裡面都有寫到，真是自己的疏忽
把缺少的 32bit library 補一補就 ok 啦

from Veritas Enterprise Administrator (VEA) Console
VRTSobgui 3.4.30.0 README file

PACKAGE INFORMATION
-----------------------------------
Product : Veritas Enterprise Administrator (VEA) Console
Package : VRTSobgui
Release : 3.4.30.0

SUPPORTED PLATFORMS
-----------------------------------
Operating Systems (OS): Linux
OS Versions : RHEL(3.0,4.0,5.0,5.5,6.0,6.1), SLES(8.0,9.0,10.0,11)

Note: For launching VEA GUI in RHEL 6.0 onwards we need to install 32 bit versions of following packages:

1) libXau-1.0.5-1.el6.i686.rpm
2) libxcb-1.5-1.el6.i686.rpm
3) libX11-1.3-2.el6.i686.rpm
4) libXext-1.1-3.el6.i686.rpm
5) libXi-1.3-3.el6.i686.rpm
6) libXtst-1.0.99.2-3.el6.i686.rpm
7) libXrender-0.9.5-1.el6.i686.rpm
.

VEA reports lun as failing, but "vxdisk list"does not

這狀況偶爾會碰到...
明明 vxdisk, vxprint 檢查都是 ok 沒問題的
VEA GUI 卻顯示 disk 有叉叉...可能是 VEA cache 的問題

如何清除 VEA cache ?

VEA reports lun as failing, but "vxdisk list"does not
http://www.symantec.com/docs/TECH128994

* 關閉 VEA
* 清除 cache
# vxconfigd-k -x cleartempdir

* 重起 VEA
.

SCSI3 PGR operations on a VxDMP dmpnode result in dmp path disablement with RHEL5U8 and later kernels

RHEL 5.8 + SFCFS 一台重開另一台就 hang 住不動到 reboot ...

被這個搞死了，總算找到原因了
Linux Kernel 跑太快，竟然還加了個新的 scsi error type
VxVM 還不認識這個新 error type，導致使用 vxdmp 的 vxfen 出狀況

SCSI3 PGR operations on a VxDMP dmpnode result in dmp path disablement with RHEL5U8 and later kernels
http://www.symantec.com/docs/TECH192940

Problem
SCSI3 PGR (Persistent Group Registrations) operations on a VxDMP (VERITAS Dynamic Multi-Pathing) dmpnode result in VxDMP path disablement.

Side effects of the issue include the following:
• Reservation conflict immediately followed by VxDMP error V-5-0-112, whenever SCSI3 PGR operations are executed on a dmpnode.
      Operations that will issue SCSI3 PGR operation on a dmpnode include:
      - Stopping the cluster with hastop.
      - Issuing `/etc/init.d/vxfen start | stop`.  This command is automatically executed at server boot and shutdown.
      - Deporting a diskgroup that contain disk(s) with registrations or importing a diskgroup with groupreserve option.
• When a node is rebooted. The surviving node(s) may see diskgroups go into dgdisabled state and file system(s) get disabled. If VCS is managing resources you will see resource faults. This occurs because dmp paths and dmpnodes are being disabled as a result of multiple SCSI3 PGR operations.
• When a node is rebooted. The surviving node(s) may get paniced. The panic will be initiated by VxFEN as it is trying to avoid a split brain condition. This occurs because dmp paths and dmpnodes are being disabled as a result of multiple SCSI3 PGR operations, then reenabled by the VxDMP recovery daemon.

Error
kernel: sd 2:0:0:14: reservation conflict
kernel: VxVM vxdmp V-5-0-112 disabled path 66/0x0 belonging to the dmpnode 201/0xd0 due to path failure

Environment
RHEL5U8 running kernel 2.6.18-308.el5 and later
Storage Foundation 5.1 and later or Storage Foundation 6.0, 6.0RP1
VxFEN is configured and enabled with SCSI3 disk based fencing in either raw or dmp mode.
VxDMP is configured.

Cause
RHEL5U8 kernel SCSI layer error handling routine introduced a new error type : ID_NEXUS_FAILURE
This new error type is not handled properly by VxDMP, resulting in dmp paths getting disabled during SCSI3 PGR operations.

Solution
If you are planning to upgrade to RHEL5U8 or are currently running RHEL5U8 kernel 2.6.18-308.el5 or later kernels and are running VxVM 5.1 and later. Symantec recommends installing VxVM5.1SP1RP2P3HF5If you are planning to upgrade to RHEL5U8 or are currently running RHEL5U8 kernel 2.6.18-308.el5 or later kernels and are running VxVM 6.0 or 6.0RP1. Symantec recommends installing VxVM6.0RP1HF1

Workarounds:
Downgrade the kernel to pre RHEL5U8.
Configure vxfenmode in disabled mode.

Note: VERITAS Storage Foundation 6.0.1 will contain the fix and is slated for public release in early September. Rolling patch 5.1SP1RP3 will contain the fix and is slated for public release in early October. Rolling Patch 5.1SP1RP3 will also contain the vxfen patch noted in related articles.
.

Shall I use Zones or LDOMs ?

筆記一下

Shall I use Zones or LDOMs?
By Karoly Vegh on Feb 16, 2012
https://blogs.oracle.com/orasysat/entry/shall_i_use_zones_or

.

How to Create a VxVM Snapshot from a mirror volume

VxVM 的 Volume Instance Snapshot 功能
Require: Storage Foundation Enterprise Version

有三種方式：
* Third-mirror break-off snapshots
* Full-sized snapshots
* Space-optimized snapshots

這兒介紹的就是第一種，範例如下

# vxrpint -th -g dg1

dg dg1          default      default  27000    1253797071.15.t2000

dm dg101        c1t2d0s2     auto     65536    143283520 -
dm dg103        c1t3d0s2     auto     65536    143283520 -

v  oracle_vol   -            ENABLED  ACTIVE   83886080 SELECT    -        fsgen
pl oracle_vol-01 oracle_vol  ENABLED  ACTIVE   83886080 CONCAT    -        RW
sd dg101-03     oracle_vol-01 dg101   41943040 83886080 0         c1t2d0   ENA
pl oracle_vol-02 oracle_vol  ENABLED  ACTIVE   83886080 CONCAT    -        RW
sd dg103-01     oracle_vol-02 dg103   0        83886080 0         c1t3d0   ENA

1. enable FastResync
# vxsnap -g dg1 prepare oracle_vol ndcomirs=1 alloc=dg101

# vxprint -th -g dg1

v  oracle_vol   -            ENABLED  ACTIVE   83886080 SELECT    -        fsgen
pl oracle_vol-01 oracle_vol  ENABLED  ACTIVE   83886080 CONCAT    -        RW
sd dg101-03     oracle_vol-01 dg101   41943040 83886080 0         c1t2d0   ENA
pl oracle_vol-02 oracle_vol  ENABLED  ACTIVE   83886080 CONCAT    -        RW
sd dg103-01     oracle_vol-02 dg103   0        83886080 0         c1t3d0   ENA
dc oracle_vol_dco oracle_vol oracle_vol_dcl
v  oracle_vol_dcl -          ENABLED  ACTIVE   6304     SELECT    -        gen
pl oracle_vol_dcl-01 oracle_vol_dcl ENABLED ACTIVE 6304 CONCAT    -        RW
sd dg101-01     oracle_vol_dcl-01 dg101 125829120 6304  0         c1t2d0   ENA

2. create a break-off snapshot volume
# vxsnap -g dg1 make source=oracle_vol/newvol=SNAP-oracle_vol/plex=oracle_vol-02

# vxprint -th g dg1

v  SNAP-oracle_vol -         ENABLED  ACTIVE   83886080 ROUND     -        fsgen
pl oracle_vol-02 SNAP-oracle_vol ENABLED ACTIVE 83886080 CONCAT   -        RW
sd dg103-01     oracle_vol-02 dg103   0        83886080 0         c1t3d0   ENA
dc SNAP-oracle_vol_dco SNAP-oracle_vol SNAP-oracle_vol_dcl
v  SNAP-oracle_vol_dcl -     ENABLED  ACTIVE   6304     SELECT    -        gen
pl SNAP-oracle_vol_dcl-01 SNAP-oracle_vol_dcl ENABLED ACTIVE 6304 CONCAT - RW
sd dg103-02     SNAP-oracle_vol_dcl-01 dg103 83886080 6304 0      c1t3d0   ENA
sp oracle_vol_snp SNAP-oracle_vol SNAP-oracle_vol_dco

v  oracle_vol   -            ENABLED  ACTIVE   83886080 SELECT    -        fsgen
pl oracle_vol-01 oracle_vol  ENABLED  ACTIVE   83886080 CONCAT    -        RW
sd dg101-03     oracle_vol-01 dg101   41943040 83886080 0         c1t2d0   ENA
dc oracle_vol_dco oracle_vol oracle_vol_dcl
v  oracle_vol_dcl -          ENABLED  ACTIVE   6304     SELECT    -        gen
pl oracle_vol_dcl-01 oracle_vol_dcl ENABLED ACTIVE 6304 CONCAT    -        RW
sd dg101-01     oracle_vol_dcl-01 dg101 125829120 6304  0         c1t2d0   ENA
sp SNAP-oracle_vol_snp oracle_vol oracle_vol_dco

3. check snapshot status
# vxsnap -g dg1 -xv list

NAME          DG         OBJTYPE SNAPTYPE PARENT     PARENTDG   SNAPDATE         CHANGED_DATA SYNCED_DATA
oracle_vol    dg1        vol     -        -          -          - -              - -          40G (100%)
SNAP-oracle_vol dg1      vol     fullinst oracle_vol dg1        2011/07/31 02:57 64K (0.0%)   40G (100%)

4. split dg
# vxdg split dg1 dg2 SNAP-oracle_vol

# vxprint -th

dg dg1          default      default  27000    1253797071.15.t2000
dm dg101        c1t2d0s2     auto     65536    143283520 -

v  oracle_vol   -            ENABLED  ACTIVE   83886080 SELECT    -        fsgen
pl oracle_vol-01 oracle_vol  ENABLED  ACTIVE   83886080 CONCAT    -        RW
sd dg101-03     oracle_vol-01 dg101   41943040 83886080 0         c1t2d0   ENA
dc oracle_vol_dco oracle_vol oracle_vol_dcl
v  oracle_vol_dcl -          ENABLED  ACTIVE   6304     SELECT    -        gen
pl oracle_vol_dcl-01 oracle_vol_dcl ENABLED ACTIVE 6304 CONCAT    -        RW
sd dg101-01     oracle_vol_dcl-01 dg101 125829120 6304  0         c1t2d0   ENA
sp SNAP-oracle_vol_snp oracle_vol oracle_vol_dco

dg dg2          default      default  7000     1312053225.56.t2000
dm dg103        c1t3d0s2     auto     65536    143283520 -

v  SNAP-oracle_vol -         ENABLED  ACTIVE   83886080 ROUND     -        fsgen
pl oracle_vol-02 SNAP-oracle_vol ENABLED ACTIVE 83886080 CONCAT   -        RW
sd dg103-01     oracle_vol-02 dg103   0        83886080 0         c1t3d0   ENA
dc SNAP-oracle_vol_dco SNAP-oracle_vol SNAP-oracle_vol_dcl
v  SNAP-oracle_vol_dcl -     ENABLED  ACTIVE   6304     SELECT    -        gen
pl SNAP-oracle_vol_dcl-01 SNAP-oracle_vol_dcl ENABLED ACTIVE 6304 CONCAT - RW
sd dg103-02     SNAP-oracle_vol_dcl-01 dg103 83886080 6304 0      c1t3d0   ENA
sp oracle_vol_snp SNAP-oracle_vol SNAP-oracle_vol_dco

5. join dg (snap vol refresh reattach must in the same dg)
# vxdg join dg2 dg1

6. Refresh snapshot (source vol, snapshit vol must in the same dg)
# vxsnap -g dg1 refresh SNAP-oracle_vol

7. Reattach, (source vol, snapshit vol must in the same dg)
# vxsnap -b -g dg1 reattach SNAP-oracle_vol source=oracle_vol

.