[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#448503: marked as done (NFS client problem - writing with group-access fails)

Your message dated Tue, 06 Apr 2010 04:15:23 +0100
with message-id <1270523723.24287.105.camel@localhost>
and subject line Re: NFS client problem - writing with group-access fails
has caused the Debian Bug report #448503,
regarding NFS client problem - writing with group-access fails
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
448503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448503
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
I'm closing this because the previous request to report the bug upstream
was never answered.  If this bug is still present in Linux 2.6.32
(currently in testing, unstable and backports) then please report it
upstream at <https://bugzilla.kernel.org> and let us know the bug
number.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: