From: Vladimir Saveliev <vs@namesys.com>
To: "Aaron D.Ball" <adb@bdi.com>
Cc: reiserfs-list@namesys.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: knfsd and append-only attribute: "operation not permitted"
Date: Fri, 21 Jan 2005 17:44:14 +0300 [thread overview]
Message-ID: <1106318654.3200.38.camel@tribesman.namesys.com> (raw)
In-Reply-To: <8381054C-6B13-11D9-BFA6-000D933B35AA@bdi.com>
Hello
On Thu, 2005-01-20 at 21:45, Aaron D.Ball wrote:
> When I use the kernel-based NFS server to export directories on
> ReiserFS that have the append-only attribute set, I can't access the
> files from the client machines at all: for example, "ls" returns
> "operation not permitted". Is this a known bug? Is there a good
> workaround?
>
It looks like the problem is not in reiserfs, but in nfsd.
fs/nfsd/vfs.c:nfsd_open() refuses to open append only files.
/* Disallow access to files with the append-only bit set or
* with mandatory locking enabled
*/
err = nfserr_perm;
if (IS_APPEND(inode) || IS_ISMNDLK(inode))
goto out;
> I'm running up-to-date Debian sid with Linux 2.6.10 compiled from the
> stock Debian kernel-source package. Everything works fine in other
> contexts, such as
>
> * direct access on the server
> * access via Samba
> * access via the userspace NFS server (which I'm using as a workaround
> for now)
>
> I'd really like to get things working with the kernel-based server so I
> can have locks. Abandoning extended attributes would mean I have to
> monitor certain files and directories for changes and check them after
> the fact rather than simply blocking all the changes I don't want. Is
> there hope? Am I just doing something dumb?
>
>
next parent reply other threads:[~2005-01-21 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8381054C-6B13-11D9-BFA6-000D933B35AA@bdi.com>
2005-01-21 14:44 ` Vladimir Saveliev [this message]
2005-01-21 15:53 ` knfsd and append-only attribute: "operation not permitted" Trond Myklebust
2005-01-21 16:23 ` Aaron D. Ball
2005-01-21 17:08 ` Trond Myklebust
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=1106318654.3200.38.camel@tribesman.namesys.com \
--to=vs@namesys.com \
--cc=adb@bdi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
/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