linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Igor M Podlesny <for.poige+lsr@gmail.com>
Cc: David Brown <david.brown@hesbynett.no>,
	Roman Mamedov <rm@romanrm.ru>,
	linux-raid@vger.kernel.org
Subject: Re: "mdadm: Raid level 5 not permitted with --build" -- why is that?
Date: Tue, 26 Jun 2012 11:13:42 +1000	[thread overview]
Message-ID: <20120626111342.4a61d1e5@notabene.brown> (raw)
In-Reply-To: <CA+sTkh53htrdUF5OUcKRa33HDmz9SHsz0=B9DvJ60uzeFST5XA@mail.gmail.com>

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

On Mon, 25 Jun 2012 21:10:17 +0800 Igor M Podlesny <for.poige+lsr@gmail.com>
wrote:

>    It's simple matter and as to me I prefer brevity. I see no purpose
> in inflating mail body just due to it was short. It's simple matter,
> that's why it's short, damn it.
> 
>    And finally — the fact of the reply *was* given proved that the
> question was easily understood. So what, then?

This is not actually correct.  I don't think that I did understand your
question, as you had provided no context.
Your question might have been:
 1/ I was reading the man page and discovered that RAID5 is not 
    permitted with --build and wondered why.
or
 2/ I was reading the code and saw that RAID5 is not permitted with 
    --build and wondered why
or
 3/ I was trying to do XX and thought that --build might be a solution
    but I need RAID5 and --build doesn't support RAID5 - why is that?

Each of these could have quite different answers so I couldn't be sure that
what I would say would actually be helpful unless I answered all of them,
which would probably be a waste of effort to some extent.  This is why I felt
that "Because!" was about all that the question really deserved.

I was feeling rather tired at the time which probably explains (without
justifying) the shortness of my answer.  I should have realised that and not
replied at all - my mistake.

BTW I wasn't intending sarcasm at all - sorry if you thought I was.

NeilBrown



> 
> > body.  Why should Neil or anyone else take the time to write a helpful reply
> > to someone who cannot even be bothered to write a good email?
> 
>    Ask him, not me. I wrote, he answered. 49 % off-topic, 1 % sarcasm,
> another 50 on topic — hell yeah, at least something!
> 
> > Neil told you why md raid does not (currently) implement "--build" for
> > raid5.  And he suggested that if you want that behaviour to change, you are
> > always welcome to send a patch.  If you don't want to write an
> > implementation of the missing behaviour, that's fair enough too - very few
> > people respond to "feel free to send a patch" by actually sending a patch.
> 
>    And I reminded that my daily job is not LSR hacking, so now what?
> 
> >  But if you want to get annoyed and sarcastic, please keep your comments to
> > yourself.
> 
>    The same applies to you — keep it to yourself, David, if you wish.
> I'm free to speak my mind free, am not I?
> 
> --


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

  parent reply	other threads:[~2012-06-26  1:13 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
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 [this message]
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=20120626111342.4a61d1e5@notabene.brown \
    --to=neilb@suse.de \
    --cc=david.brown@hesbynett.no \
    --cc=for.poige+lsr@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=rm@romanrm.ru \
    /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).