ok, i understood the commitmessage as if the behavior for tests is
more of a bonus
2018-01-30 7:30 GMT+01:00 Anand Jain :
> This __also__ helps testing
then it's clear to me. would only be good that this behavior is
documented. not that anyone else, like me, tries to use
On 2018-01-31 09:52, Peter Becker wrote:
This is all clear. My question referes to "use the lower devid disk
containing the stripe"
2018-01-31 10:01 GMT+01:00 Anand Jain :
When a stripe is not present on the read optimized disk it will just
use the lower devid disk
This is all clear. My question referes to "use the lower devid disk
containing the stripe"
2018-01-31 10:01 GMT+01:00 Anand Jain :
> When a stripe is not present on the read optimized disk it will just
> use the lower devid disk containing the stripe (instead of failing
On 01/31/2018 06:47 PM, Peter Becker wrote:
2018-01-31 10:01 GMT+01:00 Anand Jain :
When a stripe is not present on the read optimized disk it will just
use the lower devid disk containing the stripe (instead of failing back
to the pid based random disk).
Is
On 01/31/2018 03:51 PM, Peter Becker wrote:
A little question about mount -o read_mirror_policy=.
How would this work with RAID1 over 3 or 4 HDD's?
In particular, if the desired block is not available on device .
When a stripe is not present on the read optimized disk it will just
use the
A little question about mount -o read_mirror_policy=.
How would this work with RAID1 over 3 or 4 HDD's?
In particular, if the desired block is not available on device .
Could i repeat this option like the device-option to specify a
order/priority like this:
mount -o read_mirror_policy=
In case of RAID1 and RAID10 devices are mirror-ed, a read IO can
pick any device for reading. This choice of picking a device for
reading should be configurable. In short not one policy would
satisfy all types of workload and configs.
So before we add more policies, this patch-set makes existing