All of lore.kernel.org
 help / color / mirror / Atom feed
From: pg@mdraid.list.sabi.co.UK (Peter Grandi)
To: list Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Recommended filesystem for RAID 6
Date: Sat, 22 Aug 2020 08:25:41 +0100	[thread overview]
Message-ID: <24384.51317.30569.169686@cyme.ty.sabi.co.uk> (raw)
In-Reply-To: <05661c44-8193-6bba-67c9-4e0d220eb348@suddenlinkmail.com>

>> [...] Note that it IS a shingled drive, so fine for backup,
>> much less so for anything else.

It is fine for backup especially if used as a tape that is say
divided into partitions and backup is done using 'dd' (but
careful if using Btrfs) or 'tar' or similar. If using 'rsync' or
similar those still write a lot of inodes and often small files
if they are present in the source.

>> I'm not sure whether btrfs would be a good choice or not ...

> [...] btrfs did NOT play well with raid 5/6. It may be old
> info, but:
> https://superuser.com/questions/1131701/btrfs-over-mdadm-raid6

That seems based on some misunderstanding: native Btrfs 5/6 has
some "limitations", like most of its volume management, but
running over MS RAID 5/6 is much the same as running on top of a
single disk, so fine. MD RAID 5/6 takes care of redundancy so
there is no need to have metadata in 'dup' mode.

Using RAID 5/6 with SMR drives can result in pretty huge delays
(IIRC a previous poster has given some relevant URL) on writing
or on rebuilding, as the "chunk" size is very likely not to be
very congruent with the SMT zones.

  reply	other threads:[~2020-08-22  7:25 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 [this message]
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=24384.51317.30569.169686@cyme.ty.sabi.co.uk \
    --to=pg@mdraid.list.sabi.co.uk \
    --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.