Re: [PATCH 1/1] imsm: fix spare activation for old matrix arrays

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4/10/19 6:14 AM, Pawel Baldysiak wrote:
> On 3/8/19 12:19, Pawel Baldysiak wrote:
>> During spare activation get_extents() calculates metadata reserved
>> space based
>> on smallest active RAID member or it will take the defaults. Since patch
>> 611d9529("imsm: change reserved space to 4MB") default is extended. 
>> If array
>> was created prior that patch, reserved space is smaller. In case of
>> matrix
>> RAID - spare is activated in each array one-by-one, so it is spare for
>> first
>> activation, but treated as "active" during second one.
>>
>> In case of adding spare drive to old matrix RAID with the size the
>> same as
>> already existing member drive the routine will take the defaults
>> during second
>> run and mdmon will refuse to rebuild second volume, claiming that the
>> drive
>> does not have enough free space.
>>
>> Add parameter to get_extents(), so the during spare activation
>> reserved space
>> is always based on smallest active drive - even if given drive is already
>> active in some other array of matrix RAID.
>>
>> Signed-off-by: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>

Applied thanks!

Sorry for the delay, I'll push it to git once I land.

Cheers,
Jes




[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux