From: Daniel Gnoutcheff <gnoutchd@softwarefreedom.org>
To: antlists <antlists@youngman.org.uk>, 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 16:50:05 -0500 [thread overview]
Message-ID: <d1ff4b3c-a05e-5712-8edd-05d9046f7701@softwarefreedom.org> (raw)
In-Reply-To: <bfbf7ae7-b443-4559-38ba-d7b9710792ba@youngman.org.uk>
On 1/27/21 7:59 PM, antlists wrote:
> 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 ... :-)
Thanks for warning me about reshapes on stretch. I was in fact planning
some reshapes on a production stretch system. I shall reconsider. :)
I would be curious to read the thread in which the raid10 layout reshape
issue has already been discussed, but I've not been able to find it. I
tried 'raid10 reshape', 'raid10 layout reshape', 'raid layout reshape',
and 'reshape "attempt to access beyond end of device"' in the search box
at [1], and I've skimmed the subject lines for the last two month's
worth of messages, but I couldn't find anything applicable. Are there
other terms I should try?
[1] https://www.spinics.net/lists/raid/
Many thanks,
--
Daniel Gnoutcheff
Systems Administrator
Software Freedom Law Center
prev parent reply other threads:[~2021-01-28 21:50 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
2021-01-28 21:50 ` Daniel Gnoutcheff [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=d1ff4b3c-a05e-5712-8edd-05d9046f7701@softwarefreedom.org \
--to=gnoutchd@softwarefreedom.org \
--cc=antlists@youngman.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).