Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 1.8.6
-
None
-
Branch: b1_8 (Revision: c5c2986be490b2fbceb4b38d6c983d279f4bbcf8)
Distro/Arch: RHEL6/x86_64 (patchless client), RHEL5/x86_64 (server)
Network: tcp
-
3
-
20,569
-
5023
Description
sanity test 170 failed as follows:
== test 170: test lctl df to handle corrupted log ===================== == 03:15:15 sanity test_170: @@@@@@ FAIL: expected 248 bad lines, but got 249 Dumping lctl log to /home/yujian/test_logs/2011-04-21/021725/sanity.test_170.*.1303380918.log tar: Removing leading `/' from member names /home/yujian/test_logs/2011-04-21/021725/sanity-1303380918.tar.bz2 sanity test_170: @@@@@@ FAIL: test_170 failed with 1 Dumping lctl log to /home/yujian/test_logs/2011-04-21/021725/sanity.test_170.*.1303380945.log tar: Removing leading `/' from member names /home/yujian/test_logs/2011-04-21/021725/sanity-1303380945.tar.bz2 Resetting fail_loc on all nodes...done.
Maloo report: https://maloo.whamcloud.com/test_sets/d06b18ee-6c23-11e0-b32b-52540025f9af
This is an known issue on b1_8 as bug 20569.
Attachments
Issue Links
- Trackbacks
-
Lustre 1.8.x known issues tracker While testing against Lustre b18 branch, we would hit known bugs which were already reported in Lustre Bugzilla https://bugzilla.lustre.org/. In order to move away from relying on Bugzilla, we would create a JIRA