From ba557f10baf7ce668c9e1d7e1cb13d5d9f76a6cf Mon Sep 17 00:00:00 2001 From: M S Vishwanath Bhat Date: Wed, 28 Dec 2011 12:13:33 +0530 Subject: BUG:2645 -- Validates 'volume top write-perf' with zero block-size and zero count. Change-Id: I6f9bad5dff870ec555ba49bacf7bca8ed89a2333 BUG: 2645 Signed-off-by: M S Vishwanath Bhat --- dvm/2645/testcase | 42 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100755 dvm/2645/testcase diff --git a/dvm/2645/testcase b/dvm/2645/testcase new file mode 100755 index 0000000..9ac520b --- /dev/null +++ b/dvm/2645/testcase @@ -0,0 +1,42 @@ +#!/bin/bash + + +function create_data_on_mountpoint () +{ + for i in {1..100} + do + dd if=/dev/zero of=$FUSE_MOUNT/$i bs=128K count=100 2>/dev/null 1>/dev/null; + dd if=$FUSE_MOUNT/$i of=/dev/null bs=128K count=100 2>/dev/null 1>/dev/null; + done +} + + +function check_volume_top_write_perf () +{ + $GLUSTERFSDIR/gluster volume create $global_bug_id $(hostname):$EXPORT_DIR/$global_bug_id/brick1 2>/dev/null 1>/dev/null; + $GLUSTERFSDIR/gluster volume start $global_bug_id 2>/dev/null 1>/dev/null; + sleep 2 + + #latency-measurement should be on for 'top write-perf' to capture throughput of files + $GLUSTERFSDIR/gluster volume set $global_bug_id latency-measurement on 2>/dev/null 1>/dev/null; + + mount_glusterfs $global_bug_id; + create_data_on_mountpoint; + + $GLUSTERFSDIR/gluster volume top $global_bug_id write-perf bs 1024 count 100 2>/dev/null 1>/dev/null; + ret1=$? + + $GLUSTERFSDIR/gluster volume top $global_bug_id write-perf bs 0 count 100 | grep "block size should be an integer greater than zero" 2>/dev/null 1>/dev/null; + ret2=$? + + $GLUSTERFSDIR/gluster volume top $global_bug_id write-perf bs 1024 count 0 | grep "count should be an integer greater than zero" 2>/dev/null 1>/dev/null; + ret3=$? + + if [ $ret1 -eq 0 ] && [ $ret2 -eq 0 ] && [ $ret3 -eq 0 ]; then + return 0 + else + return 1 + fi +} + +source $cwd/regression_helpers; check_volume_top_write_perf -- cgit