Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Ole Tange <tange@binf.ku.dk>
Cc: linux-raid@vger.kernel.org
Subject: Re: --grow RAID6 gives: md: md_do_sync() got signal ... exiting + hang
Date: Tue, 7 May 2013 22:40:51 +1000	[thread overview]
Message-ID: <20130507224051.1d96c130@notabene.brown> (raw)
In-Reply-To: <CANU9nTkPUq7V5tnndE64H64jpb7yr6NMZSmcFrqUf8PmRQMsMg@mail.gmail.com>

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

On Tue, 7 May 2013 14:08:14 +0200 Ole Tange <tange@binf.ku.dk> wrote:

> On Tue, May 7, 2013 at 1:54 PM, NeilBrown <neilb@suse.de> wrote:
> > On Tue, 7 May 2013 13:36:56 +0200 Ole Tange <tange@binf.ku.dk> wrote:
> >
> >> I am expanding my 9 harddisk RAID6 to 10 harddisk RAID6:
> :
> >> It is, however, hanging the system.
> :
> >> # Do the reshape
> >> mdadm -v --grow /dev/md1 --raid-devices=10
> >> --backup-file=/root/back-md1
> >> mdadm: Need to backup 7168K of critical section..
> 
> This completed - did not hang.
> 
> > What does
> >   grep . /sys/block/md1/md/*
> > show? Or does it hang?
> 
> Hangs (ctrl-c works).
> 
> > What about "mdadm --examine /dev/sd*"
> 
> https://gist.github.com/anonymous/5532063
> 
> The disk box contains more drives than just the array in question. The
> interesting array is: 242d6530:e2562ecb:1dcd2a97:15a1a868
> 
> > Did the "mdadm --grow" appear to complete, and return to the shell prompt?
> 
> Yes.
> 
> > What kernel version?  What mdadm version?
> 
> $ mdadm --version
> mdadm - v3.2.5 - 18th May 2012
> 
> $ uname -r
> 3.2.0-0.bpo.1-amd64
> 
> > A hanging /proc/mdstat is definitely not a good sign.  The "got signal ...
> > exiting" isn't good either.  I would expect more messages with that.
> > You didn't just "grep md" in dmesg did you?  That is a complete dmesg output
> > for the entire time period that could possibly be relevant?
> 
> dmesg of controller upgrade (after which everything worked fine)
> followed by --grow at 4328065.432267
> 
> https://gist.github.com/anonymous/5532093
> 
> /Ole

Thanks for the extra info.  I can't find any smoking gun unfortunately.

What does "ps axgu" show.  I'm particularly looking for processes in 'D'
state.
If there  are any, particularly if they are md related, try
  cat /proc/$PID/stack
for appropriate values of $PID

Maybe also try
   echo t > /proc/sysrq_trigger

and see what gets into 'dmesg' - hopefully your dmesg buffer is big enough to
hold the important stack traces.
If you get anything from either of those, please post.

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2013-05-07 12:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07 11:36 --grow RAID6 gives: md: md_do_sync() got signal ... exiting + hang Ole Tange
2013-05-07 11:54 ` NeilBrown
2013-05-07 12:08   ` Ole Tange
2013-05-07 12:40     ` NeilBrown [this message]
2013-05-07 11:56 ` Ole Tange
2013-05-07 12:14   ` NeilBrown
2013-05-07 12:16     ` Ole Tange

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=20130507224051.1d96c130@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=tange@binf.ku.dk \
    /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