Bad ECC RAM is still bad RAM. ECC can only correct a single bit flip in register. 2 bit flips and it's all toast.<br><br>It does sound like Samba managed to totally corrupt itself and the hang later may have been related to the system thrashing ram around. The filesystem definitions are kernel space so samba has to access that to function. Just be restarting samba is a pretty good indication that it was memory associated with the samba process. The aggressive caching of the kernel will amplify a bad memory situation. Restarting samba will cause teh samba caching to also restart and that may have overwritten the bad data portion which was related to the filesystem management area.<br>
<br><div class="gmail_quote">On Thu, Dec 10, 2009 at 3:41 PM, Jeff Hubbs <span dir="ltr"><<a href="mailto:jhubbslist@att.net">jhubbslist@att.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
How does it factor in that it's ECC RAM? There are four 2GiB DIMMs, one<br>
in every fourth of sixteen slots.<br>
<div class="im"><br>
Jim Kinney wrote:<br>
> time to run memtest<br>
><br>
> On Thu, Dec 10, 2009 at 2:34 PM, Jeff Hubbs <<a href="mailto:jhubbslist@att.net">jhubbslist@att.net</a><br>
</div><div><div></div><div class="h5">> <mailto:<a href="mailto:jhubbslist@att.net">jhubbslist@att.net</a>>> wrote:<br>
><br>
> Troubling behavior under Samba 3.0.33: when a certain win2K user<br>
> opened<br>
> an excel file and saved it, it showed to be corrupted on the next<br>
> open.<br>
> If same user simply dragged a file down from the Samba share and<br>
> dragged<br>
> it back, the file had changed (shown by md5sum) even if the size were<br>
> the same. I was troubleshooting this when a few hours later, all<br>
> authentication and share access hung up. I shelled into the<br>
> server and<br>
> a ps aux would only get so far and hang w/o completing. Top would not<br>
> start - no output, just hang. Restarted samba; everything started<br>
> working again and the file corruption on share went away (by "went<br>
> away", I mean that the files weren't being changed anymore when<br>
> written<br>
> back to the server). What the hey??<br>
><br>
> FWIW, the server had been up for 91 days in a 150-200 user office. I<br>
> don't think Samba had been restarted in that time.<br>
><br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>-- <br>James P. Kinney III<br>Actively in pursuit of Life, Liberty and Happiness <br><br>