Bug 33357 - corrupted executable file on NFS volume
Summary: corrupted executable file on NFS volume
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.0
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-27 07:04 UTC by vincent gueno
Modified: 2007-04-18 16:32 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2003-06-06 00:08:51 UTC


Attachments (Terms of Use)

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
2.
3.

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



Note You need to log in before you can comment on or make changes to this bug.