ZFS tests should not run with scratch disks smaller than 10GB
I experienced some errors recently with the ZFS test suite. Specifically,
functional/cli_root/zpool_expand/zpool_expand_001_pos would hang forever. Upon inspection,
zpool destroy testpool1 was hanging because
testpool1 had come to a stop:
pool: testpool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM testpool ONLINE 0 0 0 c4t0d0 ONLINE 0 0 0 errors: No known data errors pool: testpool1 state: UNAVAIL status: One or more devices could not be used because the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://illumos.org/msg/ZFS-8000-5E scan: none requested config: NAME STATE READ WRITE CKSUM testpool1 UNAVAIL 0 0 0 insufficient replicas /dev/zvol/dsk/testpool/testfs/vol1 ONLINE 0 0 0 /dev/zvol/dsk/testpool/testfs/vol2 UNAVAIL 0 0 0 corrupted data /dev/zvol/dsk/testpool/testfs/vol3 ONLINE 0 0 0
The only thing I could think of was an I/O error because the volume is in a pool (
testpool, on one of the scratch disks) which is full. The pool was indeed nearly full. I increased the scratch disk size from 5GB to 10GB and the test completed successfully. I think in general the test suite should refuse to run with scratch disks smaller than 10GB.