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.

Bug 1999733

Summary: lvm journal logging should check for invalid options
Product: Red Hat Enterprise Linux 9 Reporter: Corey Marthaler <cmarthal>
Component: lvm2Assignee: David Teigland <teigland>
lvm2 sub component: Displaying and Reporting QA Contact: cluster-qe <cluster-qe>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: low CC: agk, heinzm, jbrassow, mcsontos, msnitzer, prajnoha, teigland, zkabelac
Version: 9.0Keywords: Triaged
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: lvm2-2.03.14-3.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-17 15:56:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Corey Marthaler 2021-08-31 16:39:39 UTC
Description of problem:

[root@hayes-02 ~]# vgs
  VG     #PV #LV #SN Attr   VSize  VFree 
  testVG   3   0   0 wz--n- <5.46t <5.46t
[root@hayes-02 ~]# lvremove --journal foo testVG
[root@hayes-02 ~]# echo $?
0


Version-Release number of selected component (if applicable):
lvm2-2.03.13-1.el9    BUILT: Thu Aug 12 10:44:54 AM CDT 2021
lvm2-libs-2.03.13-1.el9    BUILT: Thu Aug 12 10:44:54 AM CDT 2021

Comment 2 David Teigland 2021-12-02 18:46:06 UTC
added warning
https://sourceware.org/git/?p=lvm2.git;a=commit;h=455c29b10dfd15a9fa2ad72c8f9de77572328d39

# vgs --journal foo
  Ignoring unrecognized journal value.
  Ignoring unrecognized journal value.
  VG #PV #LV #SN Attr   VSize    VFree   
  mm   1   3   0 wz--n- <931.01g <931.00g

The message duplication will be fixed by a later (and much larger) change that's in progress which fixes command setup which processes settings two or more times.

Comment 5 Corey Marthaler 2022-01-07 00:35:28 UTC
Marking Verified:Tested in the latest rpms.

kernel-5.14.0-39.el9    BUILT: Thu Dec 23 10:43:17 PM CST 2021
lvm2-2.03.14-3.el9    BUILT: Tue Jan  4 04:49:45 PM CST 2022
lvm2-libs-2.03.14-3.el9    BUILT: Tue Jan  4 04:49:45 PM CST 2022


[root@hayes-03 ~]# pvcreate --journal foo /dev/sdb1
  Ignoring unrecognized journal value.
  Ignoring unrecognized journal value.
  Physical volume "/dev/sdb1" successfully created.
[root@hayes-03 ~]# vgcreate --journal bar vg /dev/sdb1
  Ignoring unrecognized journal value.
  Ignoring unrecognized journal value.
  Volume group "vg" successfully created

Comment 9 errata-xmlrpc 2022-05-17 15:56:27 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 (new packages: lvm2), 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:3972