Red Hat Bugzilla – Bug 1014312
[xfs/xfstests 298] Inline symlink is not removed from inode
Last modified: 2014-06-16 23:16:35 EDT
+++ This bug was initially created as a clone of Bug #1014308 +++
Description of problem:
Copied from the description of the test case:
inline symlinks are removed from the inode when an extended attributes forces it into being remote symlink. Warning: this test will ASSERT on unpatched DEBUG XFS.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run the xfstests test case xfs/298 for xfs fs
2. Check the output
For symlink size 128, the core.nextents is reported to be 1.
The core.nextents is 0.
This seems to have been fixed upstream by [v4] xfs: fix the symbolic link assert in xfs_ifree:
This is also reproducible in RHEL 6 (kernel-2.6.32-419.el6).
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
*** Bug 1088730 has been marked as a duplicate of this bug. ***
725eb1e xfs: fix the symbolic link assert in xfs_ifree
hm, possibly depending on
Author: Christoph Hellwig <email@example.com>
Date: Wed Jul 4 11:13:29 2012 -0400
xfs: clean up xfs_inactive
Will have to decide how important this one really is.
I'm going to close this as WONTFIX for now; it's not a trivial upstream patch application and the bug, as far as we know, is only seen in the xfstest specifically designed to trigger it.
If we get a customer report of the problem, we can re-open & re-examine this bug.