From: Gang He <ghe@suse.com> To: David Teigland <teigland@redhat.com> Cc: "linux-lvm@redhat.com" <linux-lvm@redhat.com> Subject: Re: [linux-lvm] About online pvmove/lvresize on shared VG Date: Thu, 9 Jul 2020 08:44:23 +0800 [thread overview] Message-ID: <f699b25f-4962-4b47-b0ab-9ab5c944a032@suse.com> (raw) In-Reply-To: <20200708160519.GA23533@redhat.com> Hi David, Thank for your reply. more questions, On 7/9/2020 12:05 AM, David Teigland wrote: > On Wed, Jul 08, 2020 at 03:55:55AM +0000, Gang He wrote: >> but I cannot do online LV reduce from one node, >> the workaround is to switch VG activation_mode to exclusive, run lvreduce command on the node where VG is activated. >> Does this behaviour is by-design? or a bug? > > It was intentional since shrinking the cluster fs and LV isn't very common > (not supported for gfs2). OK, thank for confirmation. > >> For pvmove command, I cannot do online pvmove from one node, >> The workaround is to switch VG activation_mode to exclusive, run pvmove command on the node where VG is activated. >> Does this behaviour is by-design? do we do some enhancements in the furture? >> or any workaround to run pvmove under shared activation_mode? e.g. --lockopt option can help this situation? > > pvmove is implemented with mirroring, so that mirroring would need to be > replaced with something that works with concurrent access, e.g. cluster md > raid1. I suspect there are better approaches than pvmove to solve the > broader problem. Sorry, I am a little confused. In the future, we can do online pvmove when VG is activated in shared mode? from man page, I feel these limitations are temporary (or Not Yet Complete). By the way, --lockopt option can help this situation? I cannot find the detailed description for this option in manpage. Thanks Gang > > Dave >
next prev parent reply other threads:[~2020-07-09 0:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-08 3:55 Gang He 2020-07-08 16:05 ` David Teigland 2020-07-09 0:44 ` Gang He [this message] 2020-07-09 17:01 ` David Teigland
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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=f699b25f-4962-4b47-b0ab-9ab5c944a032@suse.com \ --to=ghe@suse.com \ --cc=linux-lvm@redhat.com \ --cc=teigland@redhat.com \ --subject='Re: [linux-lvm] About online pvmove/lvresize on shared VG' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * 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).