From mboxrd@z Thu Jan 1 00:00:00 1970 From: "David F." Subject: Re: MDADM 3.3 broken? Date: Fri, 6 Dec 2013 19:46:47 -0800 Message-ID: References: <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> <529674CB.5040808@arcor.de> <20131207141648.069eb003@notabene.brown> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: In-Reply-To: <20131207141648.069eb003@notabene.brown> Sender: linux-raid-owner@vger.kernel.org To: NeilBrown Cc: Martin Wilck , "linux-raid@vger.kernel.org" List-Id: linux-raid.ids Okay, I wasn't sure it was allowed / would go through. We used tar's sparse file support or they would be very large. I'll have the link say up in case Martin wants a copy... Thanks! On Fri, Dec 6, 2013 at 7:16 PM, NeilBrown wrote: > On Fri, 6 Dec 2013 18:28:16 -0800 "David F." wrote: > >> Just wondering if the link to the files to debug the problem made it ??? >> >> On Thu, Dec 5, 2013 at 5:53 PM, David F. wrote: >> > Hi, >> > >> > Got the files from the customer - you can download the zipped tar from >> > >> > Let me know when you get it so we can delete it. >> > >> > Thanks. >> > >> > >> > On Wed, Nov 27, 2013 at 2:40 PM, Martin Wilck wrote: >> >> On 11/26/2013 10:59 PM, David F. wrote: >> >>> does it need to be a tar type file or would virtual hard drive .vmdk >> >>> files be okay? >> >> >> >> I guess it would be ok (never tried). >> >> >> >> Martin > > I grabbed a copy, though at 1967 bytes you could have attached it to the > email safely :-) > > I haven't had a chance to look at them in detail yet. > > NeilBrown