Note that there are some explanatory texts on larger screens.

plurals
  1. POChecksum inconsistencies in reading large files within same server. Hardware issue symptoms?
    primarykey
    data
    text
    <p>I'm having checksums inconsistencies in one server, and would like to know your opinion and similar experiences you may have had.</p> <p>Every time I run the command </p> <p><code># md5sum MyBig.3GB.largeFile.bin</code> </p> <p>the checksum output is different. Even for this command: </p> <p><code># for i in {1..10} ; do time md5sum MyBig.3GB.largeFile.bin ;done</code> </p> <p>the subsequent checksum output is different, and the time taken to run each iteration is also very different and perhaps random, from 10 secs up to 3 minutes, which is the usual time based on I/O performance. </p> <p>The issue is not only with the 'md5sum' checksum, but also with 'cksum' and 'sha1sum'. Same inconsistent results. </p> <p>I have three twin servers, with exactly the same specs. Only one of them is showing this problem. The server is in the testing phase, no real end-users yet. Although you only see this behaviour when the server is stressed and put under heavy load. And this is important, you reboot the server and the problem disappears, until is pushed to its limits again, then it starts to show those symptoms. </p> <p>The server is an ASUS motherboard, Intel Xeon i7 CPU, 4x8GB kingston RAM, SATA controller Intel 8 Series/C220, 2x2TB Seagate ST2000DM in RAID-1 software, running CentOS 6.4 64bit.</p> <p>From my experience, this is a clear symptom of a hardware potential problem. However, the server owner (i'm just renting those servers) ran a memory test, and denies any hardware related issue. The server is brand new. The memory tests didn't show any memory problem.</p> <p>Now, this is the question to you all. What do you think? what could be the problem? have you had any similar issues in the past. </p> <p>Thanks.</p> <p>(Sorry for the long description) </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload