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: Mon, 20 Feb 2012 16:26:14 +1100 [thread overview]
Message-ID: <20120220162614.2aa71a57@notabene.brown> (raw)
In-Reply-To: <4F3D230C.5000503@oldum.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 16 Feb 2012 17:38:52 +0200 Nikolay Kichukov <hijacker@oldum.net>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
> It really might be fixed in recent code, just for consistency:
>
> dpkg -l | grep mdadm
> ii mdadm 3.2.3-2 tool to administer Linux MD arrays
> (software RAID)
>
> uname -a
> Linux hanna64 3.1.0-1-amd64 #1 SMP Tue Jan 10 05:01:58 UTC 2012 x86_64 GNU/Linux
>
Odd.. I cannot find any changes since then that would fix the problem.
The main problem is that mdadm decides that /dev/loop2 is too small.
The size that it wants it to be that it extracts from the array looks
correct. I cannot see from the trace what size it thinks /dev/loop2 is,
but presumably it is the same as raid_device3.loopback, which is definitely
big enough.
As I said .. odd.
NeilBrown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iQIVAwUBT0HZdjnsnt1WYoG5AQIZuxAAr2J8b7g3L2V/mBbqxAURqS+fQ5vmNEyC
/5aVajff4nsbufHHbizhoWUP9RZ3zXpAvIJnpnwhT9Lj3ebnSIRVximJqKIhm7ki
WsmZdzIyK9w438LjzQaX6+ChwWTR2O+YvvxILmC5i34KoqSGqsI7ID1g1eNL2Nyk
eEPxYoN3vQxWGMRYM3bu8U0aDJBcDvYVIY+cdARS1lYi8j3ZW+NoWkj5itxq9cHx
HVx/5q7QNG8vQ/E6QepcehKChD6K+46iTeAlqFs3bTTy18teffRvsy7KGNQKHEOu
J+52iTi5FcPkD5iHFmYTZCaXVtJI02zh/qfNWhHfdygZ9Kfy3be/Gh92dohAw50s
FJseCAoaqAZa02fMqRf0NUBd6daCKTMNkW6fNOTe+z9+hhj6dXc13eYZUl4xCdvu
DYCKIf6lxcatu/19Pmf5YcMN8LxSZnPEoAV7J3JSqKxaVRRXY3OauN89fjtcKZqE
xR6SsoNnFclDYL44+X0wWmbqVHn8t+cZUTxeGfB4Nuy9nEA8pN6RuwcUicwCN3V4
HUgoWZjV1J09q7Jn0Wk34Mf1LBQYEeR0b69P6RNsY21xuxRp2HhjA/k+NxyWfpBb
j2R5SWEXj+ClMjkrgZHy/iyoqgecbEdFPAr7C/sflul+rTtPhUiJjFkmWIYqKNDm
FH7y2vB5AKE=
=hlIm
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2012-02-20 5:26 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
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 [this message]
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=20120220162614.2aa71a57@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).