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.
Both runs did actually output a report:
Name GrpID RgID ObjType RgStart RgSize #Areas ArID ArStart ArSize ProgID
host-092.virt.lab.msp.redhat.com_load 0 0 area 9.00m 977.00k 1 0 9.00m 977.00k dmstats
host-092.virt.lab.msp.redhat.com_load 0 0 group 9.00m 977.00k 1 0 9.00m 977.00k dmstats
Very odd: off the top of my head I'm not sure what's happening here but there are a bunch of <backtrace> in the output that need tracking down.
What's also odd is that "Command failed." appears before the successful -vvv output.
Any idea on a reproducer? Is there anything odd or unusual about the files?
It'd help to know the file system they are on, although it shouldn't make a difference as it obviously supports the FIEMAP ioctl. Also if you could post the "filefrag -v" it might give some extra hints.