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

IO error with overwriting when ZVOL space is full #11455

Closed
TimLand opened this issue Jan 12, 2021 · 6 comments
Closed

IO error with overwriting when ZVOL space is full #11455

TimLand opened this issue Jan 12, 2021 · 6 comments
Labels
Component: ZVOL ZFS Volumes Status: Stale No recent activity for issue Type: Defect Incorrect behavior (e.g. crash, hang)

Comments

@TimLand
Copy link

TimLand commented Jan 12, 2021

System information

Type Version/Name
Distribution Name Ubuntu
Distribution Version 16.04
Linux Kernel 4.4.0-24
Architecture x86
ZFS Version 0.8.6-1
SPL Version 0.8.6-1

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

zfs
zfs-2
zfs-3

@TimLand TimLand added Status: Triage Needed New issue which needs to be triaged Type: Defect Incorrect behavior (e.g. crash, hang) labels Jan 12, 2021
@TimLand TimLand changed the title A problem with overwriting when ZVOL space is full IO error with overwriting when ZVOL space is full Jan 13, 2021
@TimLand
Copy link
Author

TimLand commented Jan 13, 2021

zfs-4
zfs-5

@sempervictus
Copy link
Contributor

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).

@ghost ghost added Component: ZVOL ZFS Volumes and removed Status: Triage Needed New issue which needs to be triaged labels Jan 20, 2021
@stale
Copy link

stale bot commented Jan 21, 2022

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.

@stale stale bot added the Status: Stale No recent activity for issue label Jan 21, 2022
@behlendorf
Copy link
Contributor

If this pool is using raidz, then this issue appears to be a duplicate of #8973 which was fixed in the 2.0 release.

@stale stale bot removed the Status: Stale No recent activity for issue label Jan 21, 2022
@stale
Copy link

stale bot commented Jan 22, 2023

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.

@stale stale bot added the Status: Stale No recent activity for issue label Jan 22, 2023
@behlendorf
Copy link
Contributor

Closing as duplicate of #8973

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: ZVOL ZFS Volumes Status: Stale No recent activity for issue Type: Defect Incorrect behavior (e.g. crash, hang)
Projects
None yet
Development

No branches or pull requests

3 participants