Sponsored Content
Full Discussion: syncvg
Operating Systems AIX syncvg Post 302213210 by shockneck on Wednesday 9th of July 2008 12:53:07 PM
Old 07-09-2008
The easiest way for syncing a stale AIX LVM mirror is
Code:
# varyonvg <stalevg>

You could consider the varyonvg command as a very basic repairvg. Varyonvg will call syncvg among other things. This will run in the background so you might see a lresynclv process in the processlist. If the lv stays stale after this finished pls post the output of
Code:
# lsvg <stalevg>
# lslv <stalelv>
# lslv -l <stalelv>

(The drawback of varyonvg might be that it syncs one PP per time. Using syncvg makes sense when syncing large mirrors as you can tell it (-P) to sync more PPs per time hence being faster. When it comes to Terrabytes this does make a difference.)
 

We Also Found This Discussion For You

1. AIX

Syncvg

Hello, I currently migrate a VG from one storage to another one with mirrorvg. Does anyone know, if a syncvg copy the whole stale pps, regardless if the overlying fs is nearly empty? Or will only the used space copied? Regards (2 Replies)
Discussion started by: -=XrAy=-
2 Replies
LVMETAD(8)						      System Manager's Manual							LVMETAD(8)

NAME
lvmetad - LVM metadata cache daemon SYNOPSIS
lvmetad [-l {all|wire|debug}] [-p pidfile_path] [-s socket_path] [-f] [-h] [-V] [-?] DESCRIPTION
lvmetad is a metadata caching daemon for LVM. The daemon receives notifications from udev rules (which must be installed for LVM to work correctly when lvmetad is in use). Through these notifications, lvmetad has an up-to-date and consistent image of the volume groups avail- able in the system. By default, lvmetad, even if running, is not used by LVM. See lvm.conf(5). OPTIONS
To run the daemon in a test environment both the pidfile_path and the socket_path should be changed from the defaults. -f Don't fork, but run in the foreground. -h, -? Show help information. -l {all|wire|debug} Select the type of log messages to generate. Messages are logged by syslog. Additionally, when -f is given they are also sent to standard error. Since release 2.02.98, there are two classes of messages: wire and debug. Selecting 'all' supplies both and is equivalent to a comma-separated list -l wire,debug. Prior to release 2.02.98, repeating -d from 1 to 3 times, viz. -d, -dd, -ddd, increased the detail of messages. -p pidfile_path Path to the pidfile. This overrides both the built-in default (#DEFAULT_PID_DIR#/lvmetad.pid) and the environment variable LVM_LVMETAD_PIDFILE. This file is used to prevent more than one instance of the daemon running simultaneously. -s socket_path Path to the socket file. This overrides both the built-in default (/run/lvm/lvmetad.socket) and the environment variable LVM_LVMETAD_SOCKET. To communicate successfully with lvmetad, all LVM2 processes should use the same socket path. -V Display the version of lvmetad daemon. ENVIRONMENT VARIABLES
LVM_LVMETAD_PIDFILE Path for the pid file. LVM_LVMETAD_SOCKET Path for the socket file. SEE ALSO
lvm(8), lvm.conf(5) Red Hat Inc LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26) LVMETAD(8)
All times are GMT -4. The time now is 07:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy