Hide Forgot
When using Red Hat Linux 6.0 as an NFS client to a host running Solaris 2.5.1, I've seen file corruption. The specific trigger is running ld to link executables -- the output file is messed up with some regularity. I do not know which side of the NFS connection is to blame. It could be a bug in the Solaris server. I have not yet seen the problem with servers running Solaris 2.6. When I look at the bytes that are wrong it looks like some byte or word swapping has occurred. Here is some output of "cmp -l" showing some of the differences between a good file and a corrupted one: 36525 33 0 36527 0 33 36529 1 0 36531 0 1 36533 6 0 36535 0 6 36541 100 0 36543 0 100 36545 140 0 36546 42 0 36547 0 140 36548 0 42 36557 20 0 36559 0 20 36565 41 0 36567 0 41 36569 11 0 36571 0 11 36581 314 0 36582 224 0 36583 0 314 36584 0 224 36585 260 0 36586 23 0 36587 0 260 36588 0 23 36589 14 0 36591 0 14 36593 1 0 36595 0 1 36597 4 0 36599 0 4 36601 10 0 36603 0 10 36605 53 0 36607 0 53 ------- Additional Comments From 06/29/99 12:36 ------- We have a large amount of experience with Red Hat 5.1 and the bug was definitely not present in that release. It only appeared after the 6.0 upgrade.
This looks to be a duplicate of bug# 3758, which is a known bug with Solaris, so I do not think that linux is to blame on this one. Reopen this bug if the Solaris fix does not remedy the problem. *** This bug has been marked as a duplicate of 3758 ***