From: antlists <antlists@youngman.org.uk>
To: Daniel Gnoutcheff <gnoutchd@softwarefreedom.org>,
linux-raid@vger.kernel.org
Subject: Re: "attempt to access beyond end of device" when reshaping raid10 from near=2 to offset=2
Date: Thu, 28 Jan 2021 00:59:56 +0000 [thread overview]
Message-ID: <bfbf7ae7-b443-4559-38ba-d7b9710792ba@youngman.org.uk> (raw)
In-Reply-To: <09505ed1-ad29-28f1-627e-8a6a0b8df3a4@softwarefreedom.org>
On 27/01/2021 22:15, Daniel Gnoutcheff wrote:
> Greets,
>
> Whilst experimenting with array reshaping, I've found that if I create a
> near=2 raid10 like so:
I seem to remember this coming up very recently. And I also seem to
remember them coming up with fixes but I'm not sure if it's solved.
So if you search the archive you should find a recent thread and an
update should fix it properly soon.
Oh - and as for Stretch, old mdadm and Ubuntu are known to be, shall we
say, problematic when you reshape an array, so please try not to ... :-)
Cheers,
Wol
next prev parent reply other threads:[~2021-01-28 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 22:15 "attempt to access beyond end of device" when reshaping raid10 from near=2 to offset=2 Daniel Gnoutcheff
2021-01-28 0:59 ` antlists [this message]
2021-01-28 21:50 ` Daniel Gnoutcheff
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=bfbf7ae7-b443-4559-38ba-d7b9710792ba@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=gnoutchd@softwarefreedom.org \
--cc=linux-raid@vger.kernel.org \
/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