Sage Weil 08efb45889 OSDMonitor: do not add non-empty tier pool unless forced ... In general, users should not use non-empty pools as new tiers or else things can behave strangely: - the data sets are unrelated behavior will be... strange. - if the cache pool is not "new" and does not do the OMAP flag, the OSD will not know not to flush omap objects to an EC base tier - probably other random stuff I'm forgetting Allow a user to shoot themselves in the foot with --force-nonempty. Implements: #7457 Signed-off-by: Sage Weil <sage@inktank.com>		2014-03-03 21:11:17 -08:00
..
btrfs
client
fs	qa/fs/.gitignore	2013-07-26 21:06:14 -07:00
libceph
mds
mon/bootstrap
qa_scripts	librbd: better error when unprotect fails on unprotected snap	2013-12-31 16:26:07 -08:00
rbd
rgw
workunits	OSDMonitor: do not add non-empty tier pool unless forced	2014-03-03 21:11:17 -08:00
loopall.sh
Makefile	qa: move fs test binary into workunits dir so teuthology can build it	2013-07-05 11:16:08 -07:00
run_xfstests_qemu.sh	qa: don't run racy xfstest 008	2013-11-01 18:43:36 -07:00
run_xfstests.sh	qa: don't run racy xfstest 008	2013-11-01 18:43:36 -07:00
runallonce.sh
runoncfuse.sh
runonkclient.sh
setup-chroot.sh