Re: [PATCH 00/13 v3] Introduce device state 'failed', Hot spare and Auto replace

Kai Krakow posted on Mon, 04 Apr 2016 22:15:13 +0200 as excerpted: > Your argument would be less important if it did copy-back, tho... ;-) FWIW, I completely misunderstood your description of copy-back in my original reply, and didn't realize what you meant (and thus my mistaken understanding)

Re: [PATCH 00/13 v3] Introduce device state 'failed', Hot spare and Auto replace

Am Mon, 4 Apr 2016 04:45:16 + (UTC) schrieb Duncan <1i5t5.dun...@cox.net>: > Kai Krakow posted on Mon, 04 Apr 2016 02:00:43 +0200 as excerpted: > > > Does this also implement "copy-back" - thus, it returns the > > hot-spare device to global hot-spares when the failed device has > > been

Re: [PATCH 00/13 v3] Introduce device state 'failed', Hot spare and Auto replace

Am Mon, 4 Apr 2016 14:19:23 +0800 schrieb Anand Jain : > > Otherwise, I find "hot spare" misleading and it should be renamed. > > I never thought hot spare would be narrowed to such a specifics. [...] > About the naming.. the progs called it 'global spare' (device),

Re: [PATCH 00/13 v3] Introduce device state 'failed', Hot spare and Auto replace

On 04/04/2016 08:00 AM, Kai Krakow wrote: Am Sat, 2 Apr 2016 09:30:38 +0800 schrieb Anand Jain : Auto replace: Replace happens automatically, that is when there is any write failed or flush failed, the device will be marked as failed, which will stop any further

Re: [PATCH 00/13 v3] Introduce device state 'failed', Hot spare and Auto replace

Duncan posted on Mon, 04 Apr 2016 04:45:16 + as excerpted: > Kai Krakow posted on Mon, 04 Apr 2016 02:00:43 +0200 as excerpted: > >> Does this also implement "copy-back" - thus, it returns the hot-spare >> device to global hot-spares when the failed device has been replaced? > > I don't

Re: [PATCH 00/13 v3] Introduce device state 'failed', Hot spare and Auto replace

Kai Krakow posted on Mon, 04 Apr 2016 02:00:43 +0200 as excerpted: > Does this also implement "copy-back" - thus, it returns the hot-spare > device to global hot-spares when the failed device has been replaced? I don't believe it does that in this initial implementation, anyway. There's a

Re: [PATCH 00/13 v3] Introduce device state 'failed', Hot spare and Auto replace

Am Sat, 2 Apr 2016 09:30:38 +0800 schrieb Anand Jain : > Auto replace: > Replace happens automatically, that is when there is any write > failed or flush failed, the device will be marked as failed, which > will stop any further IO attempt to that device. And in the

[PATCH 00/13 v3] Introduce device state 'failed', Hot spare and Auto replace

Thanks for various comments, tests and feedback. Background: Hot spare and Auto replace: Hot spare is predominately used to mitigate or narrow the time window of a degraded mode, during which any further disk failure might lead to a catastrophic data loss. Data center storage generally will