linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: John Papa <John.Papa@Oracle.com>, linux-raid@vger.kernel.org
Subject: Re: latest version of mdadm for RedHat 5.3
Date: Fri, 12 Aug 2011 13:31:35 -0400	[thread overview]
Message-ID: <4E456377.6030506@redhat.com> (raw)
In-Reply-To: <20110812070759.2849ba0b@notabene.brown>

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

On 8/11/2011 5:07 PM, NeilBrown wrote:
> On Thu, 11 Aug 2011 09:00:22 -0700 John Papa <John.Papa@Oracle.com> wrote:
> 
>> On 8/11/2011 8:52 AM, John Papa wrote:
>>> Greetings,
>>>
>>> A customer is running RedHat 5.3 and has inquired regarding
>>> the latest version of mdadm for that version of RedHat.
>>>
>>> I am having some difficulty responding to the customer with
>>> the degree of confidence required for this production environment.
>>>
>>> Is mdadm version 3.2.2 compatible with RedHat version 5.3?
>>>
>>> Thank you in advance for considering this inquiry
> 
> In theory all later versions of mdadm are compatible with all kernels.  Later
> versions add features, remove bugs, and sometimes add bugs.
> 
> The real question is probably "Has it been tested" or "is someone willing to
> provide support".   Maybe you should ask Redhat??

It's a little bit more complex than that.  The mdadm package in rhel is
responsible for boot up bring up of md raid arrays, and between rhel5
and rhel6 we changed boot loaders, changed init scripts, changed over to
doing udev incremental assembly, and a host of other things.  I have
resisted the urge to put mdadm 3.x on rhel5 because it behaves
differently and the particular quirks of mdadm 2.6 might or might not be
relied upon by those boot scripts.  So, my latest build for rhel5 is
mdadm-2.6.9-3.  Now, whether or not even just that much of an update
would work with something as old as rhel5.3 with its (I'm sure) not
updated mkinitrd or initscripts is another question.

-- 
Doug Ledford <dledford@redhat.com>
              GPG KeyID: CFBFF194
	      http://people.redhat.com/dledford

Infiniband specific RPMs available at
	      http://people.redhat.com/dledford/Infiniband


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

      reply	other threads:[~2011-08-12 17:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4E43FAA8.5050509@Oracle.com>
2011-08-11 16:00 ` latest version of mdadm for RedHat 5.3 John Papa
2011-08-11 21:07   ` NeilBrown
2011-08-12 17:31     ` Doug Ledford [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=4E456377.6030506@redhat.com \
    --to=dledford@redhat.com \
    --cc=John.Papa@Oracle.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).