public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: Nix <nix@esperi.org.uk>
Cc: John Stoffel <john@stoffel.org>,
	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 14:50:26 -0400	[thread overview]
Message-ID: <24306.20210.265626.431196@quad.stoffel.home> (raw)
In-Reply-To: <875zbi3r46.fsf@esperi.org.uk>

>>>>> "Nix" == Nix  <nix@esperi.org.uk> writes:

Nix> 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?

Nix> Side note: NFSv4 really is much much better at this stuff than v3
Nix> ever was. With a fast enough network connection, I find NFSv4 as
Nix> fast for more or less all workloads as NFSv3 was, mostly because
Nix> of the lease support in v4 allowing client-side caching of the
Nix> vast majority of files and directories that are either not
Nix> written to or only written to by one client in a given short time
Nix> window. (Obviously it also helps if your network is fast enough:
Nix> 1GbE is going to be saturated many times over by a RAID array of
Nix> any but the slowest modern HDDs. 10GbE and small 10GbE-capable
Nix> switches are not very costly these days and is definitely worth
Nix> investing in on the NFS server and any clients you care about.)

I've been thinking about moving to NFSv4 at home, since my main file
server has my main desktop as an NFS and LDAP client for
authentication.  Works quite well, and I don't care if my dekstop
reboots on my, since the homedir is elsewhere.

John

  reply	other threads:[~2020-06-23 18:50 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
2020-06-23 18:50     ` John Stoffel [this message]
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=24306.20210.265626.431196@quad.stoffel.home \
    --to=john@stoffel.org \
    --cc=arequipeno@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=nix@esperi.org.uk \
    /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