search for: reeeeeallli

On Feb 3, 2016, at 16:13, Warren Young wrote: > A dying hard disk can do it. HDDs try to silently paper over I/O errors, but what they can?t hide is the time it takes to do this. If your HDD is constantly correcting errors at the oxide layer, it will be reeeeeallly sllllow. > > You can try running SMART tests on it, though that?s not guaranteed to show the problem. Well, it?s not ?a?

I?m running CentOS 6.7 on my build servers, and on one of the servers the builds are taking almost an order of magnitude longer than usual. There are no runaway processes and there is plenty of free memory. So I suspected that file I/O might be slow, and sure enough, that appears to be the case. I ran a simple dd test and compared the results to a ?normal? build server (412 MB/s vs. 31.7 MB/s).

On Feb 3, 2016, at 1:30 PM, Alfred von Campe <alfred at von-campe.com> wrote: > > I suspected that file I/O might be slow, and sure enough, that appears to be the case?.What could cause this A dying hard disk can do it. HDDs try to silently paper over I/O errors, but what they can?t hide is the time it takes to do this. If your HDD is constantly correcting errors at the oxide

On Feb 3, 2016, at 2:26 PM, Alfred von Campe <alfred at von-campe.com> wrote: > > On Feb 3, 2016, at 16:13, Warren Young wrote: > >> A dying hard disk can do it. HDDs try to silently paper over I/O errors, but what they can?t hide is the time it takes to do this. If your HDD is constantly correcting errors at the oxide layer, it will be reeeeeallly sllllow. >>