From mboxrd@z Thu Jan  1 00:00:00 1970
From: Asdo <asdo@shiftmail.org>
Subject: Re: On mdadm 3.2 and bad-block-log
Date: Mon, 16 Jul 2012 09:41:48 +0200
Message-ID: <5003C5BC.3070609@shiftmail.org>
References: <4FD7738D.3040403@shiftmail.org>
 <CAGRgLy5Eryf_kT69a3SSPi8-MVpVmhEL96tNWJZQd9-vf4iYZQ@mail.gmail.com>
 <20120716134138.0f1c9cfc@notabene.brown>
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <linux-raid-owner@vger.kernel.org>
In-reply-to: <20120716134138.0f1c9cfc@notabene.brown>
Sender: linux-raid-owner@vger.kernel.org
To: NeilBrown <neilb@suse.de>
Cc: Alexander Lyakas <alex.bolshoy@gmail.com>, linux-raid <linux-raid@vger.kernel.org>
List-Id: linux-raid.ids

On 07/16/12 05:41, NeilBrown wrote:
> and as the bad block code is
> clearly still buggy, I probably don't want to rush it out :-)

The bad block code is buggy... the one in the kernel or the one in 
mdadm-3.3 ?
'cause I am currently using an array created with bad block log on 
kernel 3.4.3...

Thanks