From: Chris Murphy <lists@colorremedies.com>
To: Eric Wong <e@80x24.org>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: raid1 with several old drives and a big new one
Date: Thu, 30 Jul 2020 21:35:58 -0600 [thread overview]
Message-ID: <CAJCQCtR36ojCgmdUQbyLn_oNQKZn2cnN8FFV7iUWz+pKJaYTfg@mail.gmail.com> (raw)
In-Reply-To: <20200731032212.GA21797@dcvr>
On Thu, Jul 30, 2020 at 9:22 PM Eric Wong <e@80x24.org> wrote:
>
> Chris Murphy <lists@colorremedies.com> wrote:
> > When one of the 2TB fails, there's some likelihood that it'll behave
> > like a partially failing device. Some reads and writes will succeed,
> > others won't. So you'll need to be prepared strategy wise what to do.
> > Ideal scenario is a new 4+TB drive, and use 'btrfs replace' to replace
> > the md concat device. Due to the large number of errors possible with
> > the 'btrfs replace' you might want to use -r option.
>
> If I went ahead with btrfs alone and am prepared to lose some
> (not "all") files; could part of the FS remain usable (and the
> rest restorable from slow backups) w/o involving LVM?
>
> I could make metadata (and maybe system chunks?) raid1c3 or even
> raid1c4 since they seem small and important enough with ancient
> HW in play.
Yes. I'm not sure whether it will mount rw,degraded if 2 devices are
missing though, it might insist on read-only.
--
Chris Murphy
next prev parent reply other threads:[~2020-07-31 3:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 0:16 raid1 with several old drives and a big new one Eric Wong
2020-07-31 2:57 ` Chris Murphy
2020-07-31 3:22 ` Eric Wong
2020-07-31 3:35 ` Chris Murphy [this message]
2020-08-01 9:05 ` Roman Mamedov
2020-07-31 8:29 ` Alberto Bursi
2020-07-31 10:06 ` Eric Wong
2020-07-31 16:13 ` Adam Borowski
2020-08-01 3:40 ` Zygo Blaxell
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=CAJCQCtR36ojCgmdUQbyLn_oNQKZn2cnN8FFV7iUWz+pKJaYTfg@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=e@80x24.org \
--cc=linux-btrfs@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).