On 02/12/2018 05:43 AM, Mateusz Korniak wrote: > On Sunday 11 of February 2018 12:13:45 Phil Turmel wrote: >> On 02/10/2018 04:43 PM, Mateusz Korniak wrote: >> >>> data is saved under different location when such write fails for >>> later reads? >> >> No. (...) > > So having arrays having non-empty BBL members means that array is in fact > degraded (for tiny part, but still), right? Yes, it's degraded wherever there's a BBL entry. To my knowledge, *no* upper layer, whether device mapper or any filesystem, uses the information to avoid allocations in the degraded area or to rescue the data precariously living there. Last I looked, mdadm --detail did not report whether the array has degraded regions. You must inspect the output of mdadm --examine for every member. > Is there any option for mdadm --monitor to send warning e-mail when bbl entry > is added? (I can't see anything regarding bbl in mdadm --monitor section) ? No. The feature is incomplete. The only mitigation is to turn it off. Phil -- 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
