[Plugin] CA Auto Turbo Write Mode

[Squid]

No.  They will only spin up when a write to any of them happen

[jebusfreek666]

14 minutes ago, Squid said:

No.  They will only spin up when a write to any of them happen

 

I figured, but wanted to make sure

Also, I know it is not built into this plugin, but I was wondering if it is possible to have turbo write invoked anytime writes go to certain shares or come in from a certain user (for a windows PC). I have a few shares that are set to not use the cache as the files are sensitive and I would prefer they get written to the encrypted array ASAP.

[Mr.meowgi]

Do we need to enable reconstruct write on disk settings for it to work? Mine is set to auto

[jademonkee]

55 minutes ago, Mr.meowgi said:

Do we need to enable reconstruct write on disk settings for it to work? Mine is set to auto

Auto in disk settings is correct. The script will change it as needed.

Keep in mind that it won't change instantly, however: It'll take (up to) as long as the polling time to activate.

[eatoff]

Does this work with Unraid 6.10 RC2?

 

The current status drives spun down (as of last poll) sits at 3 all the time (i have 3 drives plus a parity in my array), even when all drives are spun up, and the polling time is set very short.

 

I can get it to activate turbo writes by setting the Disks Allowed To Be Spun Down Before Invoking Turbo Mode to 3, but I want to be able to set this to 2 or 1 so that turbo writes will only kick in if most of my drives are spun up anyway.

 

EDIT: had a reab back about smartctl and hdparm, and looks like my USB enclosure for my drive isnt passing this info through correctly

Edited February 25, 2022 by eatoff

[mihcox]

I just set a schedule for my drives last night, but I dont understand the error I am seeing. Can someone help me with this? My goal is to only have turbowrite on from 5pm to 2am, and have the drives able to spin down any other time.

 

[Digital Shamans]

Why there is a limit to max 1 spun down disk allowed?

Having i.e. 6 disks, I would like to be able to allow plugin to evoke Turbo mode even if 3 disks are spun down.
Why not? Is it this much slower to spun up 3 disks instead of 1 that it makes no sense? I doubt that, but hey. Hence the question.
 

[Squid]

The limit is based upon the number of data drives you have.  Since it's only giving you the option for 1, you probably only have 1 data drive and the rest are all pool devices.

[Bob_C]

A small 'bug' on a page element......

 

There is an image missing to delete a schedule.

 

"src="/plugins/dynamix.docker.manager/images/remove.png""

 

Was getting messages in Syslog.

[Squid]

fixed.  Thanks

[Quantumed]

On 9/16/2022 at 11:10 AM, Squid said:

fixed.  Thanks

Cool plugin, thank you for sharing it with us. I would love to see a feature that enables turbo write mode while the mover is running and disables it when the mover isn't running. As it stands, the amount of data that needs to be moved can vary from nothing, to hundreds of GB's, making the cron schedule tricky to work with

[loki_racer]

There's a small typo in the description of this plugin.  I couldn't find the github repo to submit a PR.

 

Quote

CA Auto Turbo Write Mode will automatically enable or disable turbo write mode depending upon the number of hard drives currently spinning. This could result is[sic] significantly faster write speeds to the array without needlessly spinning up disks.

 

"is" should be "in."