All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Johannes Schild" <JSchild@gmx.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-nfs@vger.kernel.org
Subject: Re: LAYOUTCOMMIT/LAYOUTRETURN
Date: Tue, 26 Jun 2012 14:43:48 +0200	[thread overview]
Message-ID: <20120626124348.48490@gmx.net> (raw)
In-Reply-To: <1340632000.9620.7.camel@lade.trondhjem.org>

Hi,

thanks for your answers.

But how do i find out, whether the server is using FILE_SYNC?
Is there any other mode like "FILE_ASYNC"?

And if the server is using FILE_SYNC, how does it get LAYOUTCOMMIT?


Thanks in advance


Johannes


-------- Original-Nachricht --------
> Datum: Mon, 25 Jun 2012 09:46:40 -0400
> Von: Trond Myklebust <trond.myklebust@fys.uio.no>
> An: Johannes Schild <JSchild@gmx.de>
> CC: linux-nfs@vger.kernel.org
> Betreff: Re: LAYOUTCOMMIT/LAYOUTRETURN

> On Mon, 2012-06-25 at 09:43 +0200, Johannes Schild wrote:
> > Hi Guys,
> > 
> > i have another question on pNFS. I looked at my Wireshark protocols,
> while i used the FILE-Layout, and i wondered why i have no
> LAYOUTCOMMIT/LAYOUTRETURN statements in my protocols.
> > I transfered one file to my storage server (NETAPP Simulator 8.1 C-Mode)
> and i only got a LAYOUTGET.
> > 
> > cat /proc/self/mountstats | grep LAYOUT says:
> > nfsv4:
> bm0=0xfafe8fff,bml=0x60fdfffe,acl=0x3,sessions,pnfs=LAYOUT_NFSV4_1_FILES
> >     LAYOUTGET: 1 1 0 216 236 0 1 1
> >  LAYOUTCOMMIT: 0 0 0 0 0 0 0 0
> >  LAYOUTRETURN: 0 0 0 0 0 0 0 0 
> 
> A pNFS client should never send LAYOUTCOMMIT to a server that does
> FILE_SYNC writes.
> 
> The Linux pNFS client uses the 'forgetful client' model, so it will
> never send LAYOUTRETURN on layout recalls either. The only case where we
> send LAYOUTRETURN is when the file falls out of the inode cache.
> 
> 
> > Is there any other way to verify that pnfs is used on client site?
> 
> The most direct way is to look for a TCP connection to the data server
> using 'netstat -t'.
> 
> Cheers
>   Trond
> 

-- 
NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!                                  
Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a

  reply	other threads:[~2012-06-26 12:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25  7:43 LAYOUTCOMMIT/LAYOUTRETURN Johannes Schild
2012-06-25  9:04 ` LAYOUTCOMMIT/LAYOUTRETURN Idan Kedar
2012-06-25 13:46 ` LAYOUTCOMMIT/LAYOUTRETURN Trond Myklebust
2012-06-26 12:43   ` Johannes Schild [this message]
2012-06-26 12:54     ` LAYOUTCOMMIT/LAYOUTRETURN Myklebust, Trond
2012-06-26 13:21       ` LAYOUTCOMMIT/LAYOUTRETURN Johannes Schild

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=20120626124348.48490@gmx.net \
    --to=jschild@gmx.de \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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.