archive mirror
 help / color / mirror / Atom feed
From: David Teigland <>
To: Gang He <>
Cc: "" <>
Subject: Re: [linux-lvm] lvresize cannot refresh LV size on on other hosts when extending LV with a shared lock
Date: Wed, 30 Sep 2020 09:15:14 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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?


> If we do not enable this configure option, we can use "lvchange --refresh
> vg/lv" on the other nodes to synchronize LV size, 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.


      reply	other threads:[~2020-09-30 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29  8:46 Gang He
2020-09-29 10:41 ` Zdenek Kabelac
2020-09-29 14:02 ` David Teigland
2020-09-30 10:08   ` Gang He
2020-09-30 14:15     ` David Teigland [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: [linux-lvm] lvresize cannot refresh LV size on on other hosts when extending LV with a shared lock' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).