Jump to content
LAST CALL on the Unraid Summer Sale! 😎 ⌛ ×

reconstructive write does not spin up disks


Recommended Posts

Hi,

 

I am in the middle of transferring TBs of data to my new Unraid NAS. I have reconstrive write set and it seems to work. But every once in a while I discover spun down discs and slower write performance. It was my impression that when reconstructive write is enabled every write should spin up all disks. Any idea?

 

Regards

   JP

Link to comment

I do but: That plugin also claims "reconstructive write" active. I set the number of disks to maximum (so it should never kick in and reduce it). And in order to make sure it does not fiddle with it I disabled it.

 

The setting under Disk settings does still show 

md_write_method = reconstruct write

 

and the plugin is disabled.

image.thumb.png.8a3a144da7475bb5bf59abefe501b0e8.png

 

Still believe me: After a while disks are spun down and I do see reads only from the spun up disks. Once I manually spin all disks up things are back to normal. VERY confusing.

 

Link to comment

Can't remember since which OS version, even you set reconstruct write, if multiple session write to array or file cross allocation to different disk, it will change to R/M/W and back.

 

So you should review file allocation setting.

Edited by Vr2Io
Link to comment

Yes concurrent reads will trigger RMW and it can switch back and forth between both many times a second... but I've never seen that scenario causing drives to go to sleep, it should only happen when things are being quite hammered so they'd be needed... but maybe I just don't have enough drives to see that.

Link to comment
22 minutes ago, Kilrah said:

but I've never seen that scenario causing drives to go to sleep

Agree. But may be some situation keeping in R-M-W long enough.... anyway haven't test or try to reproduce.

 

Does OP use parity, reconstruct write only have meaning with parity. Just to be confirm, or provide screenshots / diagnostic.

Edited by Vr2Io
Link to comment

6 data disks plus 2 parity

 

Currently 90-100 MB/sec constant writes (which is why I want reconstructive write to stay on). 🙂 

 

I currently set "spin down" to never for the time being and keep filling up to drives. Will try to reproduce in 1-2 weeks and if I can reproduce it will send diagnostics here.

 

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.

×
×
  • Create New...