RE: [PATCH 01/11] imsm: FIX: Return longer map for failure setting

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

 




> -----Original Message-----
> From: dan.j.williams@xxxxxxxxx [mailto:dan.j.williams@xxxxxxxxx] On
> Behalf Of Dan Williams
> Sent: Wednesday, November 30, 2011 3:31 AM
> To: Kwolek, Adam
> Cc: neilb@xxxxxxx; linux-raid@xxxxxxxxxxxxxxx; Ciechanowski, Ed; Labun,
> Marcin
> Subject: Re: [PATCH 01/11] imsm: FIX: Return longer map for failure setting
> 
> On Thu, Nov 24, 2011 at 4:17 AM, Adam Kwolek <adam.kwolek@xxxxxxxxx>
> wrote:
> > When 2 maps are present, IMSM can use shorter map for setting disk in
> > to degraded state. It can happen that degraded disk can be not present
> > in shorter map.
> > We should use longer map for setting disk in to degraded state.
> 
> I don't understand this patch.  If we are setting a new degraded disk
> migration is idle and the degraded state is set in map[0].
> 
> --
> Dan

This is made for future in case when  support for shrinking will be added.
When second map is longer than first one and degradation occurs on position that is not present in first map. 
It situation should be stored in map also.

BR
Adam
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[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