1. How did these corrupted files look like from server end ?
2. As stated in the problem statement, "RHEL 4.5" doesn't have this issue but
it is not clear when the platform was moved back to RHEL 4.5, was the
server moved too ? What are the OSs running on server with and without
the problem ? What is server's filesystem (GFS, ext3, etc) ?
Intuitively, if file size and offset are correct but file contens were
partially filled with "NULL" characters, it normally implies the file
spaces are allocated but file contents are not there. We need to isolate
whether this is really a NFS client issue as stated or it is a server
(nfsd and/or filesystem) issue.
Few questions:
1. How did these corrupted files look like from server end ?
2. As stated in the problem statement, "RHEL 4.5" doesn't have this issue but
it is not clear when the platform was moved back to RHEL 4.5, was the
server moved too ? What are the OSs running on server with and without
the problem ? What is server's filesystem (GFS, ext3, etc) ?
Intuitively, if file size and offset are correct but file contens were
partially filled with "NULL" characters, it normally implies the file
spaces are allocated but file contents are not there. We need to isolate
whether this is really a NFS client issue as stated or it is a server
(nfsd and/or filesystem) issue.