All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Reindl Harald <h.reindl@thelounge.net>
Cc: George Rapp <george.rapp@gmail.com>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Recommended filesystem for RAID 6
Date: Wed, 12 Aug 2020 00:33:05 +0500	[thread overview]
Message-ID: <20200812003305.6628dd6e@natsu> (raw)
In-Reply-To: <ea7232af-a411-6b16-d03e-6b21c14cc5be@thelounge.net>

On Tue, 11 Aug 2020 20:57:15 +0200
Reindl Harald <h.reindl@thelounge.net> wrote:

> > Whichever filesystem you choose, you will end up with a huge single point of
> > failure, and any trouble with that FS or the underlying array put all your
> > data instantly at risk. 
> 
> calling an array where you can lose *two* disks as
> single-point-of-failure is absurd

As noted before, not just *disks* can fail, plenty of other things to fail in
a storage server, and they can easily take down, say, a half of all disks, or
random portions of them in increments of four. Even if temporarily -- that
surely will be "unexpected" to that single precious 20TB filesystem. How will
it behave, who knows. Do you know? For added fun, reconnect the drives back 30
seconds later. Oh, let's write to linux-raid for how to bring back a half of
RAID6 from the Spare (S) status. Or find some HOWTO suggesting a random
--create without --assume-clean. And if the FS goes corrupt, now you suddenly
need *all* your backups, not just 1 drive worth of them.

> no raid can replace backups anyways

All too often I've seen RAID being used as an implicit excuse to be lenient
about backups. Heck, I know from personal experience how enticing that can be.

> > Most likely you do not. And the RAID's main purpose in that case is to just
> > have a unified storage pool, for the convenience of not having to manage free
> > space across so many drives. But given the above, I would suggest leaving the
> > drives with their individual FSes, and just running MergerFS on top: 
> > https://www.teknophiles.com/2018/02/19/disk-pooling-in-linux-with-mergerfs/
> 
> you just move the complexity to something not used by many people for
> what exactly to gain? the rives are still in the same machine

To gain total independence of drives from each other, you can pull any drive
out of the machine, plug it in somewhere else, and it will have a proper
filesystem and readable files on it. Writable, even.

Compared to a 16-drive RAID6, where you either have a whopping 14 disks
present, connected, powered, spinning, healthy, online, OR you have useless
binary junk instead of any data.

Of course I do not insist my way is the best for everyone, but I hope now you
can better understand the concerns and reasons for choosing it. :)

-- 
With respect,
Roman

  reply	other threads:[~2020-08-11 19:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11  4:42 Recommended filesystem for RAID 6 George Rapp
2020-08-11 15:06 ` Roy Sigurd Karlsbakk
2020-08-11 19:19   ` Michael Fritscher
2020-08-11 19:45     ` Wols Lists
2020-08-22  1:31       ` David C. Rankin
2020-08-22  7:25         ` Peter Grandi
2020-08-22  9:38           ` Wols Lists
2020-08-22 19:21             ` Chris Murphy
2020-08-22 19:04           ` Chris Murphy
2020-08-22 18:50       ` Chris Murphy
2020-08-22 19:54         ` Kai Stian Olstad
2020-08-22 23:50         ` antlists
2020-08-12 14:07     ` Nix
2020-08-11 15:22 ` antlists
2020-08-11 16:23 ` Roman Mamedov
2020-08-11 18:57   ` Reindl Harald
2020-08-11 19:33     ` Roman Mamedov [this message]
2020-08-11 19:49       ` Rudy Zijlstra
2020-08-11 20:13         ` Roman Mamedov
2020-08-11 20:17           ` Reindl Harald
2020-08-11 20:12       ` Reindl Harald
2020-08-11 22:14   ` Roy Sigurd Karlsbakk
2020-08-12 14:16   ` Nix
2020-08-12 14:41     ` Roman Mamedov
2020-08-12 20:44 ` Peter Grandi

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=20200812003305.6628dd6e@natsu \
    --to=rm@romanrm.net \
    --cc=george.rapp@gmail.com \
    --cc=h.reindl@thelounge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.