Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
- pv size (LUN) = 10G
- create vg from that pv = 10G
- extend LUN size on storage side with additional 10G (LUN size is now 20G)
- using pvresize, resize pv to 40G, I get: WARNING: /dev/mapper/1stam-31315129: Overriding real size. You could lose data.
Physical volume "/dev/mapper/1stam-31315129" changed 1 physical volume(s) resized / 0 physical volume(s) not resized
[root@nott-vds5 ~]# echo $?
0
[root@nott-vds5 ~]# pvs
PV VG Fmt Attr PSize PFree
/dev/mapper/1stam-31315129 cf0614ae-9859-492e-b425-2c9bc7f04fc8 lvm2 a- 39.75g 35.88g
this command should be blocked. also, in case one wants to build some logic around such case, and allow LUN extend, how can he know the real size of the LUN and if it was resized ? anyhow, I would have expect error message on such scenario.
(In reply to comment #0)
> Description of problem:
>
> - pv size (LUN) = 10G
> - create vg from that pv = 10G
> - extend LUN size on storage side with additional 10G (LUN size is now 20G)
> - using pvresize, resize pv to 40G, I get: WARNING: /dev/mapper/1stam-31315129:
> Overriding real size. You could lose data.
> Physical volume "/dev/mapper/1stam-31315129" changed
>
> 1 physical volume(s) resized
> / 0 physical volume(s) not resized
>
> [root@nott-vds5 ~]# echo $?
> 0
>
> [root@nott-vds5 ~]# pvs
> PV VG Fmt Attr
> PSize PFree
> /dev/mapper/1stam-31315129 cf0614ae-9859-492e-b425-2c9bc7f04fc8 lvm2 a-
> 39.75g 35.88g
>
> this command should be blocked. also, in case one wants to build some logic
> around such case, and allow LUN extend, how can he know the real size of the
> LUN and if it was resized ? anyhow, I would have expect error message on such
> scenario.
It sounds like you're using --setphysicalvolumesize which "Overrides the automatically-detected size of the PV. Use with care, or prior to reducing the physical size of the device."
If this is indeed what you're doing then this is not a bug, but the intended behaviour. You should be running pvresize without the size parameter and let it autodetect the new size.