These were running so few ops that they weren't
giving any meaningful exercise to a multimds
system beyond what we're already covering in
the fs suite.
Signed-off-by: John Spray <john.spray@redhat.com>
The thrasher expects in some scenarios for the cluster to stabilize with
a new MDS taking over when there are no standbys available. This can
cause the thrasher to quit because the cluster never stabilizes.
Signed-off-by: Patrick Donnelly <pdonnell@redhat.com>
Quotas don't work with kclient, and multimds tasks
are run against kclient. We don't need to run this
against fuse here because it's a basic correctness
test that's run against fuse in the fs suite.
Fixes: http://tracker.ceph.com/issues/18600
Signed-off-by: John Spray <john.spray@redhat.com>
...so that we can selectively disable those
which are not appropriate for multimds testing, or
which are not kclient compatible (all multimds workunits
run against both kclient and fuse).
Signed-off-by: John Spray <john.spray@redhat.com>
