Bug 33357

Summary: corrupted executable file on NFS volume
Product: [Retired] Red Hat Linux Reporter: vincent gueno <vincent.gueno>
Component: kernelAssignee: Michael K. Johnson <johnsonm>
Status: CLOSED WORKSFORME QA Contact: David Lawrence <dkl>
Severity: high Docs Contact:
Priority: medium    
Version: 7.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-06-06 00:08:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description vincent gueno 2001-03-27 07:04:02 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.5 [en] (X11; I; SunOS 5.5.1 sun4u)

When I generate an executable file with gcc on NFS volume, then executable
file is corrupted (segmentation fault at execution) .To solve this problem,
I have to generate executable
  file on /tmp then move it to NFS volume. Is there a patch to solve such a
problem ? (gcc version 2.96 20000731 (Red Hat Linux 7.0))

Reproducible: Sometimes
Steps to Reproduce:
1.Link a program on NFS volume

Comment 1 Jakub Jelinek 2001-03-30 08:06:00 UTC
If gcc creates the program just fine on local file system, then the bug is
either in the NFS client, or NFS server but not in gcc. gcc (well, it is
more probably as or ld, because if assembly was corrupted, it would most probably
not assemble) simply writes a file, it does not check what filesystem it is on.
You haven't mentioned which NFS server you're using.

Comment 2 Alan Cox 2003-06-06 00:08:51 UTC
Solaris and IBM server patches were released for this