All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: nfs@lists.sourceforge.net
Subject: acl_extended_file() and NFS file systems
Date: Wed, 23 Jun 2004 17:11:53 +0100	[thread overview]
Message-ID: <40D9ABC9.1070007@moving-picture.com> (raw)

We've just come across a problem with running 'ls -l' on NFS mounted 
files from a client running Fedora Core 1 with the latest coreutils RPM 
(5.0-34.1)

Running ls -l on a file exported by a RedHat 7.2 system gives

% ls -l /some/remote/file
ls: /some/remote/file: Input/output error
-rw-rw-r--  1 james user 17373 Jun  1 20:02 /some/remote/file

/var/log/messages on the client gives:

Jun 23 16:00:53 wingnut kernel: call_verify: server accept status: 1
Jun 23 16:00:53 wingnut last message repeated 2 times
Jun 23 16:00:53 wingnut kernel: RPC: garbage, exit EIO

I've tracked this down to the use of acl_extended_file() by this version 
of ls - it works OK on local file systems and NFS file systems exported 
by other FC1 machines and Solaris boxes, but gives this error on file 
systems exported by RedHat 7.2 and Irix boxes.

I can reproduce the errors with a simple bit of 'C':

#include <sys/types.h>
#include <acl/libacl.h>
#include <errno.h>

main(int argc, char **argv)
{
         int ret;

         errno = 0;
         ret = acl_extended_file (argv[1]);
         printf("ret = %d\nerrno = %d\n", ret, errno);
         exit (0);
}

(need to link with -lacl)

I've searched around and come across references to a 'noacl' option to 
mount that might help, but mount on Fedora doesn't seem to support this 
- I get:

unknown nfs mount option: noacl

I don't really know if this a real problem (I can easily fix 'ls' by 
backing out the patch to coreutils that introduces this issue), but I 
would like to understand more on what is going on ...


Thanks

James Pearson





-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2004-06-23 16:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23 16:11 James Pearson [this message]
2004-06-23 18:10 ` acl_extended_file() and NFS file systems Steve Dickson
2004-06-23 21:54   ` James Pearson
2004-06-24 15:23     ` Steve Dickson
2004-06-24 15:32     ` James Pearson

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=40D9ABC9.1070007@moving-picture.com \
    --to=james-p@moving-picture.com \
    --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 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.