-
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
IO error with overwriting when ZVOL space is full #11455
Comments
It might be useful to add the ZVOL tag to all of these ZVOL issues. The subsystem is neglected and having a face full of "issues with the component" tags on the issues pages might provide impetus for someone to address (or stop trying to use them). |
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions. |
If this pool is using raidz, then this issue appears to be a duplicate of #8973 which was fixed in the 2.0 release. |
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions. |
Closing as duplicate of #8973 |
System information
Describe the problem you're observing
We used the vdbench tool to perform a stress test on ZVOL. After running for a few days, vdbench got an io error exception. We found that the ZVOL volume was full. But we use the dd ( dd if=/dev/zero of=/dev/zvol/b6bd4b4c90844cbe8fbe0222ecb23109/0aa8e41118094174b2392f42b42c21f7 bs=1M count=10 oflag=direct)tool writing data start from 0 position and still get the io error exception.
Describe how to reproduce the problem
The easiest way to do this is, write fill up the zvol, then dd it write some data start from 0 offset
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: