Appreciate you looking into this, I was only able to test your builds
for about 5 hours on generic kernel version so far (doing some hardware
upgrades at the moment, but my current test system is torture-test
stable).
My test hardware was 2x (westmere) Intel Xeon E5620's (2 NUMA nodes)
with 12GB
Thanks for looking into this, I'll test that build tonight but I assume
I'll see similar results.
In my previous tests with this commit applied I still occasionally ran
into the error (albeit far less often, sometimes not at all, or rather
quickly) and also some other traces regarding pthreads
Sorry, correction to above: I meant perhaps something changed since
4.4.11 since the 4.4.10 based xenial kernels seem fine (except the
curious issue with lowlatency build). I've run into some stack traces
regarding __pthread and some occasional failures in the spare tests with
"returned 0,
Interestingly this fixes the issue in 4.4.0-23-generic but not
4.4.0-23-lowlatency, and it appears my local builds of master-next on
both 4.4.0-24-generic and 4.4.0-24-lowlatency fail still. perhaps
something in the 4.4.10 sublevel patches changed something. I've also
merged 4.4.11 and 4.4.12 into
** Description changed:
Problem: Running ztest repeatedly for long periods of time eventually
results in "zdb: can't open 'ztest': No such file or directory"
This bug affects the xenial kernel built-in ZFS as well as the package
zfs-dkms. I don't believe ZFS 0.6.3-stable is affected,
** Description changed:
Problem: Running ztest repeatedly for long periods of time eventually
results in "zdb: can't open 'ztest': No such file or directory"
This bug affects the xenial kernel built-in ZFS as well as the package
- zfs-dkms.
+ zfs-dkms. I don't believe ZFS 0.6.3-stable is
Public bug reported:
Problem: Running ztest repeatedly for long periods of time eventually
results in "zdb: can't open 'ztest': No such file or directory"
This bug affects the xenial kernel built-in ZFS as well as the package
zfs-dkms. I don't believe ZFS 0.6.3-stable is affected, as the
