All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: acl_extended_file() and NFS file systems
Date: Thu, 24 Jun 2004 16:32:01 +0100	[thread overview]
Message-ID: <40DAF3F1.7030006@moving-picture.com> (raw)
In-Reply-To: <40D9FC0B.6050401@moving-picture.com>

I think I've worked out what is going on ... when I said the client was
a FC1 box, I didn't give all the facts - it's using a kernel based on
the FC1 kernel - actually one from ATrpms (http://atrpms.net/).

It turns out that this kernel has a 'nfsacl' patch (from 
http://acl.bestbits.at/download.html) applied that
adds CONFIG_NFS_ACL (and CONFIG_NFSD_ACL) which are enabled by default -
compiling a new kernel with the CONFIG_NFS_ACL option disabled (i.e.
something closer to a vanilla FC1 kernel), then the problem goes away ...

James Pearson

James Pearson wrote:
> I've put the strace and ethereal outputs at:
> 
> ftp://ftp.moving-picture.com/private/nfs/
> 
> The files 'works' from using a file on a FC1 server
> 
> The files 'fails' from using a file on a RH7.2 server
> 
> Note: it also fails on NFS files from an Irix 6.5.X server
> 
> James Pearson
> 
> Steve Dickson wrote:
> 
>> James Pearson wrote:
>>
>>> 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
>>
>>
>>
>> hmm... it sound like 7.2 is returning garbage but to which
>> over-the-wire operation? Since FC1 does not have ACL support so
>> the getxattr() (that is done by your test program) should
>> be returned EOPNOTSUPP (as it does in my testing) but instead
>> it sounds like the FC1 is actually trying to send something otw..
>> Would it be possible to get a strace and ethereal trace of this
>> phenomenon?
>>
>> SteveD.
>>
>>
>>
> 
> 
> 
> -------------------------------------------------------
> 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
> 




-------------------------------------------------------
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

      parent reply	other threads:[~2004-06-24 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23 16:11 acl_extended_file() and NFS file systems James Pearson
2004-06-23 18:10 ` Steve Dickson
2004-06-23 21:54   ` James Pearson
2004-06-24 15:23     ` Steve Dickson
2004-06-24 15:32     ` James Pearson [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=40DAF3F1.7030006@moving-picture.com \
    --to=james-p@moving-picture.com \
    --cc=SteveD@redhat.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.