From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc MERLIN Subject: Re: force remapping a pending sector in sw raid5 array Date: Mon, 12 Feb 2018 08:49:33 -0800 Message-ID: <20180212164933.GA15015@merlins.org> References: <20180206181416.amo6geclrvc6ylrf@merlins.org> <1934212.TzpEgCIeIR@matkor-lenovo> <3275011.qXpCPUrKDu@matkor-lenovo> <0780e95c-ae84-4b2b-0222-f59df368a2ee@turmel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <0780e95c-ae84-4b2b-0222-f59df368a2ee@turmel.org> Sender: linux-raid-owner@vger.kernel.org To: Phil Turmel Cc: Mateusz Korniak , Kay Diederichs , Andreas Klauer , Adam Goryachev , Roger Heflin , linux-raid@vger.kernel.org List-Id: linux-raid.ids On Mon, Feb 12, 2018 at 10:29:20AM -0500, Phil Turmel wrote: > > 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. I had a quick look but didn't really find how to turn it off after the fact (not at array creation time, but after it's already been created). Can you suggest how? Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/