From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 5 Mar 2019 11:56:03 -0500 (EST) From: "Stuart D. Gathman" In-Reply-To: <20190305163631.GD1155@redhat.com> Message-ID: References: <11dcbee0-ec65-d5d2-b07c-9937b99cc5b4@linux.ibm.com> <30346b34-c1e1-f7ba-be4e-a37d8ce8cf03@gmail.com> <1576db4f-1d7c-6894-d9b0-69c51852b11c@linux.ibm.com> <325bbb01-1b67-eafb-025e-4bfde1b16b54@gmail.com> <328b148e-61ff-1099-5362-3e799407580c@linux.ibm.com> <80ee50b6-4d44-90d1-b38e-4072ebbc7cbf@izyk.ru> <20190305163631.GD1155@redhat.com> MIME-Version: 1.0 Subject: Re: [linux-lvm] Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size 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" Content-Transfer-Encoding: 7bit To: LVM general discussion and development Cc: Nir Soffer , Ingo Franzki On Tue, 5 Mar 2019, David Teigland wrote: > On Tue, Mar 05, 2019 at 06:29:31PM +0200, Nir Soffer wrote: >> Maybe LVM should let you mix PVs with different logical block size, but it >> should >> require --force. > > LVM needs to fix this, your solution sounds like the right one. Also, since nearly every modern device device has a physical block size of 4k or more, and even when the logical block size is (emulated) 512, performance degradation occurs with smaller filesystem blocks, then the savvy admin should ensure that all filesystem have a min of 4k block size - except in special circustances. -- Stuart D. Gathman "Confutatis maledictis, flamis acribus addictis" - background song for a Microsoft sponsored "Where do you want to go from here?" commercial.