-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
strange message #72
Comments
The zconfig.sh test suite requires that you start it without any of the ZFS kernel modules loaded. This is because the test suite verifies the correct ZFS behavior when the modules are loaded/unload among other things. You just need to remove the ZFS module stack by running the command in the error message. This will unload all the ZFS kernel modules so you can run the regression test. zfs.sh -u |
Closing issue. |
Closed
dajhorn
referenced
this issue
in zfsonlinux/pkg-zfs
Jan 6, 2012
If the lsb-release package is installed on an Arch Linux distribution, the configure step will incorrectly detect the running distribution as Ubuntu. This is a result of both distributions providing an /etc/lsb-release file, and the Ubuntu VENDOR check being performed first. Since the Arch Linux test check's for a file more specific to the Arch Linux distribution, moving Arch Linux's VENDOR check above Unbuntu's check provides a quick and easy solution. Signed-off-by: Prakash Surya <surya1@llnl.gov> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes #72
ahrens
added a commit
to ahrens/zfs
that referenced
this issue
Sep 5, 2019
Signed-off-by: Matthew Ahrens <mahrens@delphix.com>
Closed
Closed
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
/usr/libexec/zfs/zconfig.sh -c
1 persistent zpool.cache zfs.sh: Unload these modules with 'zfs.sh -u':
zfs zcommon zunicode znvpair zavl spl zlib_deflate
i have also zfs-fuse installed and in use.
The text was updated successfully, but these errors were encountered: