Professional Documents
Culture Documents
http://support.veritas.com/docs/239970
Details:
If the plex has been in recover mode for too long and it seems as if a mirror
resynchronization has stalled, it is possible to check if anything is happening on
the plex by running the following command:
Note: <dgname> is the name of the disk group and <plexname> is the name of the
plex being synchronized up to.
Running the following command, for instance, will generate the following output:
The output shows that there are "WRITE" operations going to the plex. This means
that the resynchronization is working. If no "WRITE" operations were shown, it
would have been safe to say that the mirror was not getting resynchronized.
If there is no activity shown on the plex with the above vxstat command, manually
start the resynchronization process by doing the following:
Note: The last vxplex command will run until the volume is completely
synchronized.
If the following error comes up, it just means that the temporary utility fields
that VERITAS Volume Manager uses as a locking mechanism need to be cleared up:
vxvm:vxplex: ERROR: Plex <plexname> in volume <volname> is locked by another
utility.
This error is shown when the original resynchronization process has died suddenly
and these fields did not get cleared up correctly. If they are cleared up, the
vxplex commands will run fine.
From the above output, the "TUTIL0" flag is set for both the volume and the plex
(in this case, vol04 and vol04-02, respectively). This must be cleared up from
both the volume and the plex. The following command will accomplish this task:
For example :
Note: For VxVM setup not using the FMR snapshots, the following vxmend command can
also be used to clear the fields.(FMR snapshot depends on "putil2" field for it's
operations and clearing the field "putil2" can cause undesired result in FMR
operations).
For this example (to clear the flag for both volume and plex), run:
Note: Running the vxprint command again will show that the TUTIL0 states have been
cleared up.
Acknowledgements
Sun Microsystems
Products Applied:
Volume Manager for UNIX/Linux 3.5 (Solaris), 4.0 (Solaris), 4.1 (Solaris)
Subjects:
Volume Manager for UNIX/Linux
Application: Informational
Languages:
English (US)
Operating Systems:
Solaris
2.6, 7.0, 8.0, 9.0
THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS
IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES,
EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE
LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC
SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR
CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.