From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Mike Lovell <mike.lovell@endurance.com>
Cc: linux-raid@vger.kernel.org, NeilBrown <neilb@suse.de>
Subject: Re: problems with lots of arrays
Date: Tue, 10 May 2016 16:48:01 -0400 [thread overview]
Message-ID: <wrfj8tzhk5by.fsf@redhat.com> (raw)
In-Reply-To: <CAK9wOaB+Cic3nR5kzB3n=nVpbRtfo8+Qr9j_VNM3hh5tJRw6YA@mail.gmail.com> (Mike Lovell's message of "Thu, 5 May 2016 17:24:29 -0600")
Mike Lovell <mike.lovell@endurance.com> writes:
> we have a number of systems that have a large number of software
> arrays running. its in the couple hundred range. we have been using a
> custom built kernel based on 3.4 but are wanting to update to a
> mainline kernel and have been experimenting with 4.4. the systems are
> running recent centos 6 releases but we have been downgrading the
> mdadm version from 3.3.2 in 6.7 to a custom build 3.2.6. we installed
> the downgraded version due to a problem with array numbering. i
> emailed the list a while ago explaining the issue and submitting a
> patch to fix [1]. i never heard anything back and since we had a
> simple fix i didn't follow up on it.
[snip]
> what do you all think?
>
> thanks
> mike
>
> [1] http://marc.info/?l=linux-raid&m=142387809409798&w=2
Staying consistent in using dev_t rather than casting back and forth to
int seems a reasonable fix to apply to mdadm. It obviously won't change
the issues with the newer kernels, but I don't see any reason why we
shouldn't apply that fix to mdadm.
Neil any thoughts on this?
Cheers,
Jes
next prev parent reply other threads:[~2016-05-10 20:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 23:24 problems with lots of arrays Mike Lovell
2016-05-06 6:43 ` NeilBrown
2016-05-06 17:02 ` Mike Lovell
2016-05-06 17:59 ` Mike Lovell
2016-05-06 23:13 ` NeilBrown
2016-05-10 20:48 ` Jes Sorensen [this message]
2016-05-10 22:39 ` NeilBrown
2016-05-11 0:45 ` Shaohua Li
2016-05-12 1:55 ` NeilBrown
2016-05-12 5:58 ` Hannes Reinecke
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=wrfj8tzhk5by.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=mike.lovell@endurance.com \
--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).