The parity drive keeps reading/writing, but a lot more writing than reading. From what I can see the appdata and system shares are on the cache drive. If I turn the Docker off, it still randomly writes. In the past, I made the primary storage to array for the appdata/system shares, to move the files on the array to the cache. However, when I try to do that again, the cache drive doesn't appear under secondary storage.

 

I did recently install a new cache drive, so all the shares were temporarily on the array when I was setting stuff up.

diagnostics-20240929-1220.zip

Edited September 29, 20241 yr by MrTing
clarification

55 minutes ago, MrTing said:

In the past, I made the primary storage to array for the appdata/system shares, to move the files on the array to the cache. However, when I try to do that again, the cache drive doesn't appear under secondary storage.

That is the wrong way around.    You need primary storage to be the cache, secondary storage the array, and mover direction to be array->cache.

*face palm*. I incorrectly remembered what i did previously, thank you.

 

Not 100% that it fixed it, before i turned off my docker and it kept writing. now it doesnt write when the docker is off but does when the docker is on.. will check tomorrow.

Edited September 30, 20241 yr by MrTing
new info

So, turns out it still occurs, even with the docker off,  but a lot less frequently now.. Not sure what else it could be

diagnostics-20240930-1106.zip

Edited October 1, 20241 yr by MrTing
new findings

Bump

Any writes to the array will result in writes to parity, and there can only be writes to parity if something is written to one of the array disks.

Yes. The primary storage for all the shares is the cache, the mover is not running, and the docker is off. So I'm having trouble finding out what is being read & written to the array/parity drive.

Stop exporting any shares in case it's that.

After doing that, the writes stopped occurring when the docker was off. When I turned the docker back on, it returned. It was a bit weird, but after going by container by container, I found that it was Nextcloud and Sabnzbd writing logs. And I remembered previously I changed their settings from changing /mnt/cache/appdata/binhex-sabnzbdvpn to /mnt/user/appdata/binhex-sabnzbdvpn, because i read that have it as /mnt/cache isnt proper. So after changing it back to /mnt/cache, all is good. Ty for helping me