Recent testing on master with files with multiple components show that several tests fail due to ‘lfs getstripe’ with the index or the stripe count flags return multiple lines of output. If this impacts the Lustre test suites, this could impact exiting tools that use ‘lfs getstripe’ and expect output of a single value.
To demonstrate this, we have a file with three components:
Andreas Dilger has commented on this issue:
"lfs getstripe -c" should return a single value for the stripe count. In the design, this was the stripe count of the last instantiated component, since that is the best estimate for the number of stripes for the given file. In the implementation (AFAIK) it was the sum of all the instantiated stripe counts, which is also reasonable.
The following tests fail due to expecting a single value from ‘lfs getstripe’.
sanity test 27i, 27w, 27A - https://testing.hpdd.intel.com/test_sets/5cc43d3c-23b8-11e7-8920-5254006e85c2