[linux-lvm] Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size

Ilia Zykov mail at service4.ru
Thu Feb 28 10:41:42 UTC 2019

>>  smartctl -i /dev/sdb; blockdev --getbsz --getpbsz /dev/sdb
>> Device Model:     HGST HUS722T2TALA604
>> User Capacity:    2,000,398,934,016 bytes [2.00 TB]
>> Sector Size:      512 bytes logical/physical
>> Rotation Rate:    7200 rpm
>> Form Factor:      3.5 inches
>> 4096
>> 512
>> As you see “–getbsz” forever 4096.
> I also see logical block size to be 4096 for all devices on my system.
>> But I think it must be forever 512.
>> What does it mean?
> I have seen the following description about logical and physical block sizes somewhere in the internet:
> "Logical block sizes are the units used by the 'kernel' for read/write operations.

Kernel can but usually does not want, because reduce performance.

> Physical block sizes are the units which 'disk controllers' use for read/write operations."

Not disk controller on the motherboard, but controller inside disk. We
don't have access to it.

> For the problem mentioned in this thread, the physical block size is what you are looking for.

I think it is BUG in the "blockdev".
My question was:

Can this error(or similar) be related to a problem in pvmove?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3599 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/linux-lvm/attachments/20190228/cb6e721c/attachment.p7s>

More information about the linux-lvm mailing list