[LU-9476] sanity tests 102d, f, j skipped looking for ‘lustre-aware’ tar Created: 09/May/17 Updated: 07/Oct/17 Resolved: 07/Oct/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.10.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | James Nunez (Inactive) | Assignee: | Bob Glossman (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | test | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
sanity tests 102d, 102f, and 102j are skipped looking for a lustre-aware version of tar: SKIP: sanity test_102d lustre-aware tar is not installed According to Andreas Dilger:
Thus, we need to |
| Comments |
| Comment by Andreas Dilger [ 18/May/17 ] |
|
... and the Lustre User Manual needs to be updated to also include --xattrs-inlude="lustre.*" in the "restore" part of the directions. |
| Comment by ZhangWei [ 03/Aug/17 ] |
|
Hi Nunez and Dilger, |
| Comment by Andreas Dilger [ 05/Aug/17 ] |
|
All new resigns of tar can handle xattrs, but only the RHEL 6.x version explicitly requested that "lustre.*" xattrs be restored (hence the "lustre" string was in the binary). With very old tar versions (e.g. RHEL 5.x) there was no xattr support, so these tests were skipped if the "lustre" string was not found in the binary. It would be great if you could fix the tests themselves to explicitly request that lustre xattrs are restored, as written in the original bug description. This should work for any version of tar that is being tested today, so there shouldn't need to be a conditional check for the tar version in the test. |
| Comment by Bob Glossman (Inactive) [ 07/Oct/17 ] |
|
fixed by mod for |