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.
Bug 2079923 - Documentation for --devices purpose is unclear
Summary: Documentation for --devices purpose is unclear
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: lvm2
Version: 8.5
Hardware: Unspecified
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: David Teigland
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-28 14:11 UTC by Rick Greene
Modified: 2022-11-08 12:52 UTC (History)
10 users (show)

Fixed In Version: lvm2-2.03.14-4.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-08 10:55:24 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLUSTERQE-5781 0 None None None 2022-07-27 19:01:40 UTC
Red Hat Issue Tracker RHELPLAN-120419 0 None None None 2022-04-28 17:51:54 UTC
Red Hat Product Errata RHBA-2022:7792 0 None None None 2022-11-08 10:55:52 UTC

Description Rick Greene 2022-04-28 14:11:30 UTC 
Description of problem: Appears there has been a --devices option added to lvcreate that is supposed to specify the devices to use within the command.

I believe this is not clear enough because it may confuse people into thinking that this is how you specify the PV to use to write the actual extents, which is not the intent of --devices


Version-Release number of selected component (if applicable):
lvm2-2.03.12-11.el8_5.x86_64

How reproducible: Can be reproduced every time

Steps to Reproduce:
1. Create a volume group with at least 2 devices:
vgcreate vgtest /dev/sdb1 /dev/sdc1
2. Attempt to create a logical volume on just one of the devices:
lvcreate -n testlv -L 1G --devices /dev/sdc1 vgtest

Actual results:
  WARNING: Couldn't find device with uuid 1sjcQH-O6XD-2IZR-vEkA-1Dl5-x7ba-PS5Cdb.
  WARNING: VG vgtest is missing PV 1sjcQH-O6XD-2IZR-vEkA-1Dl5-x7ba-PS5Cdb (last written to /dev/sdb1).
  Cannot change VG vgtest while PVs are missing.
  See vgreduce --removemissing and vgextend --restoremissing.
  Cannot process volume group vgtest

Expected results:
logical volume would be created with extents only on /dev/sdc1 with no error

Additional info:
The proper way to do the lvcreate for the desired effect would be this:
lvcreate -n testlv -L 1G vgtest /dev/sdc1
Comment 1 Corey Marthaler 2022-04-28 15:54:41 UTC 
This issue makes a good point. Without much knowledge of the new devicesfile feature, the man page does seem to imply exactly what is attempted in comment #0. The man page should probably make a point to say that --devices overrides the existing devicesfile and if used, ONLY devices provided using --devices will be visible to lvm, and do not necessarily give lvm preference for logical volume allocation.  


       --devices PV
              Devices that the command can use. This option can be repeated or accepts a comma separated list of devices. This overrides the devices file.
Comment 2 David Teigland 2022-04-28 17:00:36 UTC 
How does this alternative description look:

Restricts the devices that are visible and accessible to the command.
Devices not listed will appear to be missing.  This option can be
repeated, or accepts a comma separated list of devices.  This overrides
the devices file.
Comment 3 Corey Marthaler 2022-04-28 17:45:11 UTC 
I like it.
Comment 4 David Teigland 2022-05-02 14:49:07 UTC 
fix https://sourceware.org/git/?p=lvm2.git;a=commit;h=dd28460017356d9a1a30a787b5572e9bcbf1c4a4
Comment 18 errata-xmlrpc 2022-11-08 10:55:24 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (lvm2 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:7792
Note You need to log in before you can comment on or make changes to this bug.