From: NeilBrown <neilb@suse.de>
To: bobzer <bobzer@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid 5 and bad block feature
Date: Wed, 15 Feb 2012 07:12:17 +1100 [thread overview]
Message-ID: <20120215071217.32963463@notabene.brown> (raw)
In-Reply-To: <CADzS=aoMH5jL_6opVRAMY=+-N+3JE9kt-BNY4rC6aon4jyfPVQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
On Tue, 14 Feb 2012 14:18:28 -0500 bobzer <bobzer@gmail.com> wrote:
> hi
>
> I wanna setup a debian server with raid 5 and so I would know some news
> about
> the new version of mdadm (devel-3.3) to use the bad block feature :-).
> there is a release planned ?
No. I don't plan releases until about a week before they happen.
Unfortunately I haven't had much time to work on mdadm lately. Maybe next
month.
> if i start to use it now, could I upgrade it when the release will arrive ?
Yes, definitely.
> Is it enough safe to use it ?
Hard to say. I have done some testing so I believe it basically works, but
there are almost certainly some bugs still in there. Until it gets widely
used it will be hard to know for sure.
I think it quite unlikely that the bugs would result in loss of data, though
they may result in a hang or a crash or something like that
I can only suggest you try it and see - but have backups of important data.
If you run into any problem I will certainly do whatever I can to sort them
out.
NeilBrown
>
> thank you for your time
>
> Mathieu
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-02-14 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADzS=aoMH5jL_6opVRAMY=+-N+3JE9kt-BNY4rC6aon4jyfPVQ@mail.gmail.com>
2012-02-14 19:20 ` raid 5 and bad block feature bobzer
2012-02-14 20:12 ` NeilBrown [this message]
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=20120215071217.32963463@notabene.brown \
--to=neilb@suse.de \
--cc=bobzer@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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).