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

0.6.0-rc5 tests failed on Gentoo kernel 3.0 #350

Closed
richardinside opened this issue Aug 1, 2011 · 3 comments
Closed

0.6.0-rc5 tests failed on Gentoo kernel 3.0 #350

richardinside opened this issue Aug 1, 2011 · 3 comments
Milestone

Comments

@richardinside
Copy link

Linux server 3.0.0-gentoo #2 SMP Sun Jul 31 15:20:56 GMT 2011 x86_64 Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz GenuineIntel GNU/Linux

make check
==================================== ZTEST ====================================
................
Pass 3, Complete, 0 ENOSPC, 32.7% of 746M used, 56% done, 2m12s to go
Setting dataset ztest/temp_20 to sync always
Setting dataset ztest/temp_9 to sync always
Setting dataset ztest/temp_4 to sync always
Setting dataset ztest/temp_2 to sync always
Setting dataset ztest/temp_2 to sync always
Setting dataset ztest/temp_7 to sync always
Setting dataset ztest/temp_5 to sync always
error: Pool 'ztest' has encountered an uncorrectable I/O failure and the failure mode property for this pool is set to panic.
child died with signal 6
make[1]: *** [check] Error 3
make[1]: Leaving directory `/root/soft/zfs/zfs-0.6.0-rc5/scripts'
make: *** [check-recursive] Error 1

Sometimes ZTEST test completes successfully, but zconfig always fails with:
/zconfig.sh -c
Skipping test 10 which requires the scsi_debug module and the /usr/bin/lsscsi utility
1 persistent zpool.cache cannot create 'test1': pool already exists
Fail (2)

@richardinside
Copy link
Author

First problem resolved. ZTEST was failing due to small /tmp size.
ZCONFIG still fails

@behlendorf
Copy link
Contributor

Yes, zconfig.sh still has some failures on newer kernels which are being worked on. However, in practice these issues are observed on a real system. Of course we will still get them fixed.

@behlendorf
Copy link
Contributor

This is was fixed by openzfs/spl@64c075c

sdimitro pushed a commit to sdimitro/zfs that referenced this issue May 23, 2022
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