WARNING: Device /dev/sda3 has size of 936652512 sectors which is smaller than corresponding PV size of 975722511 sectors. Was device resized?

[gixxerdaveneo]

After cloning 500gb disk to a 480GB disk, getting warning device has size x which is smaller. What command should be run to fix?
would running this command fix issue?
pvresize /dev/sda --setphysicalvolumesize 936652512s

vgdisplay
WARNING: Device /dev/sda3 has size of 936652512 sectors which is smaller than corresponding PV size of 975722511 sectors. Was device resized?
WARNING: One or more devices used as PVs in VG pve have changed sizes.
--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 103
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size <465.26 GiB
PE Size 4.00 MiB
Total PE 119106
Alloc PE / Size 115011 / 449.26 GiB
Free PE / Size 4095 / <16.00 GiB
VG UUID 7q3fLJ-zTAT-Dn8K-gX9j-b0n2-dW82-JkXhj2

--- Volume group ---
VG Name ceph-d953afcd-8bd6-4018-8262-b3b409160a28
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 5
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 1
Act PV 1
VG Size <1.82 TiB
PE Size 4.00 MiB
Total PE 476932
Alloc PE / Size 476932 / <1.82 TiB
Free PE / Size 0 / 0
VG UUID qXGjsc-CqNa-9zsT-p1oM-Xt6d-6N5c-mzE5VL

lvdisplay
WARNING: Device /dev/sda3 has size of 936652512 sectors which is smaller than corresponding PV size of 975722511 sectors. Was device resized?
WARNING: One or more devices used as PVs in VG pve have changed sizes.
--- Logical volume ---
LV Name data
VG Name pve
LV UUID hjfC66-77QA-omcB-aWtB-0zT7-f69E-XGIgn1
LV Write Access read/write (activated read only)
LV Creation host, time proxmox, 2020-11-24 12:49:47 -0700
LV Pool metadata data_tmeta
LV Pool data data_tdata
LV Status available
# open 0
LV Size 339.33 GiB
Allocated pool data 0.00%
Allocated metadata 0.50%
Current LE 86869
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:6

--- Logical volume ---
LV Path /dev/pve/swap
LV Name swap
VG Name pve
LV UUID DZbkKq-E4YM-jlJx-CYoe-xetf-XJij-f1YMOS
LV Write Access read/write
LV Creation host, time proxmox, 2020-11-24 12:49:46 -0700
LV Status available
# open 2
LV Size 7.00 GiB
Current LE 1792
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:0

--- Logical volume ---
LV Path /dev/pve/root
LV Name root
VG Name pve
LV UUID 7CuSkG-XHK2-q8f3-lC1a-iw2q-9UR8-RbVISz
LV Write Access read/write
LV Creation host, time proxmox, 2020-11-24 12:49:46 -0700
LV Status available
# open 1
LV Size 96.00 GiB
Current LE 24576
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:1

--- Logical volume ---
LV Path /dev/ceph-d953afcd-8bd6-4018-8262-b3b409160a28/osd-block-bd4facc8-c03e-4594-b058-1ab684ff4643
LV Name osd-block-bd4facc8-c03e-4594-b058-1ab684ff4643
VG Name ceph-d953afcd-8bd6-4018-8262-b3b409160a28
LV UUID zoQemA-mrBy-sWVE-XLUb-n3F8-AszH-ZTpzYg
LV Write Access read/write
LV Creation host, time proxmox-02, 2024-04-11 10:52:23 -0600
LV Status available
# open 24
LV Size <1.82 TiB
Current LE 476932
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:2

root@proxmox-02:~# fdsik -l
-bash: fdsik: command not found
root@proxmox-02:~# fdisk -l
Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: KINGSTON SA400S3
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1CB1A622-B184-400F-9E03-F777BE072978

Device Start End Sectors Size Type
/dev/sda1 34 1966 1933 966.5K BIOS boot
/dev/sda2 1967 1050542 1048576 512M EFI System
/dev/sda3 1050543 937703054 936652512 446.6G Linux LVM


Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WD Green SN350 2TB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/pve-swap: 7 GiB, 7516192768 bytes, 14680064 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/pve-root: 96 GiB, 103079215104 bytes, 201326592 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/ceph--d953afcd--8bd6--4018--8262--b3b409160a28-osd--block--bd4facc8--c03e--4594--b058--1ab684ff4643: 1.82 TiB, 2000397795328 bytes, 3907026944 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/rbd0: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes

 

[bbgeek17]

Hi @gixxerdaveneo. As this is not PVE-specific, there are many discussions about this situation on the net. A quick Google search brings up:
https://forums.centos.org/viewtopic.php?t=76660
https://serverfault.com/questions/912972/sectors-which-is-smaller-than-corresponding-pv-size-error

I'd recommend viewing these and other articles and proceeding very carefully. Making a wrong move can lead to data loss.

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox