Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

one failing disk from vxprint, but I can run prtvtoc against this disk

Created: 07 Feb 2013 • Updated: 07 Mar 2013 | 3 comments
This issue has been solved. See solution.

bash-2.03# prtvtoc /dev/rdsk/c4t0d58s2
* /dev/rdsk/c4t0d58s2 partition map
*
* Dimensions:
*     512 bytes/sector
*      64 sectors/track
*      60 tracks/cylinder
*    3840 sectors/cylinder
*   36828 cylinders
*   36826 accessible cylinders
*
* Flags:
*   1: unmountable
*  10: read-only
*
* Unallocated space:
*       First     Sector    Last
*       Sector     Count    Sector
*           0      3840      3839
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       2      5    01          0 141411840 141411839
       3     15    01       3840      7680     11519
       4     14    01      11520 141400320 141411839
bash-2.03#

bash-2.03# vxprint -htg ictdg
DG NAME         NCONFIG      NLOG     MINORS   GROUP-ID
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
V  NAME         RVG          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
DC NAME         PARENTVOL    LOGVOL
SP NAME         SNAPVOL      DCO

dg ictdg        default      default  6000     1074301281.1224.svan1008

dm ictdg01      c4t0d47s2    sliced   3583     17670720 -
dm ictdg02      c4t0d25s2    sliced   3583     17670720 -
dm ictdg03      c4t0d48s2    sliced   5503     70698240 -
dm ictdg04      c4t0d49s2    sliced   5503     70698240 -
dm ictdg05      c4t0d50s2    sliced   5503     70698240 -
dm ictdg06      c4t0d51s2    sliced   5503     70698240 -
dm ictdg07      c4t0d52s2    sliced   5503     70698240 -
dm ictdg08      c4t0d53s2    sliced   5503     70698240 -
dm ictdg09      c4t0d54s2    sliced   5503     70698240 -
dm ictdg10      c4t0d55s2    sliced   7423     141400320 -
dm ictdg11      c4t0d56s2    sliced   7423     141400320 -
dm ictdg12      c4t0d57s2    sliced   7423     141400320 -
dm ictdg13      c4t0d58s2    sliced   7423     141400320 FAILING
dm ictdg14      c4t0d59s2    sliced   7423     141400320 -
dm ictdg15      c4t0d60s2    sliced   7423     141400320 -
dm ictdg16      c4t0d61s2    sliced   7423     141400320 -
dm ictdg17      c4t0d62s2    sliced   7423     141400320 -
dm ictdg18      c4t0d63s2    sliced   7423     141400320 -
dm ictdg19      c4t0d64s2    sliced   7423     141400320 -
dm ictdg20      c4t0d65s2    sliced   7423     141400320 -
dm ictdg21      c4t0d66s2    sliced   7423     141400320 -
dm ictdg24      c4t0d69s2    sliced   5503     70698240 -

Comments 3 CommentsJump to latest comment

Marianne's picture

FAILING state is set when I/O errors were detected at some point in time.

If you are sure that the disk is fine, you can remove VxVM Failing state:

vxedit -g <DISK_GROUP NAME> set failing=off <DISK_NAME>

vxedit -g ictdg set failing=off ictdg13

See: http://www.symantec.com/docs/TECH61915

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
TonyGriffiths's picture

Possibly its a transient error that has corrected itself.

It may be worth checking out the device health from a Solaris perspective

Anything in /var/adm/messages or iostate -En ?

cheers

tony

TonyGriffiths's picture

Oops

I meant iostat -En

tony