Re: On mdadm 3.2 and bad-block-log

[NeilBrown <neilb@suse.de>]

[-- Attachment #1: Type: text/plain, Size: 2299 bytes --]

On Wed, 11 Jul 2012 12:40:57 +0300 Alexander Lyakas <alex.bolshoy@gmail.com>
wrote:

> Hi Neil,
> can you pls clarify whether the bad block management code in existing
> kernels is still considered experimental, and that's the reason there
> is no mdadm 3.3.x release yet?

Given that you are finding bugs in it - yes, it is still experimental :-)

The reason there is no 3.3.x release yet is that the amount of stuff that I
want to include in 3.3 has grown substantially and as the bad block code is
clearly still buggy, I probably don't want to rush it out :-)
I'm hoping for August or September for 3.3.  Probably September.

> If yes, which kernel do you recommend to experiment with this feature?

Always the latest.

> If no, should we then use the "devel-3.3" branch of mdadm, which was
> last updated ~1 year ago?

Yes. I'll be pulling that code into 'master' once I've finished some
code-cleanup that I want to do first.

Thanks,
NeilBrown



> 
> Thanks,
> Alex.
> 
> 
> 
> On Tue, Jun 12, 2012 at 7:51 PM, Asdo <asdo@shiftmail.org> wrote:
> > Hello
> > is it possible to keep mdadm 3.2 installed in the system (e.g. 3.2 as the
> > monitoring daemon) and have an array with bad-block functionality (created
> > with 3.3) running, or this will do a mess?
> >
> > Bad-block functionality is in mdadm-3.3 but this has not been released yet.
> > I was thinking about using it only once to create the array.
> >
> > However I am still missing the manual for mdadm-3.3, where is that? without
> > that I don't know how I should launch it to create an array with bad blocks.
> >
> > Another question: are older kernels such as 3.0 capable to run an array
> > created with bad-block-log, obviously without using the bad-block-log
> > functionality? oh but that could be dangerous, couldn't it...
> >
> > Thank you
> > A.
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]