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.
Description of problem:
Many quota related xfstests fail when test with v4 xfs. And they all fail in a similar way. e.g.
*** xfs_repair -n output ***
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 3
- agno = 1
- agno = 2
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
- traversing filesystem ...
- traversal finished ...
- moving disconnected inodes to lost+found ...
disconnected inode 131, would move to lost+found
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.
*** end xfs_repair output
These tests are xfs/050 xfs/108 xfs/133 xfs/134 xfs/196 xfs/244 xfs/261 xfs/262 xfs/287
Version-Release number of selected component (if applicable):
xfsprogs-4.5.0-2.el7
kernel-3.10.0-439.el7
How reproducible:
always
Steps to Reproduce:
1. MKFS_OPTIONS="-m crc=0" ./check <tests listed above>
2.
3.
Actual results:
Expected results:
Additional info:
Not sure if it's an xfsprogs bug or a kernel bug, but if I downgrade xfsprogs to 3.2.2-2.el7 version, all test pass (kernel unchanged). So filing a bug against xfsprogs.
Upstream kernel and xfsprogs have the same issue, I reported this issue (along with other issues) to xfs list back in March, no response yet.
http://oss.sgi.com/archives/xfs/2016-03/msg00063.html
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, 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://rhn.redhat.com/errata/RHBA-2016-2431.html
Description of problem: Many quota related xfstests fail when test with v4 xfs. And they all fail in a similar way. e.g. *** xfs_repair -n output *** Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 1 - agno = 2 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 131, would move to lost+found Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. *** end xfs_repair output These tests are xfs/050 xfs/108 xfs/133 xfs/134 xfs/196 xfs/244 xfs/261 xfs/262 xfs/287 Version-Release number of selected component (if applicable): xfsprogs-4.5.0-2.el7 kernel-3.10.0-439.el7 How reproducible: always Steps to Reproduce: 1. MKFS_OPTIONS="-m crc=0" ./check <tests listed above> 2. 3. Actual results: Expected results: Additional info: Not sure if it's an xfsprogs bug or a kernel bug, but if I downgrade xfsprogs to 3.2.2-2.el7 version, all test pass (kernel unchanged). So filing a bug against xfsprogs. Upstream kernel and xfsprogs have the same issue, I reported this issue (along with other issues) to xfs list back in March, no response yet. http://oss.sgi.com/archives/xfs/2016-03/msg00063.html