Bug 28589 - NFS file corruptions in object files
NFS file corruptions in object files
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
Brock Organ
http://hem.fyristorg.com/pof1/work/
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-02-21 07:12 EST by Per Frykenvall
Modified: 2007-04-18 12:31 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-02-21 07:12:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Per Frykenvall 2001-02-21 07:12:45 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; m18) Gecko/20010131
Netscape6/6.01


I have problems with object files that are corrupted. I work on my linux
machine in a directory that resides on an NFS mounted remote file system. I
compile all C files in that directory into object files. Sometimes when I
try to link the object files I get an error from ld.


Reproducible: Sometimes
Steps to Reproduce:
1. Have a copy of a C source on a local dir and an NFS dir
2. Compile in both dirs
3. Compare resulting object files
Please have a look at the URL http://hem.fyristorg.com/pof1/work/

	

Actual Results:  The object file on the NFS dir sometimes is not linkable,
ld says:
"xxx.o: file not recognized: Memory exhausted"
The object file differ from the reference object generated locally.

Expected Results:  The object file should not be corrupted, of course.

The linux machine runs Red Hat Linux release 7.0 (Guinness), Kernel
2.2.16-22 on an i686. The machine is a Compaq 400MHz Intel Pentium II with
64 MB RAM.

The NFS server is an IBM RS/6000 F50 machine with AIX 4.3.1.

NFS v2 is used.
Comment 1 Michael K. Johnson 2001-02-21 14:06:21 EST
I think that this is a known bug in the AIX nfs server, and that an
update for AIX is available to solve it.

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