These did not do enough metadata operations to
trigger any exports between MDS ranks, so it is
not useful to have them running in the multimds
suite.
Signed-off-by: John Spray <john.spray@redhat.com>
...so that we can't "pass" the test by accidentally
failing to ever export anything automatically
like in http://tracker.ceph.com/issues/20131
Signed-off-by: John Spray <john.spray@redhat.com>
This allows the client/admin to pin a directory tree to a particular rank,
preventing its export by the dynamic balancer.
Fixes: http://tracker.ceph.com/issues/17834
Signed-off-by: Patrick Donnelly <pdonnell@redhat.com>
qa/suites: drop 'fs' facet, and add 'objectstore' facet where missing
Reviewed-by: Josh Durgin <jdurgin@redhat.com>
Reviewed-by: Jason Dillaman <dillaman@redhat.com>
There are places where we were testing xfs vs btrfs on
filestore and now want to cover both filestore and bluestore.
Signed-off-by: Sage Weil <sage@redhat.com>
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>
