[LU-3795] replay-single test_58b test_58c: trusted.foo: No such attribute Created: 20/Aug/13 Updated: 21/Oct/13 Resolved: 26/Sep/13 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.5.0 |
| Fix Version/s: | Lustre 2.5.0 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Maloo | Assignee: | Nathaniel Clark |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | revzfs | ||
| Issue Links: |
|
||||||||||||||||||||
| Severity: | 3 | ||||||||||||||||||||
| Rank (Obsolete): | 9813 | ||||||||||||||||||||
| Description |
|
This issue was created by maloo for Nathaniel Clark <nathaniel.l.clark@intel.com> This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/383816e8-097f-11e3-901c-52540035b04c. The sub-test test_58b failed with the following error:
Info required for matching: replay-single 58b |
| Comments |
| Comment by Andreas Dilger [ 21/Aug/13 ] |
|
This looks like it also failed on non-zfs testing: and the first failure was on 2013-07-29 00:48:20 UTC and according to http://review.whamcloud.com/5537 the xattr cache patch landed on 07-29 also. |
| Comment by Andrew Perepechko [ 21/Aug/13 ] |
|
The first (ZFS) report is a duplicate of The second report does not look xattr cache related (no traces of xattr operations either in the MDS or in the client debug logs), "No such file or directory" probably relates to the fact that there was no such file or directory, rather than an xattr failure. |
| Comment by Peter Jones [ 26/Aug/13 ] |
|
Nathaniel Please verify whether this is still an issue after Peter |
| Comment by Nathaniel Clark [ 12/Sep/13 ] |
|
This is verified fixed by |
| Comment by Emoly Liu [ 26/Sep/13 ] |
|
I reopen this ticket because through investigation on "No such attribute" happens much more frequently than "No such file or directory". |
| Comment by Andrew Perepechko [ 26/Sep/13 ] |
|
The fixes were landed on Sep, 11 (see http://review.whamcloud.com/#/c/7208/), not two months ago. It's not clear whether your reports are based on sources more recent than of that date. https://maloo.whamcloud.com/test_sets/5bb89698-1a4f-11e3-a95b-52540035b04c was ran on Sep 10. |
| Comment by Emoly Liu [ 26/Sep/13 ] |
|
I searched Maloo test results in this link https://maloo.whamcloud.com/sub_tests/query?utf8=✓&test_set%5Btest_set_script_id%5D=f6a12204-32c3-11e0-a61c-52540025f9ae&sub_test%5Bsub_test_script_id%5D=fb022be0-32c3-11e0-a61c-52540025f9ae&sub_test%5Bstatus%5D=FAIL&sub_test%5Bquery_bugs%5D=&test_session%5Btest_host%5D=&test_session%5Btest_group%5D=&test_session%5Buser_id%5D=&test_session%5Bquery_date%5D=&test_session%5Bquery_recent_period%5D=&test_node%5Bos_type_id%5D=&test_node%5Bdistribution_type_id%5D=&test_node%5Barchitecture_type_id%5D=&test_node%5Bfile_system_type_id%5D=00437f32-318d-11e1-9c6d-5254004bbbd3&test_node%5Blustre_branch_id%5D=&test_node_network%5Bnetwork_type_id%5D=&commit=Update+results I didn't check each one. Maybe you are right, their parent commit is earlier than |
| Comment by Emoly Liu [ 26/Sep/13 ] |
|
Andrew, you are right. Sorry to reopen this one. |
| Comment by Andrew Perepechko [ 26/Sep/13 ] |
|
Thanks, Emoly. Please, reopen if the problem reoccurs in the future. |