I just got done upgrading all of the drives in my system with bigger disks.  After replacing them all one at a time (and adding a second parity drive), I upgraded my old 137gb with a 1tb ssd.   I followed the directions to do so (shut down/disable vms and docker, change share settings, run mover, etc).  When all was said and done, the new drive in, and everything moved back everything was working.  My vms and docker containers loaded correctly, all was good in the world.  Or so I thought.  As I was just doing my due diligenct and checking everything, I found something in my logs.  This is CONSTANT, happening twice every 2-4 seconds.  Im wondering if it has any effect on the speed of my system.  Here's a snap of the logs:

 

Mar 26 22:15:08 Tower kernel: BTRFS warning (device loop2): csum failed root 2458 ino 9812 off 159744 csum 0x9ed483a8 expected csum 0x656104ef mirror 1
Mar 26 22:15:08 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 305211, gen 0
Mar 26 22:15:08 Tower kernel: BTRFS warning (device loop2): csum failed root 2458 ino 9812 off 159744 csum 0x9ed483a8 expected csum 0x656104ef mirror 1
Mar 26 22:15:08 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 305212, gen 0
Mar 26 22:15:12 Tower kernel: BTRFS warning (device loop2): csum failed root 2458 ino 9812 off 159744 csum 0x9ed483a8 expected csum 0x656104ef mirror 1
Mar 26 22:15:12 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 305213, gen 0
Mar 26 22:15:12 Tower kernel: BTRFS warning (device loop2): csum failed root 2458 ino 9812 off 159744 csum 0x9ed483a8 expected csum 0x656104ef mirror 1
Mar 26 22:15:12 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 305214, gen 0
Mar 26 22:15:15 Tower kernel: BTRFS warning (device loop2): csum failed root 2458 ino 9812 off 159744 csum 0x9ed483a8 expected csum 0x656104ef mirror 1
Mar 26 22:15:15 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 305215, gen 0
Mar 26 22:15:15 Tower kernel: BTRFS warning (device loop2): csum failed root 2458 ino 9812 off 159744 csum 0x9ed483a8 expected csum 0x656104ef mirror 1
Mar 26 22:15:15 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 305216, gen 0
Mar 26 22:15:19 Tower kernel: BTRFS warning (device loop2): csum failed root 2458 ino 9812 off 159744 csum 0x9ed483a8 expected csum 0x656104ef mirror 1
Mar 26 22:15:19 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 305217, gen 0

 

In the meantime, I'm only using about 41gb on the cache drive (the only drive that is btrfs) and it shows 0 errors on the "main" screen.

 

My ram is NOT overclocked.  I saw that posted as I was searching for an answer.  While I did just upgrade my ram, it was the SAME clock speed as the old RAM just higher capacity and I did not change it.  My system has been up for years.  Over the past 2 weeks I upgraded the ram to max capacity of my host, and then upgraded each of my drives.

 

But, the issue only seems to be with the btrfs cache drive, at least thats what I see in the logs.

 

Ideas?  I could sure use some!

 

Thanks!

 

 

 

Ok, so disregard.  I did MORE searching and found a thread that pointed out that (device loop2) was most probably pointing to my docker.img having issues.  So i stopped docker support, deleted the image, and re-enabled docker support so it would re-create the img.  

 

And that did the trick!  No more btrfs errors.   Hope this post helps someone else.