Details
-
Bug
-
Resolution: Won't Fix
-
Minor
-
None
-
Lustre 2.8.0
-
autotest
-
3
-
9,977
-
9223372036854775807
Description
sanityn test 28 was recently removed from the ALWAYS_EXCEPT list by accident and is still failing. There is no real error message, but the output from the test on failure is
'error() without useful message, please fix'
Recently, there are many examples of this test failing and, thus, many logs of the failures. Here are just a couple:
https://testing.hpdd.intel.com/test_sets/d0ec87b2-530f-11e5-8228-5254006e85c2
https://testing.hpdd.intel.com/test_sets/7a462a70-5301-11e5-b798-5254006e85c2
From the test log output, it’s clear that this test needs to be updated; newdev was removed as an option to lctl many years ago:
== sanityn test 28: read/write/truncate file with lost stripes == 08:31:03 (1441355463) 2+0 records in 2+0 records out 2097152 bytes (2.1 MB) copied, 0.0383377 s, 54.7 MB/s No such command, type help error: setup: Operation already in progress error: destroy: invalid objid '12745:0' destroy OST object <objid> [num [verbose]] usage: destroy <num> objects, starting at objid <objid> run <command> after connecting to device <devno> --device <devno> <command [args ...]>
Until we fix the obvious issues, we don’t really know if the original bug/reason for ALWAYS_EXCEPT test 28 is still valid.
In sanityn, the reason for putting this test on the ALWAYS_EXCEPT list is due to bz=9977.