Replies: 1 comment
-
If you don't see anything listed after a scrub, you're likely fine. Even if you did, it won't let you randomly read mangled data, it'll return EIO if you try. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I had
zpool status
report this earlier today:On reviewing the kernel log, I saw that both the drives in mirror-2 had experienced some I/O errors 1 hour apart from each other. In the past, whenever one drive in a mirror was FAULTED due to too many errors, I always cleared the zpool, which caused a resilver, and everything was honky dory.
This was the first time both drivers in a mirror experienced I/O errors (nearly) simultanelously - before I could catch the first error and resilver the damaged drive. Moreover, this is the first time that a drive was FAULTED in the middle of a scrub.
I ran "zpool clear" regardless, as I wanted the FAULTED drive to be brought online without delay and the ongoing scrub had 40 hours left to run. Now
zpool status
says:Evidently, the faulted drive in the mirror is suffering further I/O errors even during the resilver.
Unfortunately, I have not kept a copy of the final status line reported by the first "zpool status".
What I'd like to know is if all these errors have caused any data corruption and if so, in which files.
Have I lost/masked this information with the "zpool clear", or does the fact that I'm getting "No known data errors" mean that my data is safe?
Does the fact that both mirrors said "(repairing)" mean that there was data corruption on both drives of the mirror vdev? Was it dumb to clear the zpool - should I have waited for the scrub to complete - despite the risks inherent in running the filesystem for 2 days with only a single ONLINE copy?
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions