From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx1.redhat.com (ext-mx13.extmail.prod.ext.phx2.redhat.com [10.5.110.18]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s79Gv8pJ017253 for ; Sat, 9 Aug 2014 12:57:08 -0400 Received: from Ishtar.hs.tlinx.org (ishtar.tlinx.org [173.164.175.65]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s79Gv5Lq010098 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 9 Aug 2014 12:57:07 -0400 Received: from [192.168.4.12] (athenae [192.168.4.12]) by Ishtar.hs.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id s79GuxTJ020019 for ; Sat, 9 Aug 2014 09:57:03 -0700 Message-ID: <53E652DB.9080201@tlinx.org> Date: Sat, 09 Aug 2014 09:56:59 -0700 From: "Linda A. Walsh" MIME-Version: 1.0 References: <53E3CE1C.4050506@tlinx.org> <53E50FB7.6020604@tlinx.org> In-Reply-To: Content-Transfer-Encoding: 7bit Subject: Re: [linux-lvm] vgmerge & move... done, not bad 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"; format="flowed" To: LVM general discussion and development emmanuel segura wrote: > vgchange -an HnS > When it is usable, it's pretty darn fast... average between 400-500MB/s -- will have to setup a test case to see how fast 'dd' would be. For comparison using xfsdump/restore on a 7T partition averaged 216MB/s (Note, using binary prefixes w/binary units (B=2^3), no misleading confusion of decimal prefixes on binary units as comes of 'dd' in this case) Would be "nicer" if I didn't have to do the vgmerge first and could do a direct move from oldVG/oldLV => newVG/newLV (Maintaining assumptions of same-sized allocation units). Is that planned or is there some technical reason why that wouldn't be desirable? Thanks for assist and someone clarifying that "active" might be better viewed as "available". Linda