From: Wols Lists <antlists@youngman.org.uk>
To: Reindl Harald <h.reindl@thelounge.net>,
Ram Ramesh <rramesh2400@gmail.com>,
Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: Is it possible to break one full RAID-1 to two degraded RAID-1?
Date: Thu, 30 Jan 2020 07:27:25 +0000 [thread overview]
Message-ID: <5E32855D.3020906@youngman.org.uk> (raw)
In-Reply-To: <551449ed-49f9-e567-09d3-981f4cf9eea9@thelounge.net>
On 30/01/20 06:30, Reindl Harald wrote:
>> Thanks. I thought of this, but both disk in question are nvme ssd with
>> > manually added heat sink. It will be a hassle to remove and reinstall. I
>> > think I will go with the back up rather than remove disk physically.
> why would you remove it phyiscally to remove it rom the array? seriously?
Because if you physically remove it, BOTH disks will think they are the
surviving copy. You could "assemble" either disk on its own and recover
the array.
But if you remove a disk with --fail --remove, does that tamper with the
superblock? Would that prevent that disk being re-assembled on its own?
Seriously. I don't know. And were I in the OP's shoes I would be asking
the same question.
This is where you want something COW in the stack. Lvm. Btrfs. Where you
can just take a snapshot, upgrade the system, and if it all goes
pear-shaped you throw the snapshot away.
Cheers,
Wol
next prev parent reply other threads:[~2020-01-30 7:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 3:17 Is it possible to break one full RAID-1 to two degraded RAID-1? Ram Ramesh
2020-01-29 4:09 ` Reindl Harald
2020-01-29 22:32 ` Ram Ramesh
2020-01-30 6:30 ` Reindl Harald
2020-01-30 7:27 ` Wols Lists [this message]
2020-02-07 7:02 ` Ram Ramesh
2020-02-07 9:27 ` Wols Lists
2020-02-07 14:49 ` Ram Ramesh
2020-02-07 14:55 ` Reindl Harald
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=5E32855D.3020906@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=h.reindl@thelounge.net \
--cc=linux-raid@vger.kernel.org \
--cc=rramesh2400@gmail.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;
as well as URLs for NNTP newsgroup(s).