linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: "Jörg Habenicht" <j.habenicht@gmx.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Array died during grow; now resync stopped
Date: Thu, 5 Feb 2015 15:40:34 +1100	[thread overview]
Message-ID: <20150205154034.2d2b629f@notabene.brown> (raw)
In-Reply-To: <trinity-85824e10-6eeb-490e-91e9-29cac6bb884e-1423051086472@3capp-gmx-bs24>

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

On Wed, 4 Feb 2015 12:58:06 +0100 "Jörg Habenicht" <j.habenicht@gmx.de> wrote:

> It works! :-)) The array syncs!

Excellent!

> 
> 
> > > >What does
> > > >cat /proc/1671/stack
> > > >cat /proc/1672/stack
> > > >show?
> > > 
> > > $ cat /proc/1671/stack
> > > cat: /proc/1671/stack: No such file or directory
> > 
> > I guess you don't have that feature compiled into your kernel.
> 
> Guess so. I'm going to look to the missing CONFIG_ line.

CONFIG_STACKTRACE ... in case you haven't found it already.

> > 
> > And this is stuck in the same place.... what what is consuming all the
> > stripes I wonder....
> 
> Do you like me to collect more information?

No thanks, the required information was further down.  They were all consumed
by the reshape (which needs at least twice the largest chunk size).


> > If you double it, the problem should go away.
> > 
> > mdadm should  do that for you .... I wonder why it didn't.
> > 
> 
> Do you like to have more test results?

I had a look at the code and it was fairly obvious.  mdadm adjusts the stripe
cache based on the 'old' chunk size.  It never includes the 'new' chunk size
in those calculations.  I've made a note to fix that.

Thanks,
NeilBrown


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

      reply	other threads:[~2015-02-05  4:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02  9:41 Array died during grow; now resync stopped Jörg Habenicht
2015-02-02 19:40 ` NeilBrown
2015-02-03 10:35   ` Aw: " "Jörg Habenicht"
2015-02-04  6:45     ` NeilBrown
2015-02-04 11:58       ` Aw: " "Jörg Habenicht"
2015-02-05  4:40         ` NeilBrown [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=20150205154034.2d2b629f@notabene.brown \
    --to=neilb@suse.de \
    --cc=j.habenicht@gmx.de \
    --cc=linux-raid@vger.kernel.org \
    /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).