From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 9 Jul 2020 12:01:28 -0500 From: David Teigland Message-ID: <20200709170128.GB9029@redhat.com> References: <20200708160519.GA23533@redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Subject: Re: [linux-lvm] About online pvmove/lvresize on shared VG Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Gang He Cc: "linux-lvm@redhat.com" On Thu, Jul 09, 2020 at 08:44:23AM +0800, Gang He wrote: > > 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? I think it's unlikely, but possible if someone has interest. I'd first encourage them to think about new ways to solve the problem. > from man page, I feel these limitations are temporary (or Not Yet Complete). wording should probably change > By the way, --lockopt option can help this situation? I cannot find the > detailed description for this option in manpage. No, lockopt is for some one-off special cases where we might need to work around ordinary behaviors (like --nolocking.) There's no workaround to the problem that dm-mirror doesn't work under a shared LV. Dave