vgsyncing happend for every time when I activate vg.

[Rajesh SB]

Hi,

In one of disk array, I replaced the bad Hard disk
by following these steps.

" * vgcfgrestore -n vg01 -l
* vgchange -a y vg01
It reported about "could not re-synchronize stale partitions...."
Then I remembered that I had removed the entry of the faulty disk from
/etc/lvmtab.
So, I did a vgscan -a, which created /etc/lvmtab and now both "ioscan -fnC
disk" and
"strings /etc/lvmtab" show the entry of the new disk /dev/dsk/c3t3d0
Now, I did a "vgchange -a n vg01" and "vgchange -a y vg01".

I saw that the mirror disks started sync'ing. It took almost one hour and
the command
finished with "volume group vg01 successfully changed".

Now, the problem is everytime I try to activate the volume group it starts
sync'ing. How could we rectify this problem ?

Thanks in advance.

Rajesh SB

[Michael Tully · Accepted solution]

Hi,

The man page for 'vgchange' even states this:

Quote/
If the -a y or -a e option is executed on a currently active volume group, vgchange attempts to include any physical volumes that were previously listed as missing. This is useful if a physical volume has come back online. However, no automatic synchronization of any mirrored logical volumes is done. If synchronization is required, execute the vgsync command (see vgsync(1M)).
End Quote
At a guess something has obviously gone when the disk was replaced. What I would be tempted to do is to do a 'lvreduce' on each of the logical volumes that are attached on that disk and, remove the disk from the volume group, 'pvcreate -f' the disk 'vgextend' the volume again with this same disk and re-do the mirror.

HTH
Michael

[Michael Tully]

HARHA!!!

ZERO Assignment of points from 33 (now 34 responses)

Can we add this user to the black list please..... (I try not to get narky but fair is fair......)

[Ceesjan van Hattum]

I assume, but am not 100% sure, that the automated syncing which indeed takes a long time, is initiated by /usr/sbin/syncer. It keeps on watching changes in the vg's and decides by itself to start syncing.

To stop this inconvienence, you can stop the syncer-daemon by:
/sbin/init.d/syncer stop
and you can decide yourself wheter or not to set the /etc/rc.config.d/syncer variable SYNCER=0

Regards,
Ceesjan