显示标签为“VCS/VVR”的博文。显示所有博文
显示标签为“VCS/VVR”的博文。显示所有博文

2010年4月16日

ERROR: V-3-21268: /dev/vx/dsk/dgD280silo1/orgvol is corrupted. needs checking

 

Sometime when you migrate from primary to secondary, the volume might be corrupted, just use fsck to fix it:

 

fsck -F vxfs /dev/vx/rdsk/dgD280silo1/orgvol
log replay in progress
replay complete - marking super-block as CLEAN
# mount -F vxfs /dev/vx/dsk/dgD280silo1/orgvol /orgvol


Full Text

2010年3月15日

recovery from RVG is disabled

    sometims your RVG cannot be started anyway, and the “vxprint –Vl” shows something like

    “kernel=DISABLED”

    In my case, the srl volume status is NEEDSYNC, that makes the RVG cannot be started, so repair the srl volume with following instructions:

1.  Dissociate SRL:

# vxvol -g vrdg -f dis vvrsrl

vxvm:vxvol: WARNING: Rvg rvg1 needs recovery. Volume being dissociated may not be up-to-date

2.  Stop the SRL:

# vxvol -g vrdg stop vvrsrl

3.  Start the SRL. It will take some time for the SRL to resynchronize.  You can run vxtask list from another window to monitor progress.

# vxvol start vvrsrl

4.  Re-associate the SRL:

# vxvol -g vrdg aslog rvg1 vvrsrl

5.  Recover the RVG:

# vxrecover -g vrdg -s

6.  Start the RVG:

# vxrvg start rvg1

Reference from symantec:

http://seer.entsupport.symantec.com/docs/268215.htm


Full Text

2010年3月8日

转-恢复unstartable的卷

root@com00biiacc002:~ #> vxprint -g COM2_DATA_DG -hvt
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  COM_DATA_2   -            ENABLED  ACTIVE   312475648 SELECT   -        fsgen
pl COM_DATA_2-01 COM_DATA_2  ENABLED  STALE    312475648 CONCAT   -        WO
sd COM2_DATA_DG02-01 COM_DATA_2-01 COM2_DATA_DG02 0 312475648 0   AMS_WMS1_6 RLOC
pl COM_DATA_2-02 COM_DATA_2  ENABLED  ACTIVE   312475648 CONCAT   -        RW
sd COM2_DATA_DG01-01 COM_DATA_2-02 COM2_DATA_DG01 0 312475648 0   AMS_WMS0_6 ENA
dc COM_DATA_2_dco COM_DATA_2 COM_DATA_2_dcl
v  COM_DATA_2_dcl -          DETACHED DETACH   21888    SELECT    -        gen
pl COM_DATA_2_dcl-01 COM_DATA_2_dcl DISABLED RECOVER 21888 CONCAT -        RW
sd COM2_DATA_DG02-02 COM_DATA_2_dcl-01 COM2_DATA_DG02 312475648 21888 0 AMS_WMS1_6 ENA

发现卷的状态变成detached,尝试start volumn

root@com00biiacc002:~ #> vxvol -g COM2_DATA_DG start COM_DATA_2_dcl
VxVM vxvol ERROR V-5-1-1198 Volume COM_DATA_2_dcl has no CLEAN or non-volatile ACTIVE plexes

start volumn不成功,因为不是clean或active的plex. 下面查看一下dg状态信息

root@com00biiacc002:~ #> vxinfo -g COM2_DATA_DG
COM_DATA_2     fsgen    Started
COM_DATA_2_dcl gen      Unstartable

发现COM_DATA_2_dcl 是unstartable的卷。尝试将COM_DATA_2_dcl的plex设置为clean状态。

root@com00biiacc002:~ #> vxmend -g COM2_DATA_DG fix clean COM_DATA_2_dcl-01
VxVM vxmend ERROR V-5-1-854 Plex COM_DATA_2_dcl-01 not in STALE state

根据提示将plex设置为stale状态。
root@com00biiacc002:~ #> vxmend -g COM2_DATA_DG fix stale COM_DATA_2_dcl-01
root@com00biiacc002:~ #> vxprint -g COM2_DATA_DG -hvt COM_DATA_2_dcl
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  COM_DATA_2_dcl -          DETACHED DETACH   21888    SELECT    -        gen
pl COM_DATA_2_dcl-01 COM_DATA_2_dcl DISABLED STALE 21888 CONCAT   -        RW
sd COM2_DATA_DG02-02 COM_DATA_2_dcl-01 COM2_DATA_DG02 312475648 21888 0 AMS_WMS1_6 ENA
root@com00biiacc002:~ #>

再次尝试start volumn.
root@com00biiacc002:~ #> vxvol -g COM2_DATA_DG start COM_DATA_2_dcl
VxVM vxvol ERROR V-5-1-1198 Volume COM_DATA_2_dcl has no CLEAN or non-volatile ACTIVE plexes

由于plex不是clean或active状态而无法start volumn. 将plex设置为clean状态。
root@com00biiacc002:~ #>
root@com00biiacc002:~ #> vxmend -g COM2_DATA_DG fix clean COM_DATA_2_dcl-01

start volumn.
root@com00biiacc002:~ #> vxvol -g COM2_DATA_DG start COM_DATA_2_dcl
root@com00biiacc002:~ #> vxprint -g COM2_DATA_DG -hvt COM_DATA_2_dcl
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  COM_DATA_2_dcl -          ENABLED  ACTIVE   21888    SELECT    -        gen
pl COM_DATA_2_dcl-01 COM_DATA_2_dcl ENABLED ACTIVE 21888 CONCAT   -        RW
sd COM2_DATA_DG02-02 COM_DATA_2_dcl-01 COM2_DATA_DG02 312475648 21888 0 AMS_WMS1_6 ENA

volumn及plex恢复正常。


Full Text

2010年2月25日

secondary rlink状态为need_recover的解决

    当secondary机器由于某种原因磁盘出错,dg被deport掉,会导致VVR配置出错,这种情况下,需要做下列操作(不一定都必须,但是都要检查)

1. import dg:

vxdg import datadg

2. start all replicated volume:

vxvol start <vol_name>

这样你在secondary机器上用vxprint检查,所有的rvg、rlink、volume都应该为ENABLED、ACTIVE状态,如果有DISABLE类似状态,请再检查并修复。

[root@secondary datadg]# vxprint
Disk group: datadg

TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
dg datadg       datadg       -        -        -        -        -       -

dm datadg01     sdb          -        4094608  -        -        -       -
dm datadg02     sdc          -        4094608  -        -        -       -

rv primary_secondary_rvg -   ENABLED  -        -        ACTIVE   -       -
rl rlk_primary_primary_secondary_ primary_secondary_rvg CONNECT - - ACTIVE - -
v  vol1lv       primary_secondary_rvg ENABLED 1048576 - ACTIVE   -       -
pl vol1lv-01    vol1lv       ENABLED  1048576  -        ACTIVE   -       -
sd datadg01-01  vol1lv-01    ENABLED  1048576  0        -        -       -
pl vol1lv-02    vol1lv       ENABLED  1048576  -        ACTIVE   -       -
sd datadg02-01  vol1lv-02    ENABLED  1048576  0        -        -       -
pl vol1lv-03    vol1lv       ENABLED  LOGONLY  -        ACTIVE   -       -
sd datadg01-05  vol1lv-03    ENABLED  32       LOG      -        -       -
pl vol1lv-04    vol1lv       ENABLED  LOGONLY  -        ACTIVE   -       -
sd datadg02-05  vol1lv-04    ENABLED  32       LOG      -        -       -
v  vol2lv       primary_secondary_rvg ENABLED 1048576 - ACTIVE   -       -
pl vol2lv-01    vol2lv       ENABLED  1048576  -        ACTIVE   -       -
sd datadg01-02  vol2lv-01    ENABLED  1048576  0        -        -       -
pl vol2lv-02    vol2lv       ENABLED  1048576  -        ACTIVE   -       -
sd datadg02-02  vol2lv-02    ENABLED  1048576  0        -        -       -
pl vol2lv-03    vol2lv       ENABLED  LOGONLY  -        ACTIVE   -       -
sd datadg01-04  vol2lv-03    ENABLED  32       LOG      -        -       -
pl vol2lv-04    vol2lv       ENABLED  LOGONLY  -        ACTIVE   -       -
sd datadg02-04  vol2lv-04    ENABLED  32       LOG      -        -       -
v  srllv        primary_secondary_rvg ENABLED 262144 SRL ACTIVE  -       -
pl srllv-01     srllv        ENABLED  262144   -        ACTIVE   -       -
sd datadg01-03  srllv-01     ENABLED  262144   0        -        -       -
pl srllv-02     srllv        ENABLED  262144   -        ACTIVE   -       -
sd datadg02-03  srllv-02     ENABLED  262144   0        -        -       -

3. 在需要recover的机器执行recover操作:

root@secondary datadg]# vxrecover –s

这步执行之后应该就ok,可以用下面的命令检查。下面是在执行vxrecover之前和之后的vxprint结果显示比较:

[root@secondary datadg]# vxprint -lP
Disk group: datadg

Rlink:    rlk_primary_primary_secondary_
info:     timeout=500 packet_size=8400 rid=0.1100
          latency_high_mark=10000 latency_low_mark=9950
          bandwidth_limit=none
state:    state=ACTIVE
          synchronous=off latencyprot=off srlprot=autodcm
assoc:    rvg=primary_secondary_rvg
          remote_host=172.111.100.10 IP_addr=172.111.100.10 port=4145
          remote_dg=datadg
          remote_dg_dgid=1265752821.7.localhost.localdomain
          remote_rvg_version=unknown
          remote_rlink=rlk_secondary_primary_secondar
          remote_rlink_rid=0.1106
          local_host=172.111.100.20 IP_addr=172.111.100.20 port=4145
protocol: UDP/IP
flags:    write disabled attached consistent disconnected needs_recovery

[root@secondary datadg]# vxrecover -s
[root@secondary datadg]# vxprint -lP
Disk group: datadg

Rlink:    rlk_primary_primary_secondary_
info:     timeout=500 packet_size=8400 rid=0.1100
          latency_high_mark=10000 latency_low_mark=9950
          bandwidth_limit=none
state:    state=ACTIVE
          synchronous=off latencyprot=off srlprot=autodcm
assoc:    rvg=primary_secondary_rvg
          remote_host=172.111.100.10 IP_addr=172.111.100.10 port=4145
          remote_dg=datadg
          remote_dg_dgid=1265752821.7.localhost.localdomain
          remote_rvg_version=21
          remote_rlink=rlk_secondary_primary_secondar
          remote_rlink_rid=0.1106
          local_host=172.111.100.20 IP_addr=172.111.100.20 port=4145
protocol: UDP/IP
flags:    write enabled attached consistent connected

 

[root@secondary datadg]# vxrlink -g datadg verify rlk_primary_primary_secondary_
RLINK                REMOTE HOST          LOCAL HOST           STATUS     STATE
rlk_primary_primary_secondary_ 172.111.100.10       172.111.100.20       OK         ACTIVE


Full Text