Bug 68867

Summary: NFS locking does not work properly
Product: [Retired] Red Hat Linux Reporter: dMan <dariuszs>
Component: nfs-utilsAssignee: Pete Zaitcev <zaitcev>
Status: CLOSED WORKSFORME QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-05-13 17:37:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description dMan 2002-07-15 15:09:35 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
Kernel 2.4.9-34: When creating files thru programs I got the message "User does 
not have appropriate authorization level for file abcfile.dat" and the programs 
bombs, yet if I go to the directory where I wanted to create that file, a 
file "abcfile.dat.lck" is created with 0 bytes in size. When I turn off 
locking "-o nolock" on NFS mount then I don't have this problem or if I use 
Kernel 2.4.7-10, or different flavor of linux, for example SuSe.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.mount -o rsize=8192,wsize=8192 WINPC:C/linuxshare /usr/local/win
2.create and run program that creates file (use C++, Java or Perl), that 
actually requests a file lock ("touch" does not do that) to write a file

	

Actual Results:  You'll see compiler error "User does not have appropriate 
authorization level for file abcfile.dat". You'll see also 
that "abcfile.dat.lck" file was created wich is 0 bytes in size.

Expected Results:  File "abcfile.dat" should be created with size other than 0 
bytes.

Additional info:

Comment 1 Pete Zaitcev 2002-09-10 22:25:46 UTC
Please attach strace logs of the program in question.
The best would be to collect strace output at 2.4.7-10 in a separate file.
PLEASE DO NOT DROP THEM INTO THE COMMENTS BOX of the bug.