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 2165771 - lvresize appears to determine that a LUKS stack is a "File system found" even though later "No file system found on"
Summary: lvresize appears to determine that a LUKS stack is a "File system found" even...
Keywords:
Status: CLOSED DUPLICATE of bug 2165691
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: lvm2
Version: 9.2
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: LVM and device-mapper development team
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-31 00:26 UTC by Corey Marthaler
Modified: 2023-01-31 21:34 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-31 21:33:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-146978 0 None None None 2023-01-31 00:26:55 UTC

Description Corey Marthaler 2023-01-31 00:26:16 UTC 
Description of problem:
This LV does *not* have a filesystem on it, however it does have a LUKS volume, which I believe triggers the "File system found on crypt device" message. It then checks that LUKS volume and determines that "No file system found". Maybe those messages can be less confusing for the user by stating "Luks (or something generic like 'stacked') device found on ..." and then "No file system found on" versus the contradicting messages currently.


lvcreate --yes --type linear -n resize_lv  -L 30G resize_matrix  
Logical volume "resize_lv" created.

activating LV resize_lv -ay on virt-557.cluster-qe.lab.eng.brq.redhat.com
lvchange --yes -ay  resize_matrix/resize_lv

'echo "Str0ngP455w0rd###" | cryptsetup luksFormat /dev/resize_matrix/resize_lv'
'echo "Str0ngP455w0rd###" | cryptsetup luksOpen /dev/resize_matrix/resize_lv resize_luks'

Adding additional space to resize_matrix/resize_lv on virt-557.cluster-qe.lab.eng.brq.redhat.com
lvextend --yes --fs resize -L +364M resize_matrix/resize_lv 
  Size of logical volume resize_matrix/resize_lv changed from 30.00 GiB (7680 extents) to <30.36 GiB (7771 extents).
  File system found on crypt device /dev/dm-3 on LV resize_matrix/resize_lv.
  No file system found on /dev/dm-3.
  Logical volume resize_matrix/resize_lv successfully resized.


Version-Release number of selected component (if applicable):
kernel-5.14.0-239.el9    BUILT: Thu Jan 19 04:29:56 PM CET 2023
lvm2-2.03.17-4.el9    BUILT: Tue Jan 10 06:40:12 PM CET 2023
lvm2-libs-2.03.17-4.el9    BUILT: Tue Jan 10 06:40:12 PM CET 2023
Comment 1 David Teigland 2023-01-31 17:18:26 UTC 
I noticed the same and fixed that message in the patch for bug 2165691.
Comment 2 David Teigland 2023-01-31 21:33:54 UTC 
included in the patch for bug 2165691 since it was related

*** This bug has been marked as a duplicate of bug 2165691 ***
Note You need to log in before you can comment on or make changes to this bug.