29.09.2014 06:56, NeilBrown wrote:
On Sun, 28 Sep 2014 17:52:52 +0200 Goswin von Brederlow goswin-...@web.de
wrote:
And then when force_array only checks up to the number of disks in the
array it misses half of them. In my case exactly those it should be
forcing.
This is fixed by
Control: severity -1 important
[]
Ow. I overlooked this. Thank you Neil for pointing it out.
I've 3.3.2 (with some more changes) ready to be releases in debian,
but I'm afraid it will be difficult due to udeb freeze. Let's see...
And since this bug has a good potential to make your system
Package: mdadm
Version: 3.3-2
Followup-For: Bug #763080
Hi,
attached a patch to make --force work with my reshaping array. The
problem seems to be that load_devices fills in the best array only for
every second slot (and makes it 4 times as big as needed):
mdadm: best[0] = 0
mdadm: best[1] = -1
On Sun, 28 Sep 2014 17:52:52 +0200 Goswin von Brederlow goswin-...@web.de
wrote:
And then when force_array only checks up to the number of disks in the
array it misses half of them. In my case exactly those it should be
forcing.
This is fixed by upstream patch
commit
4 matches
Mail list logo
