-
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
Nonsensical zpool status output during scrub #8891
Comments
Already fixed in #8766, will be 0.8.1 |
I was looking for that but could not find it in a quick search. |
Oh, excellent. I presume the issue is entirely cosmetic and the underlying scrub operation does what it is supposed to? If so I'll just ignore it and wait for 0.8.1 :-) |
@tc1415 that's right. It's entirely cosmetic and the underlying scrub does correctly verify everything. |
Confirmed fixed in 0.8.1, so closing. |
System information
Describe the problem you're observing
After setting a scrub running and waiting a bit, zpool status produces nonsensical output reporting it has scanned many TB of data on a pool with only 212 GB of data in it.
The man page notes that it can "slightly" exceed 100 % but this is three orders-of-magnitude higher!
Describe how to reproduce the problem
zpool scrub pool
Wait a bit (or do
watch zpool status pool
and watch it)zpool status pool
Observe output.
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: