Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Adrian von Bidder <avbidder-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
Cc: nfs@lists.sourceforge.net
Subject: Re: [NFS] NFS performance debugging
Date: Fri, 27 Jun 2008 13:47:53 -0400	[thread overview]
Message-ID: <20080627174753.GE18933@fieldses.org> (raw)
In-Reply-To: <200806270824.54066-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>

On Fri, Jun 27, 2008 at 08:24:49AM +0200, Adrian von Bidder wrote:
> On Thursday 26 June 2008 19.03:42 you wrote:
> > On Thu, Jun 26, 2008 at 08:19:29AM +0200, Adrian von Bidder wrote:
> > > On Wednesday 25 June 2008 18.56:58 J. Bruce Fields wrote:
> > > > On Wed, Jun 25, 2008 at 09:02:42AM +0200, Adrian von Bidder wrote:
> > > > > First tries showed
> > > > >  * There are no acl on my files now
> > > >
> > > > NFSv4 uses an entirely different type of ACL, for which you need
> > > > different client-side tools; see
> > >
> > > I'm absolutely confused on the state of nfs4 acls.  There are so many
> > > old mailing list posts around that it's difficult to see what
> > > information applies to the currentimplementation.  So: are POSIX acls
> > > in the server filesystem somehow mapped to nfsv4 acls on the client
> > > side?  I understand there understands an RFC proposal on how to do
> > > this, and
> > > http://wiki.linux-nfs.org/wiki/index.php/ACLs is very interesting but
> > > doesn't really cover the current state of the implementation.
> >
> > I've attempted to update that wiki page to fix that problem; could you
> > take a look and tell me whether the changes help?
> 
> The summary is: "POSIX ACLs on the server side turn (more or less) into 
> NFSv4 ACL on the client.", correct?

Yes (but note that that translation happens on the server).

> So our current ACL based system of 
> permissions should work except that we can't modify permissions on the 
> client side until I've deployed nfs4 acl tools ...

ACL's will definitely still be enforced correctly, yes--enforcement of
permissions is entirely left up to the exported filesystem.

> > > > 	http://www.citi.umich.edu/projects/nfsv4/linux/nfs4-acl-tools/
> > >
> > > Hmm.  Not packaged in Debian yet?????? ;-)  So work to do for me if I
> > > end up using nfs4
> >
> > Yes.  Volunteers to package those things welcomed....
> 
> ... which means you've possibly got your Debian packager, and I might even 
> be able to do that on company time.

If you get a chance to work on that, that would be great.

> Ok, I guess I know in which direction to put my work now, thanks a lot.  
> (nfs-iostat will be the first thing I'll try, though, to get some more 
> data.)

Yes, that's probably best.  (NFSv4 will be somewhat of a long shot, and
in any case it'll help to first understand better where the time's
going.)

--b.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
    http://vger.kernel.org/vger-lists.html#linux-nfs


      parent reply	other threads:[~2008-06-27 17:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 14:59 [NFS] NFS performance debuggins Adrian von Bidder
     [not found] ` <200806231659.58158-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
2008-06-23 15:15   ` Trond Myklebust
2008-06-23 19:28   ` J. Bruce Fields
2008-06-24 10:17     ` [NFS] NFS performance debugging Adrian von Bidder
     [not found]       ` <200806241217.29243-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
2008-06-24 20:29         ` J. Bruce Fields
2008-06-25  7:02           ` Adrian von Bidder
     [not found]             ` <200806250902.42880-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
2008-06-25 13:20               ` Trond Myklebust
2008-06-25 13:59                 ` Steve Dickson
     [not found]                   ` <48624F34.1070108-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-06-27  7:30                     ` Krishna Kumar2
2008-06-27 13:44                       ` Chuck Lever
     [not found]                         ` <76bd70e30806270644j3e67c83and7b1f7fd6cc2f5f5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-27 18:12                           ` Trond Myklebust
2008-06-30  9:05                           ` Krishna Kumar2
2008-06-27 18:06                       ` Olga Kornievskaia
2008-06-25 16:56               ` J. Bruce Fields
2008-06-26  6:19                 ` Adrian von Bidder
     [not found]                   ` <200806260819.35108-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
2008-06-26 17:03                     ` J. Bruce Fields
2008-06-27  6:24                       ` Adrian von Bidder
     [not found]                         ` <200806270824.54066-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org>
2008-06-27 17:47                           ` J. Bruce Fields [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=20080627174753.GE18933@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=avbidder-xzBkAS4TQxQfv37vnLkPlQ@public.gmane.org \
    --cc=nfs@lists.sourceforge.net \
    /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