From mboxrd@z Thu Jan 1 00:00:00 1970 From: "David F." Subject: Re: MDADM 3.3 broken? Date: Tue, 26 Nov 2013 13:59:34 -0800 Message-ID: References: <528A7721.8080604@arcor.de> <20131119110110.396b2af3@notabene.brown> <528BBFEB.7050202@arcor.de> <20131120105115.27494ab6@notabene.brown> <20131120114833.695fc9d4@notabene.brown> <20131120133016.7de2d400@notabene.brown> <528E710F.1050901@arcor.de> <5293C789.3020703@arcor.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: In-Reply-To: <5293C789.3020703@arcor.de> Sender: linux-raid-owner@vger.kernel.org To: Martin Wilck Cc: NeilBrown , "linux-raid@vger.kernel.org" List-Id: linux-raid.ids does it need to be a tar type file or would virtual hard drive .vmdk files be okay? On Mon, Nov 25, 2013 at 1:56 PM, Martin Wilck wrote: > The metadata really looks all ok, but mdadm fails to assemble it > correctly. It does look like a bug to me. The problem seems to be > related to the global spare somehow. I have no idea why. > > The best thing to proceed would be to run mdadm --dump on > /dev/sd[bcdef], put the output in a tgz and make it available to us > somewhere. So we could actually debut the assembly. > > Regards, > Martin > > >