From 87f13869acc251febf9be578d7767e3587fb8615 Mon Sep 17 00:00:00 2001 From: Elena Gryaznova Date: Tue, 11 May 2010 14:23:08 +0400 Subject: [PATCH] b=20918 report max recovery time estimated i=Andrew.Perepechko --- lustre/tests/recovery-random-scale.sh | 3 +++ 1 file changed, 3 insertions(+) diff --git a/lustre/tests/recovery-random-scale.sh b/lustre/tests/recovery-random-scale.sh index fcbd393..3cf5a16 100644 --- a/lustre/tests/recovery-random-scale.sh +++ b/lustre/tests/recovery-random-scale.sh @@ -47,6 +47,8 @@ build_test_filter check_and_setup_lustre rm -rf $DIR/[df][0-9]* +max_recov_time=$(max_recovery_time) + # the test node needs to be insulated from a lustre failure as much as possible, # so not even loading the lustre modules is ideal. # -- umount lustre @@ -290,6 +292,7 @@ while [ $ELAPSED -lt $DURATION -a ! -e $END_RUN_FILE ]; do log "WARNING: failover, client reintegration and check_client_loads time exceeded SERVER_FAILOVER_PERIOD - MINSLEEP ! Failed to load the filesystem with I/O for a minimum period of $MINSLEEP $reqfail times ( REQFAIL=$REQFAIL ). This iteration, the load was only applied for sleep=$sleep seconds. +Estimated max recovery time : $max_recov_time Probably the hardware is taking excessively long to boot. Try to increase SERVER_FAILOVER_PERIOD (current is $SERVER_FAILOVER_PERIOD), bug 20918" [ $reqfail -gt $REQFAIL ] && exit 6 -- 1.8.3.1