From 61b1a7d68ccdd6fb0fe07c614a0c3f4086ae8a84 Mon Sep 17 00:00:00 2001 From: Eric Sandeen Date: Wed, 8 Feb 2012 12:30:07 -0600 Subject: [PATCH] 068: run fsstress in read/write mode Jan Kara was testing filesystem freeze, and was consistently locking up, although my tests of 068 were passing. He pointed out that he was running in read/write mode, and it was atime updates causing the trouble. Sure enough, dropping "-w" from fsstress locked me up too. Change this so we get better (and more realistic) coverage. Signed-off-by: Eric Sandeen cc: Jan Kara Reviewed-by: Dave Chinner --- 068 | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/068 b/068 index 6f08f188..b595d1df 100755 --- a/068 +++ b/068 @@ -79,8 +79,9 @@ touch $tmp.running nops=200 while [ -f "$tmp.running" ] do - # -w ensures that the only ops are ones which cause write I/O - $FSSTRESS_PROG -d $STRESS_DIR -w -p $procs -n $nops $FSSTRESS_AVOID \ + # We do both read & write IO - not only is this more realistic, + # but it also potentially tests atime updates + $FSSTRESS_PROG -d $STRESS_DIR -p $procs -n $nops $FSSTRESS_AVOID \ > /dev/null 2>&1 done -- 2.47.3