Archive-Team
/
zfs
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 103 Wiki Activity

ZTS: zpool_resilver_restart 

Since the vdev initialize feature was integrated the ZTS
zpool_resilver_restart test has been hitting its internal
timeout more frequently.  This happens most often on
the coverage builder but not exclusively.  Increasing the
timeout for this test case prevents any false positives.

Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #8273
This commit is contained in:
Brian Behlendorf 2019-01-13 10:01:31 -08:00 committed by GitHub
parent 6955b40138
commit 99b0b5bc3f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
tests/zfs-tests/tests/functional/cli_root/zpool_resilver/zpool_resilver.cfg
View File

@ -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

4
tests/zfs-tests/tests/functional/cli_root/zpool_resilver/zpool_resilver_restart.ksh
View File

@ -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
@ -56,7 +56,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