From: Andy Smith <andy@strugglers.net>
To: linux-raid@vger.kernel.org
Subject: Re: MDRaid Rollback
Date: Wed, 24 Mar 2021 14:44:07 +0000 [thread overview]
Message-ID: <20210324144407.GL3712@bitfolk.com> (raw)
In-Reply-To: <CA+OzjxLW2Vw-ecs7jNELecpYxoBbK767pXEV8rFVaQp_HXfjOg@mail.gmail.com>
Hello,
On Wed, Mar 24, 2021 at 01:04:07PM +0200, Shaun Glass wrote:
> Would just like to know if it is possible at all to break a mirror and
> convert a md device back to its original state without losing data ?
The default metadata version (1.2) is placed at the start of an
array, so even if zeroed this will prevent the array member being
used as the filesystem that is on top of it.
If you have metadata version 0,9 or 1.0 which are at the end then I
don't see why it wouldn't work. I've never done it though so try it
out first on loop devices.
Don't forget to "mdadm --zero-superblock /dev/sda1" (or whatever
devices) for the member device that you have failed out of the
array, so it is no longer treated as part of an array,
But, this being a RAID-1 you have at least two devices so wouldn't
it be safer to:
- Fail out one device
- Zero that device
- Create new filesystem on the removed device
- Copy data onto it from the still-running array that is currently
degraded
- Use new filesystem for whatever you wanted
?
Depending on what you are trying to achieve you could also import
the broken our device as ANOTHER MD RAID-1 array so both arrays are
running degraded (and now divergent).
Finally, if you are on superblock versions 1.1 or 1.2 you may be
able to work out the offset into the device and use a loop device to
skip that, so treating it as a normal filesystem:
https://raid.wiki.kernel.org/index.php/RAID_superblock_formats#The_version-1_Superblock_Format
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
next prev parent reply other threads:[~2021-03-24 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 11:04 MDRaid Rollback Shaun Glass
2021-03-24 14:34 ` Reindl Harald
2021-03-24 14:44 ` Andy Smith [this message]
2021-03-24 15:13 ` Roman Mamedov
2021-03-24 21:50 ` Wols Lists
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=20210324144407.GL3712@bitfolk.com \
--to=andy@strugglers.net \
--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