From: NeilBrown <neilb@suse.de>
To: Sebastian Hegler <sebastian.hegler@tu-dresden.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm-3.2.5: segfault in "--grow --continue"
Date: Tue, 10 Jul 2012 23:02:05 +1000 [thread overview]
Message-ID: <20120710230205.171ee562@notabene.brown> (raw)
In-Reply-To: <D6EAEC68-9C5B-4CBF-943C-85ABF3E319BD@tu-dresden.de>
[-- Attachment #1: Type: text/plain, Size: 2385 bytes --]
On Tue, 10 Jul 2012 12:46:19 +0200 Sebastian Hegler
<sebastian.hegler@tu-dresden.de> wrote:
> Hi!
>
> I had to shut down a server with a raid grow operation (cleanly). After some hassles I got the array assembled again (manually), but it would not continue to grow. When trying
>
> mdadm --grow --continue /dev/md127
>
> (as per the manpage) I receive a segfault. Compiling from source, and using gdb, I see:
>
> root@kuiper:~/mdadm-3.2.5# gdb ./mdadm
> [SNIP]
> Reading symbols from /root/mdadm-3.2.5/mdadm...done.
> (gdb) set args --grow --continue /dev/md127
> (gdb) run
> Starting program: /root/mdadm-3.2.5/mdadm --grow --continue /dev/md127
>
> Program received signal SIGSEGV, Segmentation fault.
> Grow_continue_command (devname=0x7fffffffe8cc "/dev/md127", fd=7, backup_file=0x0, verbose=0) at Grow.c:4118
> 4118 if (verify_reshape_position(content,
> (gdb) bt
> #0 Grow_continue_command (devname=0x7fffffffe8cc "/dev/md127", fd=7, backup_file=0x0, verbose=0) at Grow.c:4118
> #1 0x0000000000407ac2 in main (argc=4, argv=0x7fffffffe678) at mdadm.c:1701
>
>
>
> The same bug is present in the git repository, but another location:
>
> root@kuiper:~/mdadm.git# gdb ./mdadm
> [SNIP]
> Reading symbols from /root/mdadm.git/mdadm...done.
> (gdb) set args --grow --continue /dev/md127
> (gdb) run
> Starting program: /root/mdadm.git/mdadm --grow --continue /dev/md127
>
> Program received signal SIGSEGV, Segmentation fault.
> Grow_continue_command (devname=0x7fffffffe8d0 "/dev/md127", fd=7, backup_file=0x0, verbose=0) at Grow.c:4086
> 4086 if (verify_reshape_position(content,
> (gdb) bt
> #0 Grow_continue_command (devname=0x7fffffffe8d0 "/dev/md127", fd=7, backup_file=0x0, verbose=0) at Grow.c:4086
> #1 0x0000000000406c39 in main (argc=4, argv=0x7fffffffe678) at mdadm.c:1447
>
>
> I also filed a bug against Debian's BTS, but I did not receive a bug number yet. In the meantime, I'd be very happy about any information on how to get my RAID array back into growing. I'm not on the list, please CC me.
>
--grow --continue should only be needed if the array was assembled with
--freeze-reshape (I think).
Normally, the reshape should continue automatically.
cat /proc/mdstat
mdadm -E ....
mdadm -D ...
would be helpful, maybe together with kernel logs if there are any.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-07-10 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 10:46 mdadm-3.2.5: segfault in "--grow --continue" Sebastian Hegler
2012-07-10 13:02 ` NeilBrown [this message]
2012-07-10 16:51 ` Sebastian Hegler
2012-07-11 2:26 ` NeilBrown
2012-07-11 11:15 ` Sebastian Hegler
2012-07-16 6:26 ` NeilBrown
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=20120710230205.171ee562@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=sebastian.hegler@tu-dresden.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).