All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Rapp <george.rapp@gmail.com>
To: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Recommended filesystem for RAID 6
Date: Tue, 11 Aug 2020 00:42:33 -0400	[thread overview]
Message-ID: <CAF-KpgYcEF5juR9nFPifZunPPGW73kWVG9fjR3=WpufxXJcewg@mail.gmail.com> (raw)

Hello Linux RAID community -

I've been running an assortment of software RAID arrays for a while
now (my oldest Creation Time according to 'mdadm --detail' is April
2011) but have been meaning to consolidate my five active arrays into
something easier to manage. This weekend, I finally found enough cheap
2TB disks to get started. I'm planning on creating a RAID 6 array due
to the age and consumer-grade quality of my 16 2TB disks.

Use case is long-term storage of many small files and a few large ones
(family photos and videos, backups of other systems, working copies of
photo, audio, and video edits, etc.)? Current usable space is about
10TB but my end state vision is probably upwards of 20TB. I'll
probably consign the slowest working disks in the server to an archive
filesystem, either RAID 1 or RAID 5, for stuff I care less about and
backups; the archive part can be ignored for the purposes of this
exercise.

My question is: what filesystem type would be best practice for my use
case and size requirements on the big array? (I have reviewed
https://raid.wiki.kernel.org/index.php/RAID_and_filesystems, but am
looking for practitioners' recommendations.)  I've run ext4
exclusively on my arrays to date, but have been reading up on xfs; is
there another filesystem type I should consider? Finally, are there
any pitfalls I should know about in my high-level design?

Details:
# uname -a
Linux backend5 5.7.11-200.fc32.x86_64 #1 SMP Wed Jul 29 17:15:52 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
# mdadm --version
mdadm - v4.1 - 2018-10-01

Finally, and this is inadequate given the value I've received from the
efforts of this group, but thanks for many years of supporting mdadm
and helping with software RAID issues, including the recovery
procedures you have written up and guided me through. This group's
efforts have saved my data, my bacon, and my sanity on more than one
occasion.
--
George Rapp  (Pataskala, OH) Home: george.rapp -- at -- gmail.com
LinkedIn profile: https://www.linkedin.com/in/georgerapp
Phone: +1 740 936 RAPP (740 936 7277)

             reply	other threads:[~2020-08-11  4:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11  4:42 George Rapp [this message]
2020-08-11 15:06 ` Recommended filesystem for RAID 6 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
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='CAF-KpgYcEF5juR9nFPifZunPPGW73kWVG9fjR3=WpufxXJcewg@mail.gmail.com' \
    --to=george.rapp@gmail.com \
    --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.