From: Igor M Podlesny <for.poige+lsr@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: "mdadm: Raid level 5 not permitted with --build" -- why is that?
Date: Mon, 25 Jun 2012 19:33:23 +0800 [thread overview]
Message-ID: <CA+sTkh7cYEmrujcRkvisFM1EksQBJ2kMKBfkd3RyDwr2-bvGpw@mail.gmail.com> (raw)
In-Reply-To: <20120625165242.117881e1@notabene.brown>
On 25 June 2012 14:52, NeilBrown <neilb@suse.de> wrote:
> On Fri, 22 Jun 2012 11:07:33 +0800 Igor M Podlesny <for.poige+lsr@gmail.com>
> wrote:
>
>> subj. Hi :)
>
> Please try to construct coherent email message. If you want people to read
> what you write, make it easy for them.
And what is so uneasy in such a little quoting sentence?, I shall ask.
Those, who know where does the quote come from, are the target
group, those, who doesn't — aren't.
What's the problem?
> Because!
>
> With nowhere to record device failure, you don't have any safety.
Well, suppose you don't need one — due to short-term period of such
an array existence which in its turn was predicated by real array
failure, say, damaging superblocks (if it reminds you something).
mdadm -C would create one, but you may not know which '-e' to specify.
That's the reasoning beneath to have -B which wouldn't overwrite any
data on disks at all so ideally fitting as a probe tool.
> Feel free to send a patch.
— "Feel free" to spend time digging into an area which isn't what
you get paid for? At least what exactly should be patched this time,
will you kindly tell us?
>
> NeilBrown
--
--
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
next prev parent reply other threads:[~2012-06-25 11:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 3:07 "mdadm: Raid level 5 not permitted with --build" -- why is that? Igor M Podlesny
2012-06-25 6:52 ` NeilBrown
2012-06-25 11:33 ` Igor M Podlesny [this message]
2012-06-25 11:58 ` Roman Mamedov
2012-06-25 12:12 ` Igor M Podlesny
2012-06-25 12:40 ` David Brown
2012-06-25 13:10 ` Igor M Podlesny
2012-06-25 13:14 ` Rudy Zijlstra
2012-06-25 13:17 ` Igor M Podlesny
2012-06-25 17:59 ` John Crisp
2012-06-26 1:57 ` Igor M Podlesny
2012-06-26 11:55 ` John Crisp
2012-06-26 1:13 ` NeilBrown
2012-06-26 2:22 ` Igor M Podlesny
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=CA+sTkh7cYEmrujcRkvisFM1EksQBJ2kMKBfkd3RyDwr2-bvGpw@mail.gmail.com \
--to=for.poige+lsr@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).