so that close has to update mtime and generate CL_MTIME
record in the changelog.
Signed-off-by: Alex Zhuravlev <bzzz@whamcloud.com>
Change-Id: I118172229c86ed5c201299de7476678689bf4cab
Reviewed-on: https://review.whamcloud.com/40508
Tested-by: jenkins <devops@whamcloud.com>
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Reviewed-by: John L. Hammond <jhammond@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Oleg Drokin <green@whamcloud.com>
compare_mtime_changelog $DIR/$tdir/$tfile
# Test CL_MTIME during close
- dd if=/dev/urandom of=$DIR/$tdir/${tfile}_2 bs=1M count=64 ||
- error "cannot create file $DIR/$tdir/${tfile}_2"
+ $MULTIOP $DIR/$tdir/${tfile}_2 O_2w4096c || error "multiop failed"
compare_mtime_changelog $DIR/$tdir/${tfile}_2
}
run_test 160l "Verify that MTIME changelog records contain the parent FID"