Friday, June 10, 2005

loss of fiber channel veritas

BTC wrote:
> Hi,
>
> One of my servers briefly lost its fiber channel connection to its 3510
> array (don't ask)!
>
> The connection was restored quickly, but not before vxvm got itself in a
> knot. (See the output of vxdisk and vxprint below).
>
> I'm not sure how to recover from this. I have been through the Veritas
> doco but that doesn't seem to cover a situation like this.
>
> I have seen a few references to using "vxdctl enable", but I am
> concerned that this might make matters worse. Considering I have a few
> terabytes of data on these disks I'm not keen on having to restore from
> tape. So will "vxdctl enable" do anything "bad" like dropping the
> configs for my volumes?
>
> Any assistance would be greatly appreciated.
>
> Cheers,
>
> BTC
>
> # vxdisk list
> DEVICE TYPE DISK GROUP STATUS
> c1t0d0s2 sliced rootdisk rootdg online
> c1t1d0s2 sliced nsr00 nsr online
> c1t2d0s2 sliced rootdg00 rootdg online
> c1t3d0s2 sliced nsr01 nsr online
> c1t4d0s2 sliced datadg00 datadg online
> c1t5d0s2 sliced datadg01 datadg online
> fabric_0 sliced - - online
> fabric_1 sliced - - online
> fabric_2 sliced - - online
> fabric_3 sliced - - online
> fabric_4 sliced - - online
> fabric_5 sliced - - online
> fabric_6 sliced - - online
> fabric_7 sliced - - online
> fabric_8 sliced - - online
> fabric_9 sliced - - online
> fabric_10 sliced - - online
> fabric_11 sliced - - online
> - - datadg02 datadg failed was:fabric_0
> - - datadg03 datadg failed was:fabric_1
> - - datadg04 datadg failed was:fabric_2
> - - datadg05 datadg failed was:fabric_3
> - - datadg06 datadg failed was:fabric_4
> - - datadg07 datadg failed was:fabric_5
> - - datadg08 datadg failed was:fabric_6
> - - datadg09 datadg failed was:fabric_7
> - - datadg10 datadg failed was:fabric_8
> - - datadg11 datadg failed was:fabric_9
> - - datadg12 datadg failed was:fabric_10
> - - datadg13 datadg failed was:fabric_11
>
>
> # vxprint -g datadg
> TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0
> PUTIL0
> dg datadg datadg - - - - -
> -
>
> dm datadg00 c1t4d0s2 - 143328960 - - -
> -
> dm datadg01 c1t5d0s2 - 143328960 - - -
> -
> dm datadg02 - - - - NODEVICE -
> -
> dm datadg03 - - - - NODEVICE -
> -
> dm datadg04 - - - - NODEVICE -
> -
> dm datadg05 - - - - NODEVICE -
> -
> dm datadg06 - - - - NODEVICE -
> -
> dm datadg07 - - - - NODEVICE -
> -
> dm datadg08 - - - - NODEVICE -
> -
> dm datadg09 - - - - NODEVICE -
> -
> dm datadg10 - - - - NODEVICE -
> -
> dm datadg11 - - - - NODEVICE -
> -
> dm datadg12 - - - - NODEVICE -
> -
> dm datadg13 - - - - NODEVICE -
> -
>
> v Admin fsgen DISABLED 37748736 - ACTIVE -
> -
> pl Admin-01 Admin DISABLED 37755520 - NODEVICE -
> -
> sd datadg02-02 Admin-01 DISABLED 37755520 0 NODEVICE -
> -
>
> v CDBurning fsgen ENABLED 142606336 - ACTIVE -
> -
> pl CDBurning-01 CDBurning ENABLED 142606464 - ACTIVE -
> -
> sd datadg00-01 CDBurning-01 ENABLED 142606464 0 - -
> -
>
> v Computing fsgen DISABLED 209715200 - EMPTY -
> -
> pl Computing-01 Computing DISABLED 209715264 - NODEVICE -
> -
> sd datadg01-01 Computing-01 ENABLED 142606464 0 - -
> -
> sd datadg02-07 Computing-01 DISABLED 67108800 142606464 NODEVICE -
> -
>
> v Dump fsgen DISABLED 2097152 - EMPTY -
> -
> pl Dump-01 Dump DISABLED 2116928 - NODEVICE -
> -
> sd datadg02-06 Dump-01 DISABLED 2116928 0 NODEVICE -
> -
>
> v Finance fsgen DISABLED 48234496 - ACTIVE -
> -
> pl Finance-01 Finance DISABLED 48237568 - NODEVICE -
> -
> sd datadg12-01 Finance-01 DISABLED 48237568 0 NODEVICE -
> -

vxdctl enable can be run even if the vxconfigd is running in enabled
mode.
It looks for new devices that are added since vxconfigd was last
started.

You can use /etc/vx/bin/vxreattach -c c?t?d?. If it displays the
diskgroup and disk name you can then use /etc/vx/bin/vxreattach -r
c?t?d?

snip from man vxreattach

/etc/vx/bin/vxreattach -c c1t2d0

If reattachment is possible, vxreattach returns with an exit
status of 0 and displays the disk group name and disk media
name. If reattachment is not possible, vxreattach returns
an exit status of 2 and displays an error.

Attempt to reattach the disk in the foreground and try to
recover stale plexes of any volumes on the disk:

/etc/vx/bin/vxreattach -r c1t2d0

If the reattachment is successful, vxreattach returns an
exit status of 0. Otherwise, if an error occurs, vxreattach
returns a non-zero exit code as defined on vxintro(1M).

HTH
S

0 Comments:

Post a Comment

<< Home