From: Asdo <asdo@shiftmail.org>
To: NeilBrown <neilb@suse.de>
Cc: Alexander Lyakas <alex.bolshoy@gmail.com>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: On mdadm 3.2 and bad-block-log
Date: Mon, 16 Jul 2012 09:41:48 +0200 [thread overview]
Message-ID: <5003C5BC.3070609@shiftmail.org> (raw)
In-Reply-To: <20120716134138.0f1c9cfc@notabene.brown>
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
next prev parent reply other threads:[~2012-07-16 7:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 16:51 On mdadm 3.2 and bad-block-log Asdo
2012-07-11 9:40 ` Alexander Lyakas
2012-07-16 3:41 ` NeilBrown
2012-07-16 7:41 ` Asdo [this message]
2012-07-16 7:55 ` Alexander Lyakas
2012-07-16 8:56 ` Asdo
2012-07-16 9:08 ` Alexander Lyakas
2012-07-17 1:49 ` NeilBrown
2012-07-17 8:21 ` Asdo
2012-07-17 23:34 ` NeilBrown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5003C5BC.3070609@shiftmail.org \
--to=asdo@shiftmail.org \
--cc=alex.bolshoy@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).