From: Anthony Youngman <antlists@youngman.org.uk>
To: Phil Turmel <philip@turmel.org>,
linux-raid <linux-raid@vger.kernel.org>,
neilb@suse.com
Subject: Re: linux raid wiki - backup files
Date: Mon, 21 Nov 2016 20:22:09 +0000 [thread overview]
Message-ID: <c3d16a30-b36e-3d26-f30a-441b236f7107@youngman.org.uk> (raw)
In-Reply-To: <4febebb6-0442-cc5e-45d5-e041e21e2d95@turmel.org>
On 21/11/16 14:07, Phil Turmel wrote:
> On 11/20/2016 09:48 AM, Wols Lists wrote:
>> On 20/11/16 00:27, Phil Turmel wrote:
>>> Yes. But the new stripes lay on top of the old stripes, unless you move
>>> the data offset. Which is why a backup file holds the old stripe just
>>> in case. If you can move the offset, you use the lower offset for the
>>> lower addresses in the array, and the higher offset for the higher
>>> addresses, on either side of the reshape position.
>>
>> Okay, understood. So v0.9 and v1.0 always need a backup for a reshape.
Having looked at the man page, this now seems obvious - the superblock
is at the end, so the data offset is 0. But for a 1.0 array, could we
create a data offset?
(So, if we created a data offset, we could then move the superblock and
convert a 1.0 to 1.1 or 1.2? Okay, it can't do it now, but it looks to
me like it shouldn't be that hard ... ?)
>>
>> But if we have a data offset with v1.2, a reshape will use that space if
>> it can rather than needing a backup file?
>
I'm guessing that 1.0 and 1.1 defaulted to no data offset to speak of?
And if we (can) create a decent data offset, we can then use that in
exactly the same way as with v1.2?
Cheers,
Wol
next prev parent reply other threads:[~2016-11-21 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 16:03 linux raid wiki - backup files Wols Lists
2016-11-20 0:27 ` Phil Turmel
2016-11-20 14:48 ` Wols Lists
2016-11-21 14:07 ` Phil Turmel
2016-11-21 20:22 ` Anthony Youngman [this message]
2016-11-21 21:02 ` Phil Turmel
2016-11-21 21:30 ` Anthony Youngman
2016-11-21 21:40 ` Phil Turmel
2016-11-21 22:45 ` NeilBrown
2016-11-22 23:16 ` Anthony Youngman
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=c3d16a30-b36e-3d26-f30a-441b236f7107@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=philip@turmel.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).