Bug#448503: NFS client problem - writing with group-access fails
Package: linux-image-2.6.18-5-686
Version: 2.6.18+6etch2
Severity: important
This is a re-opening of an error reported as Bug#448161
for the package
Package: nfs-common
Version: 1.0.10-6+etch.1
because its maintainer
("Steinar H. Gunderson" <sgunderson@bigfoot.com>)
[thank you, I took your advice] told me that the nfs-common, and
nfs-utils package are the wrong address to turn to with nfs client
permission problems.
Thus I'm repeating the description here. I can also tell you,
that a 2.6.20-version (2.6.20-3), that I installed on some
machines does not(!) solve the problem (yet), should that be
of any help.
The sarge-systems that work run on kernels 2.6.8-4-686 (plain
from the Debian 'proposed update' repository, without
modification), and (self-compiled) 2.6.12-1-686 with an nfs-patch
to avoid an nfs cookie-sign-bit problem as it arises from SGI's
IRIX e.g. The patch in 2.6.12 is unrelated to the problem presented
here, as far as I can tell!
If I can be of any further help in this, please don't hesitate to
contact me.
Here's the problem itself:
When trying to alter/change/overwrite a file via nfs, that
the user doesn't own, but where the file belongs to and is
writeable by a group, that the user is in as his non-primary
group also, an I/O ("operation not permitted") error is reported
and the operation fails. This happens only, when trying to change
the file, pure access or reading works fine.
The nfs-protocol should be version 3, as the nfs-server is an
AIX v5.2 system.
The systems involved run on Debian v4.0 ('etch' and
'etch-proposed-updates').
Systems on 'sarge' and 'sarge-proposed-updates' worked and still
do flawlessly here, and raise no problem with respect to this
behaviour; nor do other Unix-variants. Only 'etch' seems to be
affected.
Thanks and greetings,
Ruediger Oberhage
Reply to: