From: Frank van Maarseveen <frankvm@frankvm.com>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Janos Farkas <chexum+dev@gmail.com>
Subject: Re: nfs problems with 2.6.18-rc1
Date: Thu, 20 Jul 2006 10:11:43 +0200 [thread overview]
Message-ID: <20060720081143.GA1408@janus> (raw)
In-Reply-To: <17597.28376.805867.197599@cse.unsw.edu.au>
On Wed, Jul 19, 2006 at 09:29:28AM +1000, Neil Brown wrote:
[...]
>
> > 13:37:51.254708 access fh Unknown/0100000100FD000002000000755104000AA487A20000001F0AA487A200030001 001f
> > 13:37:51.255375 reply ok 32 access ERROR: Permission denied attr:
>
> 'access' should never return 'Permission denied' so there is
> definitely something wrong here. I was expected nfserr_acces rather
> than nfserr_perm...
Maybe a silly remark but:
EACCES = Permission denied
EPERM = Operation not permitted
--
Frank
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
WARNING: multiple messages have this Message-ID (diff)
From: Frank van Maarseveen <frankvm@frankvm.com>
To: Neil Brown <neilb@suse.de>
Cc: Janos Farkas <chexum+dev@gmail.com>,
nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [NFS] nfs problems with 2.6.18-rc1
Date: Thu, 20 Jul 2006 10:11:43 +0200 [thread overview]
Message-ID: <20060720081143.GA1408@janus> (raw)
In-Reply-To: <17597.28376.805867.197599@cse.unsw.edu.au>
On Wed, Jul 19, 2006 at 09:29:28AM +1000, Neil Brown wrote:
[...]
>
> > 13:37:51.254708 access fh Unknown/0100000100FD000002000000755104000AA487A20000001F0AA487A200030001 001f
> > 13:37:51.255375 reply ok 32 access ERROR: Permission denied attr:
>
> 'access' should never return 'Permission denied' so there is
> definitely something wrong here. I was expected nfserr_acces rather
> than nfserr_perm...
Maybe a silly remark but:
EACCES = Permission denied
EPERM = Operation not permitted
--
Frank
next prev parent reply other threads:[~2006-07-20 8:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 18:22 nfs problems with 2.6.18-rc1 Janos Farkas
2006-07-13 18:22 ` Janos Farkas
2006-07-16 23:23 ` Neil Brown
2006-07-16 23:23 ` Neil Brown
2006-07-17 10:08 ` Janos Farkas
2006-07-17 10:08 ` Janos Farkas
2006-07-18 12:20 ` Janos Farkas
2006-07-18 12:20 ` Janos Farkas
2006-07-18 23:29 ` Neil Brown
2006-07-18 23:29 ` Neil Brown
2006-07-20 8:11 ` Frank van Maarseveen [this message]
2006-07-20 8:11 ` [NFS] " Frank van Maarseveen
2006-07-17 9:03 ` Tony Reix
2006-07-17 9:03 ` [NFS] " Tony Reix
2006-07-17 11:25 ` Janos Farkas
2006-07-17 11:25 ` Janos Farkas
-- strict thread matches above, loose matches on Subject: below --
2006-07-13 20:15 Ottman, Tom
2006-07-13 20:38 Gilman, Mark
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=20060720081143.GA1408@janus \
--to=frankvm@frankvm.com \
--cc=chexum+dev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--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.