14 minutes ago, superloopy1 said:

Guys, do i set the number of drives to the max in my array prior to doing a parity check? Parity check takes an age on my system, just looking for ways to speed it up besides buying a whole new setup ;)>

Turbo write doesn't effect check speed.

19 minutes ago, JonathanM said:

Turbo write doesn't effect check speed.

No?

 

I've never understood this thread and i've read it back to back a number of times. So we are only talking write speeds that are affected by this, reads  are not handled similarly? Apolgies if i'm way off beam here .... educate me.

Yes, write speed when writing a file.  Reads are not affected at all and will happen at the native speed of the drive (subject to bandwidth considerations etc)

7 minutes ago, superloopy1 said:

I've never understood this thread and i've read it back to back a number of times. So we are only talking write speeds that are affected by this, reads  are not handled similarly? Apolgies if i'm way off beam here .... educate me.

Since unRAID stores a single file, regardless of size, on only one disk (no data striping across disks) read speed is limited by the speed of the disk on which the file is stored.  There is no way to speed this up.

Thanks guys, understood now. I'm stuck with an extremely slow parity check it appears, heyho ...

2 minutes ago, superloopy1 said:

Thanks guys, understood now. I'm stuck with an extremely slow parity check it appears, heyho ...

Start a new thread in the general support forum and include the diagnostics saved during a check.

59 minutes ago, superloopy1 said:

extremely slow parity check

How slow? 2-3 hours per TB of largest drive is typical

19 hours ago, superloopy1 said:

Guys, do i set the number of drives to the max in my array prior to doing a parity check? Parity check takes an age on my system, just looking for ways to speed it up besides buying a whole new setup ;)>

There is no way to speed up the parity check simply by changing some settings as its speed is determined by the hardware capabilities of your system.  Normally the limiting factor is the speed of the slowest drive in the array, although it is also possible for the way the drives are connected to have a limiting effect.

 

You also want to ensure that no other disk accesses are being made to the array at the same time as in such a case both of them have their performance adversely affected.

 

If you have large drives then it may be worthwhile installing the Parity Check Tuning plugin to at least restrict the check to running outside prime time.

Guys, I don't understand something here, it says all drives will  spin up, is that assuming people have default share settings across all drives?

What if i isolate shares per drive until they filled up [so other hdds are in permanent OFF mode]

Will turbo write spin them up too, even if they empty and have no shares on them?

 

Thanks

Yes because parity doesn't know or care about shares or files, only about disk blocks.

In order to calculate parity for a given disk block when writing to one drive either you read existing parity and adjust it against the write, or you read the corresponding block from all disks and recalculate parity "from scratch".

The former is slow due to disk seeking time, which is why the other (turbo/reconstruct write) is an option.

Edited December 17, 20223 yr by Kilrah

If auto selects read/modify/write all the time, what is the point of having an auto option that does nothing?

1 minute ago, cprn said:

what is the point of having an auto option that does nothing?

Placeholder for future implementation.

I've been considering turning this on for a while.

 

Just asking, is there a timeline or idea for when the auto option will be implemented?

Also, does switching between parity write methods require rebooting, or can I test this by just adjusting the setting?

1 hour ago, KptnKMan said:

Also, does switching between parity write methods require rebooting, or can I test this by just adjusting the setting?

It's dynamic, and there's actually a "CA Auto Turbo Write Mode" plugin to change it based on some conditions. Probably why Auto isn't implemented, the plugin's more flexible.

It would be especially awesome if I could somehow choose it on clients side. For example by having 2 different shares pointing to the same location. /Fast and /Slow, so if I have the time to copy stuff overnight but not spin up other drives, i choose the slow option and if I need the data on the array fast, i could choose the fast option...

Quick question. I have a disk clear going on with a newly added disk. I have a disk-to-disk copy going on. What happens if during all this I flip this switch to "reconstruct write"?

Edited November 3, 20241 yr by steelsoap

28 minutes ago, steelsoap said:

What happens if during all this I flip this switch to "reconstruct write"?

If you have a disk to disk copy going on, turbo write won't work, only when that finishes.

I wonder how it knows when such operation finishes. I thought it working "dynamically" means that it (de)activates between lower level operations like individual file copies.

Well, I enabled reconstructive write and now my other disk in the array has read operations going on on it, spiking up to 4MB/s. Speed of copy remains unaffected.

24 minutes ago, steelsoap said:

I wonder how it knows when such operation finishes.

It will work when there's i/o to one array disk only

Btw the source disk is not part of the array so only one disk would have IO on it, BUT I have that other disk clear going on as well so that makes 2.

32 minutes ago, steelsoap said:

BUT I have that other disk clear going on as well so that makes 2.

Not sure if that will count, it's something I've never tested.

Is the future here yet or do I have to set it to reconstruct write in unraid 7.0?

If you want turbo write enabled, you do.