Permalink
Browse files

ZTS: zpool_resilver_restart

Since the vdev initialize feature was integrated the ZTS
zpool_resilver_restart test has been failing.  But only on the
coverage builder.  This test has always taken longer on this
builder so we're going to try increasing the timeout.

The vdev initialize functionally should not have slowed down
this case this.  This change is primary to debug the issue.

Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
TEST_ZTEST_SKIP="yes"
TEST_ZFSTESTS_TAGS="zpool_resilver"
  • Loading branch information...
behlendorf committed Jan 12, 2019
1 parent 6955b40 commit e9ea1cb2089120a3532f85a42dbbe0c83de0bd31
@@ -27,4 +27,4 @@ export DISK1=$(echo $DISKS | nawk '{print $1}')
export DISK2=$(echo $DISKS | nawk '{print $2}')
export DISK3=$(echo $DISKS | nawk '{print $3}')

export MAXTIMEOUT=80
export MAXTIMEOUT=300
@@ -33,7 +33,7 @@
# "Verify 'zpool resilver' restarts in-progress resilvers"
#
# STRATEGY:
# 1. Write some data and detatch the first drive so it has resilver
# 1. Write some data and detach the first drive so it has resilver
# work to do
# 2. Repeat the process with a second disk
# 3. Reattach the drives, causing the second drive's resilver to be
@@ -45,6 +45,7 @@ verify_runnable "global"

function cleanup
{
zpool status -i
log_must set_tunable32 zfs_scan_suspend_progress 0
log_must rm -f $mntpnt/biggerfile1
log_must rm -f $mntpnt/biggerfile2
@@ -56,7 +57,7 @@ log_assert "Verify 'zpool resilver' restarts in-progress resilvers"

mntpnt=$(get_prop mountpoint $TESTPOOL/$TESTFS)

# 1. Write some data and detatch the first drive so it has resilver work to do
# 1. Write some data and detach the first drive so it has resilver work to do
log_must file_write -b 524288 -c 1024 -o create -d 0 -f $mntpnt/biggerfile1
log_must sync
log_must zpool detach $TESTPOOL $DISK2

0 comments on commit e9ea1cb

Please sign in to comment.