***: dfshjkl has quit IRC (Ping timeout: 255 seconds)
erratic has quit IRC (Client Quit)
shafire has quit IRC (Ping timeout: 252 seconds)
ant has quit IRC (Quit: Leaving)
ant has joined #arpnetworks
gizmoguy has quit IRC (Ping timeout: 240 seconds)
gizmoguy has joined #arpnetworks
jpalmer has quit IRC (Ping timeout: 256 seconds)
jpalmer has joined #arpnetworks
jpalmer has quit IRC (Ping timeout: 246 seconds)
jpalmer has joined #arpnetworks RandalSchwartz: kr24 in trouble?
getting DMA errors on my virtual disks
that's either noisy neighbor or RAID rebuild.
anyone else on 24? brycec: https://twitter.com/arpnetworks/status/680195111842529280 BryceBot: TWITTER: We're looking into issues with host kvr24 (Fri Dec 25 01:15:26 +0000 2015) brycec: And yeah I can connect, but not login over ssh to a VPS on 24 RandalSchwartz: shs
aha brycec: oh hey my ssh finally went through
but is dog slow -: brycec is waiting for "dmesg" do do *anything* RandalSchwartz: ugh brycec: Seems better at the moment
Nothing exciting in my dmesg, and loadavg wasn't high. RandalSchwartz: well that was weird.
so why was my VM showing DMA errors
looks like my server seems reasonable again ***: erratic has joined #arpnetworks up_the_irons: 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.
but load is going to be higher at the moment because the array is degraded (and thus, write cache is off) mercutio: it was rather on/off RandalSchwartz: thanks for the update mercutio: it's rebuilding now. ***: jlgaddis has quit IRC (Ping timeout: 255 seconds)
jlgaddis has joined #arpnetworks