[[6.7.0-rc2] Reading all disks when writing to a single one]

I'm the OP and in my case I only write to individual disks. User shares are defined but I don't use them.

 

The server has no Dockers, no VMs. The only two plugins are User scripts and Fix common problems.

 

During a copy to disk21 all disks were spun up and showed read requests during the whole copy activity (around 10 minutes). As soon as copy to disk21 ended all read activity to the other disks stopped as well.

 

One of the spun up and read disks is disk17. This disk is for backup purposes only. It's not used from anything but backup jobs beginning at 04:00 every night and running for approx. an hour. This disk was spun up and read for 10 minutes as well during that copy operation.

 

This reminds me of one of the previous releases. I came late into the RCs, did mention something like "all disks spin up", had to read lots of "not happening here" and with the final release a patch to SMB was introduced that fixed that behaviour.

 

I'm not at home currently, will look for this old thread tomorrow.

 

 

 

 

 

[Syslinux Configuration uses wrong GUI element]

What you describe is a radiobutton, no checkbox. Definetely.

 

Here are two example sites where you can play with both controls. You want a radiobutton, definetely:

 

https://www.w3.org/WAI/UA/TS/html401/cp0101/0101-RADIO.html

https://www.ericmmartin.com/code/jquery/checkbox.html

 

TL;DR

 

A checkbox is the wrong control for a selection like that. It's simply confusing if you are used to traditional User Interfaces. Changing a checkbox should _never_ change another checkbox in the same set of checkbox controls. And in addition a checkbox does exist to switch them on or off.

 

Out of a set of radiobuttons one and only one can be switched on. If you switch a radiobutton to on, the other button that was switched on before, goes off.

 

Out of a set of checkboxes all, none or individual checkboxes can be switched on or off. To accomplish that every single checkbox reacts on it's individual handling.

 

On that Unraid page you can't switch a checkbox off (wrong handling of a checkbox) and to make it worse switching a checkbox to on does switch another checkbox off.

 

Out of thousands pages of existing documentation let me show you these:

https://developer.android.com/guide/topics/ui/controls/checkbox

https://developer.android.com/guide/topics/ui/controls/radiobutton

 

The important text is this:

- Radio buttons allow the user to select one option from a set.

 

- Checkboxes allow the user to select one or more options from a set. [...] Because a set of checkbox options allows the user to select multiple items, each checkbox is managed separately [...]

 

Handling of stuff like that goes back to Common User Access (IBM, Microsoft) from the 70s/80s in the last century. Standard controls like Radiobuttons and Checkboxes did not change their meaning in these ~40 years.

 

[[6.7.0-rc2] Reading all disks when writing to a single one]

No, I don't use something like Turbo Write. In fact I don't even know what it is.

 

Are these Tunable Values?

 

I changed md_num_stripes 4096, md_sync_window 2048 and md_sync_thresh 2000. All others are default.

 

***Edit*** These three Tunable Values mentioned above have been changed a year ago. I didn't change anything between 6.6.6 and 6.7.0-rc2.

 

 

 

 

[[6.7.0-rc2] Reading all disks when writing to a single one]

Did some tests in Safe Mode and without Safe Mode.

 

1.) What I see is, that writes are delayed. What I don't know is if this is the GUI lagging or a real diskwrite lag. E.g.: Copy a file between two individual disks with all disks spun-down. MC reports a successful copy. After that (!!!) the GUI shows that both parity disks and that individual disk are spinning up. This does not happen with 6.6.6.

 

2.) Copying like mentioned in my first post did not spin up all disks (neither Safe Mode nor without Safe Mode).

 

3.) But while writing this post I can see in a second window that all disks begin to spin up. This is true for Safe Mode and without Safe Mode. Something is waking up the disks. This does not happen with 6.6.6.

 

There's one special disk in the array. Here I write backups nightly. This disk is ony used in the night, it's not used for anything else. Even this disk did spin up with all the other disks.

 

[[6.7.0-rc2] Reading all disks when writing to a single one]

Thanks, will check. That server has no Dockers, no VMs. Only two plugins (User scripts, Fix common problems). Bet it will show up in Safe Mode as well.

 

[System Information does not detect CPU]

Ok, will be "soon" I suppose

 

[Scheduled Parity Check did not run]

Yes, I'm on 6.6.6.

 

My first thought was "calendar week" vs. "week of year" but both is at #1.

 

Will try again with Friday in first week 23:00 tonight. Will see what happens.