From mboxrd@z Thu Jan 1 00:00:00 1970 From: Curt Subject: Re: hung grow Date: Tue, 10 Oct 2017 16:58:24 -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> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <874lr6ybll.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 Tue, Oct 10, 2017 at 4:47 PM, NeilBrown wrote: > > Clearly a kernel bug. > What kernel are you using? Can you try a newer one easily? 3.10.0-229.el7.x86_64. I could either update the OS or transfer to a new server and use a rescue cd as mentioned before. > > Can you please > mkdir /tmp/dump > mdadm --dump=/dev/dump /dev...list.all.devices.in.the.array > tar czf --sparse /tmp/dump.tgz /tmp/dump > Yeah, I will get that for you once I reboot the server. > and send me /tmp/dump.tgz. It will only contains the metadata. > I can then create an identical looking array and experiment. > > I doubt if letting it run will bring benefits. > > NeilBrown