Change Details

Set up zpools with a unique name, stash the zpool name away in a file pointed to by $ZPOOL_NAME_FILE, then restore them in the cleanup routines. This will fix issues with the tests where they are creating a zpool once with a deterministic name and tearing it down multiple times, and is a more concurrency-safe solution.

Set up zpools with a unique name, stash the zpool name away in a file pointed to by $ZPOOL_NAME_FILE (which is relative to a per-testcase generated temporary directory), then restore them in the cleanup routines. This will fix issues with the tests where they are creating a zpool once with a deterministic name and tearing it down multiple times, and is a more concurrency-safe solution.

Set up zpools with a unique name, stash the zpool name away in a file pointed to by $ZPOOL_NAME_FILE (which is relative to a per-testcase generated temporary directory), then restore them in the cleanup routines. This will fix issues with the tests where they are creating a zpool once with a deterministic name and tearing it down multiple times, and is a more concurrency-safe solution.