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 1043591

Summary: [xfs/xfstests xfs/295] xfs_logprint: unknown log operation type (494e) on v5 file systems
Product: Red Hat Enterprise Linux 7 Reporter: Boris Ranto <branto>
Component: xfsprogsAssignee: Eric Sandeen <esandeen>
Status: CLOSED CURRENTRELEASE QA Contact: Boris Ranto <branto>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: dchinner
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 10:54:49 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 Boris Ranto 2013-12-16 18:04:12 UTC 
Description of problem:
The test case xfs/295 fails on v5 file systems. The test seems to expose the same issue as was present on v4 file systems a while back.

Version-Release number of selected component (if applicable):
kernel-3.10.0-57.el7.x86_64
xfsprogs-3.2.0-0.3.alpha2.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Run the test case xfs/295 from xfstests on v5 xfs fs (test dev should mkfs'd with -m crc=1)
MKFS_OPTIONS="-m crc=1" ./check xfs/295
2.
3.

Actual results:
xfs_logprint: unknown log operation type (494e)
Bad data in log

Expected results:
The test passes.

Additional info:
Comment 1 Eric Sandeen 2014-02-27 01:21:50 UTC 
We have a resolution for this now, sent upstream:

[PATCH 1/2] xfs_logprint: Don't error out after split items lose context
[PATCH 2/2] xfs_logprint: don't advance op counter in xlog_print_trans_icreate

Neither is unique to CRCs, although CRCs seem to have perturbed the log to expose these bugs.

Requesting blocker because xfs_logprint can be a critical tool for debugging & triage, and without these fixes it may error out early.
Comment 3 Boris Ranto 2014-03-04 10:02:16 UTC 
Verified in xfsprogs-3.2.0-0.8.alpha2.el7, the test case passes.

Reproduced in xfsprogs-3.2.0-0.6.alpha2.el7, xfs_logprint reports unknown log operation.
Comment 4 Ludek Smid 2014-06-13 10:54:49 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.