linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin ESTRABAUD <be@mpstor.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "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: Tue, 26 May 2015 17:44:44 +0100	[thread overview]
Message-ID: <5564A2FC.20809@mpstor.com> (raw)
In-Reply-To: <20150525151429.GB18386@infradead.org>

On 25/05/15 16:14, Christoph Hellwig wrote:
> 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.
>
OK, we'll give 3.18 another shot (we had tried before without luck), but 
if not much as changed we're likely to see the problem also there. I'm 
going to also try running this test over a different SAN fabric (GbE 
instead of 40GbE and see if the issue still occurs).

Thanks,

Ben.

      reply	other threads:[~2015-05-26 16:44 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
2015-05-26 16:44       ` Benjamin ESTRABAUD [this message]

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=5564A2FC.20809@mpstor.com \
    --to=be@mpstor.com \
    --cc=bc@mpstor.com \
    --cc=hch@infradead.org \
    --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).