From a84250b902515e7f5c9c4cd44885ca98b738b392 Mon Sep 17 00:00:00 2001 From: Andreas Dilger Date: Wed, 22 Jun 2016 11:36:10 -0600 Subject: [PATCH] LU-7418 tests: avoid background writeout in sanity 29 Intermittent failures of sanity.sh test_29 are caused by background writeout starting (or continuing) after the MDC DLM locks were cancelled, requiring the layout lock to be re-fetched from the MDS. Cancelling the DLM locks via "lru_size=clear" is not enough, since this will not cancel any locks that are currently in use. Instead, ensure that all the dirty pages from previous tests are written out so that no new writes are started during the test. Signed-off-by: Andreas Dilger Change-Id: Ie45965a974e0cd170f969fa122e1762c2361c278 Reviewed-on: http://review.whamcloud.com/20929 Tested-by: Jenkins Tested-by: Maloo Reviewed-by: Oleg Drokin --- lustre/tests/sanity.sh | 1 + 1 file changed, 1 insertion(+) diff --git a/lustre/tests/sanity.sh b/lustre/tests/sanity.sh index 53d33b5..66c1ccc 100644 --- a/lustre/tests/sanity.sh +++ b/lustre/tests/sanity.sh @@ -2119,6 +2119,7 @@ run_test 28 "create/mknod/mkdir with bad file types ============" test_29() { [ $PARALLEL == "yes" ] && skip "skip parallel run" && return 0 + sync; sleep 1; sync # flush out any dirty pages from previous tests cancel_lru_locks test_mkdir $DIR/d29 touch $DIR/d29/foo -- 1.8.3.1