Sponsored Content
Full Discussion: Syncvg
Operating Systems AIX Syncvg Post 302878500 by rbatte1 on Friday 6th of December 2013 11:11:51 AM
Old 12-06-2013
When you add the LV copy and synchronise them, the image of the PP is copied irrespective of what it contains or doesn't. I'm afraid you will just have to wait.
It doesn't matter if you use mirrorvg or mklvcopy. It has to copy everything. Use:-
Code:
lsvg yourvg | grep STALE

... to see how you are getting on. This may get locked out if you are running mirrorvg in the default auto-sync mode. You can ease this by running mirrorvg with the -s (lower case S) flag. This will create the LV copies and then you can synchronise them with syncvg -v yourvg

Make sure when you remove the LV copy, that you specify the hdisk to remove the copy from, else it may well just pick the newly created one.


Caution

Do not interrupt these processes else the ODM and the VG disk information may get out of step leaving you unable to complete the sync. There is a way out, but it's a bit messy.




I hope that this helps,
Robin
Liverpool/Blackburn
UK
This User Gave Thanks to rbatte1 For This Post:
 

We Also Found This Discussion For You

1. AIX

syncvg

Hello I have a box with aix 5.3 if I type lsvg -l rootvg all my filesystems are sync except one rootvg: LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT hd5 boot 1 2 2 closed/syncd N/A hd6 paging 32 64 ... (16 Replies)
Discussion started by: lo-lp-kl
16 Replies
lgrp_cookie_stale(3LGRP)				 Locality Group Library Functions				  lgrp_cookie_stale(3LGRP)

NAME
lgrp_cookie_stale - determine whether snapshot of lgroup hierarchy is stale SYNOPSIS
cc [ flag ... ] file... -llgrp [ library ... ] #include <sys/lgrp_user.h> int lgrp_cookie_stale(lgrp_cookie_t cookie); DESCRIPTION
The lgrp_cookie_stale() function takes a cookie representing the snapshot of the lgroup hierarchy obtained from lgrp_init(3LGRP) and returns whether it is stale. The snapshot can become out-of-date for a number of reasons depending on its view. If the snapshot was taken with LGRP_VIEW_OS, changes in the lgroup hierarchy from dynamic reconfiguration, CPU on/offline, or other conditions can cause the snapshot to become out-of-date. A snapshot taken with LGRP_VIEW_CALLER can be affected by the caller's processor set binding and changes in its processor set itself, as well as changes in the lgroup hierarchy. If the snapshot needs to be updated, lgrp_fini(3LGRP) should be called with the old cookie and lgrp_init() should be called to obtain a new snapshot. RETURN VALUES
Upon successful completion, lgrp_cookie_stale() returns whether the cookie is stale. Otherwise, it returns -1 and sets errno to indicate the error. ERRORS
The lgrp_cookie_stale() function will fail if: EINVAL The cookie is not valid. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ SEE ALSO
lgrp_init(3LGRP), lgrp_fini(3LGRP), lgrp_view(3LGRP), liblgrp(3LIB), attributes(5) SunOS 5.10 16 Apr 2003 lgrp_cookie_stale(3LGRP)
All times are GMT -4. The time now is 09:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy