From: NeilBrown <neilb@suse.de>
To: Xiao Ni <xni@redhat.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid5 reshape is stuck
Date: Thu, 28 May 2015 08:59:58 +1000 [thread overview]
Message-ID: <20150528085958.0f95e323@notabene.brown> (raw)
In-Reply-To: <476656362.5105083.1432728264276.JavaMail.zimbra@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3958 bytes --]
On Wed, 27 May 2015 08:04:24 -0400 (EDT) Xiao Ni <xni@redhat.com> wrote:
>
>
> ----- Original Message -----
> > From: "NeilBrown" <neilb@suse.de>
> > To: "Xiao Ni" <xni@redhat.com>
> > Cc: linux-raid@vger.kernel.org
> > Sent: Wednesday, May 27, 2015 7:34:49 PM
> > Subject: Re: raid5 reshape is stuck
> >
> > On Wed, 27 May 2015 07:28:04 -0400 (EDT) Xiao Ni <xni@redhat.com> wrote:
> >
> >
> > > [root@intel-waimeabay-hedt-01 mdadm]# cat
> > > /usr/lib/systemd/system/mdadm-grow-continue\@.service
> > > # This file is part of mdadm.
> > > #
> > > # mdadm is free software; you can redistribute it and/or modify it
> > > # under the terms of the GNU General Public License as published by
> > > # the Free Software Foundation; either version 2 of the License, or
> > > # (at your option) any later version.
> > >
> > > [Unit]
> > > Description=Manage MD Reshape on /dev/%I
> > > DefaultDependencies=no
> > >
> > > [Service]
> > > ExecStart=/usr/sbin/mdadm --grow --continue /dev/%I
> > > --backup-file=/root/tmp0
> >
> > Please remove the ---backup-file=/root/tmp0 for further testing. The patch I
> > provided should make that unnecessary.
> >
> > > StandardInput=null
> > > StandardOutput=null
> > > StandardError=null
> >
> > Could you try removing these - that might allow error messages to appear.
> > I wonder why I included them - they shouldn't be needed.
> >
> > Thanks,
> > NeilBrown
> >
> >
>
> [root@intel-waimeabay-hedt-01 mdadm]# mdadm -CR /dev/md0 -l5 -n4 /dev/loop[0-3] --assume-clean
> mdadm: /dev/loop0 appears to be part of a raid array:
> level=raid5 devices=5 ctime=Wed May 27 02:45:08 2015
> mdadm: /dev/loop1 appears to be part of a raid array:
> level=raid5 devices=5 ctime=Wed May 27 02:45:08 2015
> mdadm: /dev/loop2 appears to be part of a raid array:
> level=raid5 devices=5 ctime=Wed May 27 02:45:08 2015
> mdadm: /dev/loop3 appears to be part of a raid array:
> level=raid5 devices=5 ctime=Wed May 27 02:45:08 2015
> mdadm: Defaulting to version 1.2 metadata
> mdadm: array /dev/md0 started.
> [root@intel-waimeabay-hedt-01 mdadm]# mdadm /dev/md0 -a /dev/loop4
> mdadm: added /dev/loop4
> [root@intel-waimeabay-hedt-01 mdadm]# mdadm --grow /dev/md0 --raid-devices=5
> mdadm: Need to backup 6144K of critical section..
> [root@intel-waimeabay-hedt-01 mdadm]# cat /proc/mdstat
> Personalities : [raid6] [raid5] [raid4]
> md0 : active raid5 loop4[4] loop3[3] loop2[2] loop1[1] loop0[0]
> 1532928 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]
> [>....................] reshape = 0.0% (0/510976) finish=532.2min speed=0K/sec
>
> unused devices: <none>
> [root@intel-waimeabay-hedt-01 mdadm]# cat /usr/lib/systemd/system/mdadm-grow-continue\@.service
> # This file is part of mdadm.
> #
> # mdadm is free software; you can redistribute it and/or modify it
> # under the terms of the GNU General Public License as published by
> # the Free Software Foundation; either version 2 of the License, or
> # (at your option) any later version.
>
> [Unit]
> Description=Manage MD Reshape on /dev/%I
> DefaultDependencies=no
>
> [Service]
> ExecStart=/usr/sbin/mdadm --grow --continue /dev/%I
> #StandardInput=null
> #StandardOutput=null
> #StandardError=null
> KillMode=none
>
>
> The problem still exist. And there are messages in /var/log/messages
>
> May 27 08:03:29 intel-waimeabay-hedt-01 systemd: mdadm-grow-continue@md0.service: main process exited, code=exited, status=1/FAILURE
> May 27 08:03:29 intel-waimeabay-hedt-01 systemd: Unit mdadm-grow-continue@md0.service entered failed state.
>
Does
systemctl status -l mdadm-grow-continue@md0.service
report anything different. That was the result I expected from removing the
Standard*=null lines.
I assume the new mdadm is installed in /usr/sbin/mdadm.
Thanks,
NeilBrown
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2015-05-27 22:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1612858661.15347659.1431671671467.JavaMail.zimbra@redhat.com>
2015-05-15 7:00 ` raid5 reshape is stuck Xiao Ni
2015-05-19 11:10 ` Xiao Ni
2015-05-20 23:48 ` NeilBrown
2015-05-21 3:37 ` Xiao Ni
2015-05-21 12:31 ` Xiao Ni
2015-05-22 8:54 ` Xiao Ni
2015-05-25 3:50 ` NeilBrown
2015-05-26 10:00 ` Xiao Ni
2015-05-26 10:48 ` Xiao Ni
2015-05-27 0:02 ` NeilBrown
2015-05-27 1:10 ` NeilBrown
2015-05-27 11:28 ` Xiao Ni
2015-05-27 11:34 ` NeilBrown
2015-05-27 12:04 ` Xiao Ni
2015-05-27 22:59 ` NeilBrown [this message]
2015-05-28 6:32 ` Xiao Ni
2015-05-28 6:49 ` NeilBrown
2015-05-29 11:13 ` XiaoNi
2015-05-29 11:19 ` NeilBrown
2015-05-29 12:19 ` XiaoNi
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=20150528085958.0f95e323@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=xni@redhat.com \
/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).