From: Daniel Pocock <daniel@pocock.pro>
To: linux-nfs@vger.kernel.org
Subject: storage controllers for use with NFS+BtrFs
Date: Mon, 19 Jan 2015 22:23:43 +0100 [thread overview]
Message-ID: <54BD75DF.9010702@pocock.pro> (raw)
I've been looking into the issue of which storage controllers are
suitable for use with NFS + BtrFs (or NFS + ZFS) and put some comments
about it on my blog[1] today.
I understand that for NFS it is generally desirable to have non-volatile
write cache if you want good write performance.
On the other hand, self-healing file systems (BtrFs and ZFS) like having
direct access to disks and those RAID cards with caches don't always
give the same level of access to the volume.
Can anybody give any practical suggestions about how to reconcile these
requirements and experience good NFS write performance onto these
filesystems given the type of HBA and RAID cards available?
1. http://danielpocock.com/storage-controllers-for-small-linux-nfs-networks
next reply other threads:[~2015-01-19 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 21:23 Daniel Pocock [this message]
2015-01-20 13:25 ` storage controllers for use with NFS+BtrFs Benjamin Coddington
2015-01-20 13:38 ` Daniel Pocock
2015-01-20 14:12 ` Benjamin Coddington
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=54BD75DF.9010702@pocock.pro \
--to=daniel@pocock.pro \
--cc=linux-nfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox