I was unable to replicate:
```
write: No space left on device
8245278720 bytes transferred in 1880.011589 secs (4385760 bytes/sec)
```
But that could simply be that I don't get dbuf eviction triggered.
However I did find some differences between the two versions, perhaps it will
help.
--
You
@lundman pushed 1 commit.
d6cda08 Correct differences in arc.c for crypto
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
@ahrens the failure has been originally observed on the OpenZFS Jenkins
pipelines, for instance:
http://jenkins.open-zfs.org/blue/organizations/jenkins/openzfs%2Fopenzfs/detail/PR-510/8/pipeline
The PR description is just a stripped-down version of the failing test to
demonstrate the race
prashks commented on this pull request.
Yes the `remove_mirror.ksh` changes looks good (need to wait for the removal
before the next steps in the test) and I was planning to upstream this.
Apparently this is seen at times during the precommit runs and is just a timing
related issue.
But i'm
@prashks could you take a look?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/534#issuecomment-363157772
--
openzfs-developer
Archives:
The fix looks reasonable (aside from the runfile changes), but can you clarify
how the testing in the PR description is related to the test failure? It looks
like you're trying to `zpool remove` part of a mirror, but I think you should
be doing `zpool remove testpool mirror-1`. Do you have
