[01:47] *** erratic has joined #arpnetworks [01:47] *** dfshjkl has quit IRC (Ping timeout: 255 seconds) [01:48] *** erratic has quit IRC (Client Quit) [02:20] *** shafire has quit IRC (Ping timeout: 252 seconds) [07:02] *** ant has quit IRC (Quit: Leaving) [07:06] *** ant has joined #arpnetworks [09:48] *** gizmoguy has quit IRC (Ping timeout: 240 seconds) [09:48] *** gizmoguy has joined #arpnetworks [16:39] *** jpalmer has quit IRC (Ping timeout: 256 seconds) [16:44] *** jpalmer has joined #arpnetworks [16:53] *** jpalmer has quit IRC (Ping timeout: 246 seconds) [17:03] *** jpalmer has joined #arpnetworks [17:16] kr24 in trouble? [17:16] getting DMA errors on my virtual disks [17:17] that's either noisy neighbor or RAID rebuild. [17:17] anyone else on 24? [17:22] https://twitter.com/arpnetworks/status/680195111842529280 [17:22] TWITTER: We're looking into issues with host kvr24 (Fri Dec 25 01:15:26 +0000 2015) [17:22] And yeah I can connect, but not login over ssh to a VPS on 24 [17:23] shs [17:23] aha [17:24] oh hey my ssh finally went through [17:24] but is dog slow [17:24] * brycec is waiting for "dmesg" do do *anything* [17:28] ugh [17:42] Seems better at the moment [17:42] Nothing exciting in my dmesg, and loadavg wasn't high. [18:00] well that was weird. [18:00] so why was my VM showing DMA errors [18:27] looks like my server seems reasonable again [18:33] *** erratic has joined #arpnetworks [18:35] RandalSchwartz: long story short, failing drive was not getting kicked out of the RAID, and we were seeing horrible iowait. After identifying such drive, we force failed it, and things are looking better. We're also in the processing of replacing that drive as I type this. [18:36] but load is going to be higher at the moment because the array is degraded (and thus, write cache is off) [18:42] it was rather on/off [18:48] thanks for the update [18:57] it's rebuilding now. [21:12] *** jlgaddis has quit IRC (Ping timeout: 255 seconds) [21:13] *** jlgaddis has joined #arpnetworks