On Wed, Sep 30, 2020 at 06:08:53PM +0800, Gang He wrote: > Hi David, > > Thank for your helps. > > On 9/29/2020 10:02 PM, David Teigland wrote: > > On Tue, Sep 29, 2020 at 08:46:25AM +0000, Gang He wrote: > > > ghe-tw-nd1# lvresize -L+1024M vg1/lv1 > > > WARNING: extending LV with a shared lock, other hosts may require LV refresh. > > > Size of logical volume vg1/lv1 changed from 13.00 GiB (3328 extents) to 14.00 GiB (3584 extents). > > > Logical volume vg1/lv1 successfully resized. > > > Refreshing LV /dev//vg1/lv1 on other hosts... > > > > Triggering remote lvchange refresh for lvresize has been implemented using > > dlm_controld. See configure --enable-lvmlockd-dlmcontrol which enables > > lvmlockd to use the libdlmcontrol api dlmc_run_start/dlm_run_check. > > Dave > That means LV size will be refreshed automatically if this configure option > is enabled, right? right > If we do not enable this configure option, we can use "lvchange --refresh > vg/lv" on the other nodes to synchronize LV size, right? right > This command will affect the upper cluster file system if it is running? I'm not sure I underststand, but extending the lv shouldn't effect the fs. Extending the fs (e.g. gfs2_grow) will make the fs use the new space. Dave _______________________________________________ linux-lvm mailing list linux-lvm@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
