From: Bill Davidsen <davidsen@tmr.com>
To: Ian Docherty <idiandocherty@googlemail.com>
Cc: 'Robin Hill' <robin@robinhill.me.uk>, linux-raid@vger.kernel.org
Subject: Re: md software raid
Date: Tue, 27 Oct 2009 16:52:23 -0400 [thread overview]
Message-ID: <4AE75D87.60708@tmr.com> (raw)
In-Reply-To: <000601ca56ee$f7a4d360$e6ee7a20$@com>
Ian Docherty wrote:
>
>> -----Original Message-----
>> From: linux-raid-owner@vger.kernel.org [mailto:linux-raid-
>> owner@vger.kernel.org] On Behalf Of Robin Hill
>> Sent: 23 October 2009 10:38
>> To: linux-raid@vger.kernel.org
>> Subject: Re: md software raid
>>
>> On Fri Oct 23, 2009 at 02:11:09AM -0700, ian.d wrote:
>>
>>
>>> hello
>>>
>>> As a newbie to Linux kernel etc.
>>>
>>> How do you tell which version of md software raid is included in a
>>> specific kernel version?
>>> Is there a command to run which will return this info?
>>> Is it possible to install different versions of md in different
>>>
>> kernels?
>>
>> There's two separate components to Linux software RAID - the md code in
>> the kernel, and the mdadm application which interfaces with it. I very
>> much doubt the kernel code is versioned at all, other than by the
>> kernel version (or GIT version). The mdadm application is versioned,
>> and you can get the installed version by running 'mdadm -V'.
>>
>> Some of the mdadm functionality will only work with newer kernel
>> versions, but you should be able to run any version with any kernel
>> (within reason anyway) and make use of the core functionality. There
>> may be some exceptions here, but they should be detailed in the release
>> notes for specific versions.
>>
>> As for changing the md version in the kernel - it may be possible, but
>> generally there's a lot of work involved in back/forward porting code
>> between kernel versions (because of changes to core structures, etc).
>>
>> Is there any particular reason you're asking this (e.g. needing to use
>> some of the latest functionality with an older kernel)? You may get a
>> more definitive answer if you have a specific case.
>>
>
> Thanks this info was very helpful.
>
> The reason I asked was because I have been following a thread re MD-XFS 50%
> write performance issue with different kernel releases and as performance is
> important to me I was thinking it might be better for me to use an older
> kernel (2.6.28.4) but keeping md,mdadm functionality up to date
>
That's certainly a valid point, if you are stuck using xfs by preference
or requirement. I have seen claims that 2.6.32 will be better, but I
have no intention of testing it, having parted company with xfs a while ago.
--
Bill Davidsen <davidsen@tmr.com>
Unintended results are the well-earned reward for incompetence.
next prev parent reply other threads:[~2009-10-27 20:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 9:11 md software raid ian.d
2009-10-23 9:38 ` Robin Hill
2009-10-27 10:19 ` Ian Docherty
2009-10-27 20:52 ` Bill Davidsen [this message]
2009-10-27 20:55 ` Richard Scobie
2009-10-27 21:15 ` Christopher Chen
2009-10-28 0:45 ` Leslie Rhorer
2009-10-28 0:47 ` Majed B.
2009-10-28 0:52 ` Leslie Rhorer
2009-10-28 0:58 ` Majed B.
2009-10-28 0:50 ` Richard Scobie
2009-10-27 22:00 ` Ric Wheeler
2009-10-28 15:08 ` Eric Sandeen
2009-10-28 16:06 ` Bernd Schubert
2009-10-28 23:39 ` Dave Chinner
2009-10-28 1:09 ` Max Waterman
2009-10-28 1:10 ` Majed B.
2009-10-28 2:03 ` Richard Scobie
2009-10-28 2:11 ` Leslie Rhorer
2009-10-28 2:26 ` Majed B.
2009-10-28 2:54 ` Leslie Rhorer
[not found] ` <4D87015385157D4285D56CA6101072FF3A6675B8@exchange07.valvesoftware.com>
2009-10-28 2:52 ` Majed B.
2009-10-28 3:26 ` Guy Watkins
2009-10-28 3:08 ` Leslie Rhorer
2009-10-28 3:11 ` Chris Green
2009-10-28 3:29 ` Leslie Rhorer
2009-11-05 13:51 ` Matt Garman
2009-10-28 3:35 ` Guy Watkins
2009-10-28 11:27 ` Max Waterman
2009-10-28 3:50 ` Christoph Hellwig
2009-10-28 6:37 ` Leslie Rhorer
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=4AE75D87.60708@tmr.com \
--to=davidsen@tmr.com \
--cc=idiandocherty@googlemail.com \
--cc=linux-raid@vger.kernel.org \
--cc=robin@robinhill.me.uk \
/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).