linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Benjamin ESTRABAUD <be@mpstor.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"bc@mpstor.com" <bc@mpstor.com>
Subject: Re: Issue running buffered writes to a pNFS (NFS 4.1 backed by SAN) filesystem.
Date: Mon, 25 May 2015 08:14:29 -0700	[thread overview]
Message-ID: <20150525151429.GB18386@infradead.org> (raw)
In-Reply-To: <555CB69B.7030108@mpstor.com>

On Wed, May 20, 2015 at 05:30:19PM +0100, Benjamin ESTRABAUD wrote:
> I'm going to try this now (move client and maybe even server to Linux 4.0,
> now that 4.0 has a more "current" stable release).

Only the client is interesting in this case.

> By the way, what is the minimum Linux Kernel version required to connect to
> a NFS v4.1 server using pNFS? We only managed to get this working with
> kernel 4.0 (on the client) and it appears that this is the lowest kernel
> release that supports pNFS block clients (working with Linux pNFS recent
> block server). Could you please confirm this?

The big changes to make the block client useful went into 3.18.  Almost
nothing has changed in the client since.

  reply	other threads:[~2015-05-25 15:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 17:44 Issue running buffered writes to a pNFS (NFS 4.1 backed by SAN) filesystem Benjamin ESTRABAUD
2015-05-15 19:20 ` J. Bruce Fields
2015-05-20 16:27   ` Benjamin ESTRABAUD
2015-05-20 18:31     ` Benjamin ESTRABAUD
2015-05-25 15:13       ` Christoph Hellwig
2015-05-26 16:43         ` Benjamin ESTRABAUD
2015-05-20 19:40     ` J. Bruce Fields
2015-05-21 10:09       ` Benjamin ESTRABAUD
2015-05-17 16:38 ` Christoph Hellwig
2015-05-20 16:30   ` Benjamin ESTRABAUD
2015-05-25 15:14     ` Christoph Hellwig [this message]
2015-05-26 16:44       ` Benjamin ESTRABAUD

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=20150525151429.GB18386@infradead.org \
    --to=hch@infradead.org \
    --cc=bc@mpstor.com \
    --cc=be@mpstor.com \
    --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;
as well as URLs for NNTP newsgroup(s).