Sage Weil 32719a60f7 rados: specify xfs ... If no fs is specified, the OSD is created on /, and the scratch devices aren't used at all. That means ext4, and the long file name lameness. Signed-off-by: Sage Weil <sage@redhat.com>		2016-04-14 14:31:44 -04:00
..
basic	rados/basic: test over xfs (not just btrfs)	2016-04-13 13:14:04 -04:00
monthrash	rados_api_tests: reduce the osd_max_object_name_len value	2016-04-07 15:35:30 -07:00
multimon	rados: specify xfs	2016-04-14 14:31:44 -04:00
objectstore	rados: specify xfs	2016-04-14 14:31:44 -04:00
singleton	admin malloc interface testsReviewed-by: Josh Durgin <jdurgin@redhat.com>	2016-04-07 15:38:22 -07:00
singleton-nomsgr	rados/singleton-nomsgr: add lfn upgrade tests	2016-04-07 15:35:30 -07:00
thrash	rados_api_tests: reduce the osd_max_object_name_len value	2016-04-07 15:35:30 -07:00
thrash-erasure-code	suites: radosbench 180 -> 150s	2016-03-31 12:27:11 -04:00
thrash-erasure-code-big	openstack: define the resources required to run a rados suite	2016-03-30 01:45:14 +02:00
thrash-erasure-code-isa
thrash-erasure-code-shec	openstack: define the resources required to run a rados suite	2016-03-30 01:45:14 +02:00
upgrade	suites: radosbench 180 -> 150s	2016-03-31 12:27:11 -04:00
verify	rados_api_tests: reduce the osd_max_object_name_len value	2016-04-07 15:35:30 -07:00