Bug 7100 - File corruption with filesystems mounted from IBM AIX 4.2.1
File corruption with filesystems mounted from IBM AIX 4.2.1
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
6.1
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Michael K. Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-11-18 10:02 EST by Luca Giuzzi
Modified: 2008-05-01 11:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-08 09:53:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Luca Giuzzi 1999-11-18 10:02:25 EST
While compiling in a directory exported from an IBM AIX 4.2.1 server,
file corruption has been detected in a predictable way for the object
code generated by gcc. The problem does not present itself when
the directory is exported by a linux, Digital Unix (4.01E) or Solaris
(2.6+security fixes). Likewise, the problem is not visible when the
kernel being used is a 2.2.10.
It seems that this form of file corruption does not happen when simply
copying a file from the exported filesystem onto itself.
Comment 1 Cristian Gafton 2000-01-04 17:26:59 EST
Assigned to dledford
Comment 2 Stephen Tweedie 2000-02-08 09:53:59 EST
This sounds like a known AIX NFS server bug.  From memory, AIX cannot deal with
padded NFS packets, assuming that the NFS packet data length is equal to the IP
packet length.  See the report at

http://www.uwsg.indiana.edu/hypermail/linux/kernel/9911.0/0452.html

and the work-around at

http://www.uwsg.indiana.edu/hypermail/linux/kernel/9911.0/0549.html

There are a couple of NFS patches referenced at

http://www.uwsg.indiana.edu/hypermail/linux/kernel/9911.0/0498.html

but there is no guarantee that they will help.

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