Millions of Parity Reads and Writes without Parity Check


Go to solution Solved by apandey,

Recommended Posts

Hello! Well the title says it all. I am having a very very peculiar issue where usually overnight but also sometimes throughout the day, something is continually reading and writing to the array (usually Disk2). Now this is sometimes a "common" problem with unraid. The part that is thrown me for a curve is that it is ALSO reading and writing an equivalent amount of data to the parity drive. No errors being corrected that I can see.

 

1) I have tried restarting docker which I thought fixed the problem for a couple days... but then it came back.

2) iotop was not useful given the intermittent issue

3) I tried disabling party check scheduler which again stopped the problem for a couple days I think but could be a coincidence

4) I disabled ALL docker containers which did nothing so I dont think it is a container writing that much.

 

 

Any help or guidance or direction is appreciated! I got to solve this before my drives go bust!

 

apollo-diagnostics-20230125-0955.zip

Link to comment
1 hour ago, apandey said:

This sounds normal to me. Any writes to any disk in the array will need the corresponding part of parity to be recomputed and written. That is how parity works

 

See here - https://wiki.unraid.net/Parity#How_parity_works

 

1 hour ago, JorgeB said:

That's expected, anything written to an array disk will also be written to parity, and with default read/write/modify, parity is also read.

Thank you guys for the comments! I guess I was thrown by the parity reads matching the array disks. I have downloaded and set up the file activity plugin. I ran it so I guess I will just have to wait and see if it catches anything suspicious going on. I will report back once it happens again to see if it catches anything. Cheers!

Link to comment
  • 2 weeks later...
On 1/25/2023 at 10:42 AM, apandey said:

Perhaps you can try file activity plugin to narrow down the cause of writes

So from inspecting the file activity, I could not find the culprit... however... the weird writing issue has gone away... the only major change I have made was disabling NZBget from writing logs for every action, but that would only impact my writes to the cache drives.... so, oh well. I guess it solved itself! Thank you!

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.