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
-
22,842
-
4296
Description
sanity test 101b failed as follows:
== test 101b: check stride-io mode read-ahead ================= == 02:56:29 0.264963s, 63.3191MB/s Read-ahead success for size 8192 0.238399s, 70.3745MB/s Read-ahead success for size 16384 0.239034s, 70.1876MB/s Read-ahead success for size 32768 0.231213s, 72.5617MB/s Read-ahead success for size 65536 0.230497s, 72.7871MB/s Read-ahead success for size 131072 0.243734s, 68.8341MB/s Read-ahead success for size 262144 0.239763s, 69.9742MB/s Read-ahead success for size 524288 0.230390s, 72.8209MB/s Read-ahead success for size 1048576 Resetting fail_loc on all nodes...done. rm: cannot remove `/mnt/lustre': Device or resource busy test_101b returned 1 FAIL (7s)
Maloo report: https://maloo.whamcloud.com/test_sets/d06b18ee-6c23-11e0-b32b-52540025f9af
This is a test script issue.
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