linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Braid <jamesb@loreland.org>
To: linux-raid@vger.kernel.org
Subject: Re: grow fails with 2.6.34 git
Date: Thu, 15 Apr 2010 00:27:51 +0100	[thread overview]
Message-ID: <hq5j1n$3os$1@dough.gmane.org> (raw)
In-Reply-To: <v2p4877c76c1004141548m6d3da932hd14543da1b730af9@mail.gmail.com>

Michael Evans wrote:
> Yes, that /extremely/ slow growth progress is normal for this
> conversion.  Every critical section must be backed up synced, and only
> then will it proceed.  You may notice an incorrect number of disks
> relative to the expected number.  That will go away the next time the
> array is assembled.

Thanks. I'm not concerned about the speed; the fact that I had to stop 
and restart the array before the reshape would begin is what concerns 
me, as well as the odd sysfs errors.


  reply	other threads:[~2010-04-14 23:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14 22:10 grow fails with 2.6.34 git James Braid
2010-04-14 22:48 ` Michael Evans
2010-04-14 23:27   ` James Braid [this message]
2010-04-14 23:38     ` Michael Evans
2010-04-15  1:04 ` Neil Brown
2010-04-15  2:22   ` Michael Evans
2010-04-15  2:55     ` Neil Brown
2010-04-15 15:09   ` James Braid

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='hq5j1n$3os$1@dough.gmane.org' \
    --to=jamesb@loreland.org \
    --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).