Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zfs test suite uses local pool name of 'tank' which failes if a pool of same name exists #93

Closed
stevecs opened this issue Feb 7, 2011 · 2 comments

Comments

@stevecs
Copy link

stevecs commented Feb 7, 2011

The test suite zconfig.sh uses the common name of 'tank' (which is described in pretty much all documentation as an example pool name). If a user is trying to run the test suite and already has a pool by that name the test suite will fail starting at the zpool import/export device stage due to more than one matching pool.

Suggest changing the test suite pool name to something much less common.

@stevecs
Copy link
Author

stevecs commented Feb 7, 2011

Note, this appears to also be a problem in zfault.sh as well.

@behlendorf
Copy link
Contributor

Good idea. We'll revisit what the right thing to do here is when we rework to test infrastructure to handle testing the Posix interface.

dajhorn referenced this issue in zfsonlinux/pkg-zfs Sep 7, 2012
When various kernel debuging options are enabled this allocation
may be larger than usual as shown by the following warning.  It
is in no way harmful so we suppress the warning.

  SPL: large kmem_alloc(40960, 0x80d0) at
  tsd_hash_table_init:358 (76495/76495)

Signed-off-by: Brian Behlendorf <[email protected]>
Closes #93
sdimitro pushed a commit to sdimitro/zfs that referenced this issue Feb 14, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants