From mboxrd@z Thu Jan 1 00:00:00 1970 From: Curt Subject: Re: hung grow Date: Wed, 11 Oct 2017 11:38:34 -0400 Message-ID: References: <89992d1f-172f-9fc6-3a1e-50df34e11d3b@turmel.org> <87po9xyv0r.fsf@notabene.neil.brown.name> <87d15xymgc.fsf@notabene.neil.brown.name> <0d4987d9-e8ff-0cdb-6e45-7f962b75c189@turmel.org> <3e5766b0-1437-2857-4806-264386d1633f@youngman.org.uk> <6d4b7055-c26c-951e-b63c-273a7fe447b8@turmel.org> <874lr6ybll.fsf@notabene.neil.brown.name> <87k202wapp.fsf@notabene.neil.brown.name> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <87k202wapp.fsf@notabene.neil.brown.name> Sender: linux-raid-owner@vger.kernel.org To: NeilBrown Cc: Phil Turmel , Anthony Youngman , linux-raid@vger.kernel.org List-Id: linux-raid.ids On Wed, Oct 11, 2017 at 12:49 AM, NeilBrown wrote: > > Nope. It is a kernel bug that is still present. I can easily reproduce > it on the mainline kernel now that I have your metadata. > I know generally what the problem is. I'll try to craft a fix tomorrow. > You'll need to build and run a new kernel to be able to fix you array. > That might seem scary, but it really isn't that hard. > > NeilBrown Awesome thanks. Just let me know what I need to do. Cheers, Curt