From: Wols Lists <antlists@youngman.org.uk>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: linux raid wiki - backup files
Date: Sat, 19 Nov 2016 16:03:28 +0000 [thread overview]
Message-ID: <583077D0.5070804@youngman.org.uk> (raw)
I'm updating the mdadm overview at the moment, and I'm giving examples
for changing raid levels etc.
Is a backup file still required? I get the impression with current
kernels and mdadm, any required backup is put in the space left by "data
offset", or if you're adding a disk it stores it in the space on that disk.
Okay, I'll have to document that older versions still need it, but if
that's not needed any more, I'd rather not emphasize it.
I'd also like to confirm my understanding of how a resize works ...
If the number of raid devices is increased, am I right in thinking that
a new stripe one is created from the old stripes one and two, then
written, then the new stripe two is created from the old two and three,
etc etc? In effect, the data slumps down from the old array into the new?
And of course the reverse when a device is removed - it starts with the
highest stripe, which gets pulled upwards so the old array gets pulled
up into the new?
(And during the reshape, you have a marker of the current stripe being
updated, so any stripes above that get read from one array, and below
they get read from the other.)
Cheers,
Wol
next reply other threads:[~2016-11-19 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 16:03 Wols Lists [this message]
2016-11-20 0:27 ` linux raid wiki - backup files Phil Turmel
2016-11-20 14:48 ` Wols Lists
2016-11-21 14:07 ` Phil Turmel
2016-11-21 20:22 ` Anthony Youngman
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=583077D0.5070804@youngman.org.uk \
--to=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).