Bug 134372

Summary:	Nfsv4 : Pynfs test failing - change attribute not affected by SETATTR(mode)
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Forgotten User b5BnQSUi71 <forgotten_b5BnQSUi71>
Component:	Other	Assignee:	Neil Brown <nfbrown>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Alpha 2
Target Milestone:	---
Hardware:	x86
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User b5BnQSUi71 2005-11-18 10:26:17 UTC

Pynfs (now called newpynfs), a suite of several Python tools for NFS4 is used
for testing NFSv4 RFC compliance. It can be downloaded here
http://www.citi.umich.edu/projects/nfsv4/pynfs/

Steps to reproduce the bug:
1. Setup NFSv4 server in SUSE 10.1 Alpha 2
2. Install newpynfs
3. Run the pynfs testserver.py script
./testserver.py --maketree <hostname> all -v
        or
python testserver.py --maketree <hostname> all -v
4. The results will be store in out_last file
5. Redirect results to a text file
./showresults.py out_last > SUSE10.1-acl2.txt
6. The following test is failing 
SATT14   st_setattr.testChange                             : FAILURE
       change attribute not affected by SETATTR(mode)

Comment 1 Olaf Kirch 2005-12-12 10:33:54 UTC

Neil, could you track this one, please? Thanks!

Comment 2 Neil Brown 2005-12-12 23:04:35 UTC

This is, in my mind, a serious flaw in the NFSv4 spec, though we I raised it some
years ago I was totally unable to convince anyone :-(

Linux uses 'ctime' for the change attribute and on many filesystems (ext3 and reiser included) don't support a granularity better than 1second.  The filesystem
doesn't make it possible to do any better, and the NFSv4 spec doesn't make it 
possible to cope with that...

You could try with xfs or jfs and confirm they pass this test...

I'll bring it up on the nfsv4@linux-nfs mailing list...

Comment 3 Forgotten User b5BnQSUi71 2005-12-22 04:04:58 UTC

You are right, Neil. Unable to reproduce the problem with xfs

Comment 4 Ihno Krumreich 2006-04-24 12:24:15 UTC

Status of the bug?

Comment 5 Forgotten User b5BnQSUi71 2006-04-26 13:13:08 UTC

I think the discussion here didn't come to a conclusion yet.
http://linux-nfs.org/pipermail/nfsv4/2005-December/003052.html

Neil, Can we move this to LATER?

Comment 6 Neil Brown 2006-04-27 02:20:18 UTC

Yes, let's make it "LATER".

I think it is a real problem that needs fixing, but it just isn't on the top
of the list yet....

Comment 7 Stephan Kulow 2008-06-25 09:34:03 UTC

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

Comment 8 Stephan Kulow 2008-06-25 09:35:43 UTC

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

Comment 9 Stephan Kulow 2008-06-25 09:41:34 UTC

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

Comment 10 Stephan Kulow 2008-06-25 09:53:02 UTC

Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(