Details
-
Bug
-
Resolution: Cannot Reproduce
-
Critical
-
None
-
Lustre 2.5.0
-
3
-
9333
Description
This issue was created by maloo for gmahajan <gmahajan@ddn.com>
This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/10687878-f427-11e2-b8a2-52540035b04c.
The sub-test test_58c failed with the following error:
test_58c failed with 2
Info required for matching: replay-single 58c
CMD: wtm-12vm3 lctl set_param fail_loc=0
fail_loc=0
getfattr: /mnt/lustre2/d0.replay-single/d58/f.replay-single.58c: No such file or directory
replay-single test_58c: @@@@@@ FAIL: test_58c failed with 2
Trace dump:
= /usr/lib64/lustre/tests/test-framework.sh:4202:error_noexit()
= /usr/lib64/lustre/tests/test-framework.sh:4229:error()
= /usr/lib64/lustre/tests/test-framework.sh:4483:run_one()
= /usr/lib64/lustre/tests/test-framework.sh:4516:run_one_logged()
= /usr/lib64/lustre/tests/test-framework.sh:4371:run_test()
= /usr/lib64/lustre/tests/replay-single.sh:1462:main()
Dumping lctl log to /logdir/test_logs/2013-07-23/lustre-reviews-el6-x86_64-review-zfs-1_3_1_16860_-70004232338460-021952/replay-single.test_58c.*.1374596486.log
Attachments
Activity
| Resolution | New: Cannot Reproduce [ 5 ] | |
| Status | Original: Reopened [ 4 ] | New: Closed [ 6 ] |
| Comment |
[ Saw this failure in FAILOVER test for SLES11 SP3 ldiskfs client and server: lustre-b2_6-rc2 https://testing.hpdd.intel.com/test_sets/79386184-0f6e-11e4-aee3-5254006e85c2 ] |
| Resolution | Original: Cannot Reproduce [ 5 ] | |
| Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
| Resolution | New: Cannot Reproduce [ 5 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Fix Version/s | Original: Lustre 2.5.0 [ 10295 ] |
The Maloo searching result shows that LU-3625 has disappeared since Aug.7 (probably fixed by some commit)? And the other issue on replay-single.sh test_58b/c(No such attribute) in LU-3795 was fixed in Sep.11.
Could we lower priority of this bug?
We would still like some investigation of the source of the problem even if the failure is only on ZFS. Did this start failing at a certain time, maybe related to some patch introducing a regression?
This failure for ldiskfs hasn't been seen in recent one month, but it still happens for zfs, so I add label "zfs".
| Labels | New: zfs |
If it is no longer happening I think that it should be enough to close it as cannot repro and we can reopen the ticket if it is seen again.