From: Wols Lists <antlists@youngman.org.uk>
To: Markus Hochholdinger <Markus@hochholdinger.net>,
Xiao Ni <xni@redhat.com>
Cc: Song Liu <song@kernel.org>, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [PATCH] md: fix update super 1.0 on rdev size change
Date: Tue, 16 Nov 2021 16:41:10 +0000 [thread overview]
Message-ID: <79efe789-e018-686c-e6ac-554ad99c4866@youngman.org.uk> (raw)
In-Reply-To: <3122218.nCYcmegLye@enterprise>
On 16/11/2021 09:28, Markus Hochholdinger wrote:
> By using metadata 1.0, the super block is at the end on the logical volumes
> and you can easily do a snpashot of the logical volumes and mount the snapshot
> for backups without calculating or guessing an offset.
Dunno whether now is the time, but if you're moving superblocks, can we
think about (a) moving superblocks to convert between 1.0, 1.1 and 1.2,
and (b) possibly leaving backup copies lying around.
As I say, now might not to be the time to do it, but if you're thinking
about it, an easy way to do it might just hit you in the face, and you
won't leave any landmines if someone comes along later to do it.
(As maintainer of the raid wiki, backup superblocks assisting raid
recovery might be a VERY useful tool !!!)
Cheers,
Wol
next prev parent reply other threads:[~2021-11-16 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 14:28 [PATCH] md: fix update super 1.0 on rdev size change markus
2021-11-15 9:47 ` Xiao Ni
2021-11-15 18:39 ` Markus Hochholdinger
2021-11-15 20:07 ` Wol
2021-11-16 8:35 ` Xiao Ni
2021-11-16 7:53 ` Xiao Ni
2021-11-16 9:28 ` Markus Hochholdinger
2021-11-16 16:41 ` Wols Lists [this message]
2021-11-16 8:36 ` Xiao Ni
2021-11-16 9:24 ` Paul Menzel
2021-11-16 9:44 ` Markus Hochholdinger
2021-11-16 9:52 ` Paul Menzel
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=79efe789-e018-686c-e6ac-554ad99c4866@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=Markus@hochholdinger.net \
--cc=linux-raid@vger.kernel.org \
--cc=song@kernel.org \
--cc=xni@redhat.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