NFS/NAS file corruption issue..

[Prashant Zanwar_4]

Hi,

I have a NFS mount, from filer NAS, which is equal on 2-servers.

I copy a jar file on this mount, on one of the server, which reflexes equally on other server..

File size and time stamp and inode shown are same here..

Strange thing is cksum is different, and jar tvf works on one one server where it is copies actually, but is not working on other server, it throws error,

Error in JAR file format. zip-style comment?

Other time message was different, it was corrupt...

I have nfs mount options:

nfs proto=tcp,rw,hard,intr,rsize=32768,wsize=32768,vers=3 0 0

Anyone faced it any time, or any ideas..

Please reply immediate as this is a live application which needs files..

Although servers are Linux, I have a question open there too, still would like to have you guys thoughts...I have a case open with EMC and LINUX too...

Thanks and regards

Prashant

[Steven E. Protter]

jar file is good?

After talking with Bill Hassell, I will transmit something he said. NFS if used in this context should be not share a lan with PC's and other devices that can set up storms and clog the lan.

Maybe vlan or private switch. Eliminate other factors.

If one machine causes corruption, I'd look at its NIC, cable and card. Maybe something is wrong there.

SEP

[Prashant Zanwar_4]

I have one more system happening this as mentioned above..

Thanks and regards
Prashant

[Prashant Zanwar_4]

It's just weired that same filer mount on a relative server is showing checksum different for same file...File is corrupt...
We have filer conncted over different subnet than public lan..
I run md5 on the file which returns different output on two nodes, inode information is same..similar is time stamp...
Thanks and regards

[Prashant Zanwar_4]

If I mount the filer with a different mount point, I get a good file!! in same path..

Thanks and regards
Prashant

[Prashant Zanwar_4]

this issue has a working solution now. Mainly this is a bug with Linux NFS. When the executable or jar which is open by some process, gets overwritten, it fails at one server as txt is open in memory. But file gets written. So one server has correct while other server not. We r working with Linux on this..
Thanks and regards
Prashant