We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
pmempool_transform/TEST9 pmemobj9.log <libpmemobj>: <1> [heap.c:539 zone_calc_size_idx] assertion failure: heap_size >= zone_id * (sizeof(struct zone) + sizeof(struct chunk) * ((65535) - 7))
The problem has been solved by changing the order of devdax devices in test config file.
It seems that in some scenarios "old data" was treated as new data and not initialized from scratch.
Are you willing to submit a pull request with a proposed change? (Yes, No)
Requested priority: (Showstopper, High, Medium, Low)
The text was updated successfully, but these errors were encountered:
When the original order of Device DAXes was restored, the issue did not reproduce anymore.
Sorry, something went wrong.
No branches or pull requests
ISSUE: Invalid heap size when creating a new pool on a used-before devdax.
Environment Information
Please provide a reproduction of the bug:
pmempool_transform/TEST9 pmemobj9.log <libpmemobj>: <1> [heap.c:539 zone_calc_size_idx] assertion failure: heap_size >= zone_id * (sizeof(struct zone) + sizeof(struct chunk) * ((65535) - 7))
The problem has been solved by changing the order of devdax devices in test config file.
It seems that in some scenarios "old data" was treated as new data and not initialized from scratch.
How often bug is revealed: (always, often, rare):
Actual behavior:
Expected behavior:
Details
Additional information about Priority and Help Requested:
Are you willing to submit a pull request with a proposed change? (Yes, No)
Requested priority: (Showstopper, High, Medium, Low)
The text was updated successfully, but these errors were encountered: