From: Nix <nix@esperi.org.uk>
To: John Stoffel <john@stoffel.org>
Cc: Ian Pilcher <arequipeno@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: RAID types & chunks sizes for new NAS drives
Date: Tue, 23 Jun 2020 13:26:33 +0100 [thread overview]
Message-ID: <875zbi3r46.fsf@esperi.org.uk> (raw)
In-Reply-To: <24305.24232.459249.386799@quad.stoffel.home> (John Stoffel's message of "Mon, 22 Jun 2020 21:45:12 -0400")
On 23 Jun 2020, John Stoffel told this:
> You also don't say how *big* your disks will be, and if your 5 bay NAS
> box can even split like that, and if it has the CPU to handle that.
> Is it an NFS connection to the rest of your systems?
Side note: NFSv4 really is much much better at this stuff than v3 ever
was. With a fast enough network connection, I find NFSv4 as fast for
more or less all workloads as NFSv3 was, mostly because of the lease
support in v4 allowing client-side caching of the vast majority of files
and directories that are either not written to or only written to by one
client in a given short time window. (Obviously it also helps if your
network is fast enough: 1GbE is going to be saturated many times over by
a RAID array of any but the slowest modern HDDs. 10GbE and small
10GbE-capable switches are not very costly these days and is definitely
worth investing in on the NFS server and any clients you care about.)
next prev parent reply other threads:[~2020-06-23 12:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 16:23 RAID types & chunks sizes for new NAS drives Ian Pilcher
2020-06-23 1:45 ` John Stoffel
2020-06-23 2:31 ` o1bigtenor
2020-06-23 17:01 ` John Stoffel
2020-06-24 22:13 ` o1bigtenor
2020-06-23 12:26 ` Nix [this message]
2020-06-23 18:50 ` John Stoffel
2020-06-23 15:36 ` antlists
2020-06-23 18:55 ` John Stoffel
2020-06-24 12:32 ` Phil Turmel
2020-06-24 14:49 ` John Stoffel
2020-06-24 18:41 ` Wols Lists
2020-06-23 20:27 ` Ian Pilcher
2020-06-23 21:30 ` John Stoffel
2020-06-23 23:16 ` Ian Pilcher
2020-06-24 0:34 ` John Stoffel
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=875zbi3r46.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=arequipeno@gmail.com \
--cc=john@stoffel.org \
--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.