From: NeilBrown <neilb@suse.de>
To: Nikolay Kichukov <hijacker@oldum.net>
Cc: "Mathias Burén" <mathias.buren@gmail.com>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: add another disk to existing raid 0, ie grow raid 0 possible?
Date: Thu, 9 Feb 2012 14:50:54 +1100 [thread overview]
Message-ID: <20120209145054.4443a48b@notabene.brown> (raw)
In-Reply-To: <4F21396D.7030308@oldum.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 26 Jan 2012 13:30:53 +0200 Nikolay Kichukov <hijacker@oldum.net>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello Neil,
>
> Here goes the details. Once again, no valuable data, just curious what has gone wrong in that case:
>
> dmesg output, first I stopped md2, then assembled it again to perform the grow.
> http://pastebin.com/HkPVEKad
>
> mdadm -E output:
> http://pastebin.com/pJCjvrJE
>
> The system runs GNU/Debian testing with latest updates from security-testing applied.
> Kernel: 3.1.0-1-amd64
> mdadm: 3.2.2-1
>
> Let me know should you need any further information.
I've finally had a look at this and unfortunately cannot find the problem.
The main reason being that I cannot reproduce it.
I built the same kernel and mdadm and created a very similar array and
tried to grow it and it all went smoothly.
In your case it didn't start the reshape at all (reshape position was zero) so
something went wrong very early.
If you feel like trying to reproduce it again that might be helpful.
Then I would ask you to run the "mdadm --grow" command under
strace -o /tmp/foo -f mdadm --grow ....
and send me the /tmp/foo. But I won't be surprised if you cannot reproduce.
Sad really.
Thanks anyway,
NeilBrown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iQIVAwUBTzNCnjnsnt1WYoG5AQKYmQ/7BpQMjqjgceyMgbl5xFE3rNf0Raia5Og0
5UrxQtNDD+rKnQgHUN3WJizXZ+T+qN0FAFxUs4XArRdZCNN3QHeMxdSv1h3DPVta
roKxjeRNgLKf11GGm6Vw4z8wJlfhvF0pDW7SVysIO/0IXBy1OK7ll3j45Hjp0Tz4
L46//YsrRqijGz8eoOh7QXMF2YVEaD6Q5xbqM4TL4Bsovsl2ii9aTWlETpWuh/GB
c/p2uU4I6G3H/7fpd3kF2/UIwoR5kwUacRICmn4kwq4wTMjzPFc/rHynFF/AZMHR
PrdS/BG5pwr75IMnInFuKeLK5LvlwWzcnDwWx5GRhJi0LlYlws2JJrMbAnn/zbrM
mzNQUZK8y+j0Bo5xArpl9D715fGxajmPyHInHR3vOH5xOkIW8Irkue3TxVyq/oUD
HEljE6tBdOp9meiECTAP4LBLeQmyohIPw722F/qsc54nG3dYztRV0vFJftubw1X0
LAzQrxzqy6lSWnGyJjE/kXEqcIFPqUw4q7JmXEKe5QDoPNRo9KPVO0sLUB+7O3Of
IXMTxf8Gz/m5tfsx3DmSRVnZkwpwwlr2GUHusFTQdrnQYfKhGjrFw27ygdvmvqtV
zuEVf2tr2G/eGBt2A9Vv+hthZzYpesv1JT04gA9dnyQyIfFhA15JAXPJOqAXv8D3
8f70+yvjlBg=
=l9xR
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-02-09 3:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 10:26 add another disk to existing raid 0, ie grow raid 0 possible? Nikolay Kichukov
2012-01-26 10:47 ` Mathias Burén
2012-01-26 10:57 ` NeilBrown
2012-01-26 11:30 ` Nikolay Kichukov
2012-01-26 11:52 ` NeilBrown
2012-01-26 12:12 ` Nikolay Kichukov
2012-02-09 3:50 ` NeilBrown [this message]
2012-02-10 14:10 ` Nikolay Kichukov
2012-02-12 22:07 ` NeilBrown
2012-02-14 9:43 ` Nikolay Kichukov
2012-02-16 6:55 ` NeilBrown
2012-02-16 15:38 ` Nikolay Kichukov
2012-02-20 5: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=20120209145054.4443a48b@notabene.brown \
--to=neilb@suse.de \
--cc=hijacker@oldum.net \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@gmail.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).