Hide Forgot
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:
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.
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.
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.