Formatted cache drive from BTRFS to XFS still getting BTRFS errors

Hello

I upgraded to a new larger cache drive and it automatically got formatted to BTRFS, I figured I would give it a go and transferred all of my apps etc over to is. When writing data to the cache drive I was getting a lot of error messaged in the log pertaining to BTRFS errors so I figured I would switch to XFS. I transferred my data off, reformatted to XFS and transferred all of the data back, I am still getting BTRFS errors, things seem fine but I would like to figure out the root of this and if there is a fix for it.  The errors are along the lines of this and I have no drives that are BTRFS in my system anymore:

Feb 19 20:36:26 Tower kernel: BTRFS error (device loop1): bad fsid on block 20987904

Feb 19 20:36:26 Tower kernel: BTRFS error (device loop1): bad fsid on block 20987904

Feb 19 20:36:26 Tower kernel: BTRFS error (device loop1): failed to read chunk root

Feb 19 20:36:26 Tower kernel: BTRFS error (device loop1): open_ctree failed

Feb 19 20:36:26 Tower root: mount: wrong fs type, bad option, bad superblock on /dev/loop1,

Feb 19 20:36:26 Tower root:        missing codepage or helper program, or other error

Feb 19 20:36:26 Tower root:

Feb 19 20:36:26 Tower root:        In some cases useful info is found in syslog - try

Feb 19 20:36:26 Tower root:        dmesg | tail or so.

Feb 19 20:36:26 Tower root: mount error

Hello

 

I upgraded to a new larger cache drive and it automatically got formatted to BTRFS, I figured I would give it a go and transferred all of my apps etc over to is. When writing data to the cache drive I was getting a lot of error messaged in the log pertaining to BTRFS errors so I figured I would switch to XFS. I transferred my data off, reformatted to XFS and transferred all of the data back, I am still getting BTRFS errors, things seem fine but I would like to figure out the root of this and if there is a fix for it.  The errors are along the lines of this and I have no drives that are BTRFS in my system anymore:

 

Feb 19 20:36:26 Tower kernel: BTRFS error (device loop1): bad fsid on block 20987904

Feb 19 20:36:26 Tower kernel: BTRFS error (device loop1): bad fsid on block 20987904

Feb 19 20:36:26 Tower kernel: BTRFS error (device loop1): failed to read chunk root

Feb 19 20:36:26 Tower kernel: BTRFS error (device loop1): open_ctree failed

Feb 19 20:36:26 Tower root: mount: wrong fs type, bad option, bad superblock on /dev/loop1,

Feb 19 20:36:26 Tower root:        missing codepage or helper program, or other error

Feb 19 20:36:26 Tower root:

Feb 19 20:36:26 Tower root:        In some cases useful info is found in syslog - try

Feb 19 20:36:26 Tower root:        dmesg | tail or so.

Feb 19 20:36:26 Tower root: mount error

However, I'm not the real guy to ask here on what the consequences are of stopping the VM service and then deleting the libvirt.img file  (nor on the btrfs command to run to fix the image otherwise).

And unfortunately, the forum will be going into a read-only mode in a couple of hours, so you might have to wait until tomorrow for a definitive answer.

Ok thanks for the info, I'm going to delete my docker and try and create a new image and see.

I will report back.

Cheers

I tried to delete my docker and recreate it but still getting errors as well getting a bunch of other errors that are concerning, wondering if I am having motherboard issues. Its weird that there are errors relating to BTRFS when the cache was reformatted to XFS. The error below causes my cache drive to show no directories on it, shows normal on the main page but click on the directory and it shows nothing is on it. 

syslog-4.txt

Sorry this is the start of the error I meant. 

Feb 21 19:19:36 Tower kernel: blk_update_request: I/O error, dev sdh, sector 1026147647
Feb 21 19:19:36 Tower kernel: XFS (sdh1): metadata I/O error: block 0x3d29c4ff ("xlog_iodone") error 5 numblks 64
Feb 21 19:19:36 Tower kernel: XFS (sdh1): xfs_do_force_shutdown(0x2) called from line 1200 of file fs/xfs/xfs_log.c.  Return address = 0xffffffff812b37d1
Feb 21 19:19:36 Tower kernel: XFS (sdh1): Log I/O Error Detected.  Shutting down filesystem
Feb 21 19:19:36 Tower kernel: XFS (sdh1): Please umount the filesystem and rectify the problem(s)
Feb 21 19:19:36 Tower kernel: sd 7:0:0:0: [sdh] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Feb 21 19:19:36 Tower kernel: sd 7:0:0:0: [sdh] tag#7 CDB: opcode=0x2a 2a 00 01 ba 3c 98 00 00 10 00
Feb 21 19:19:36 Tower kernel: blk_update_request: I/O error, dev sdh, sector 28982424
Feb 21 19:19:36 Tower kernel: sdh: detected capacity change from 1050214588416 to 0
Feb 21 19:19:36 Tower kernel: Buffer I/O error on dev sdh1, logical block 3622795, lost async page write
Feb 21 19:19:36 Tower kernel: Buffer I/O error on dev sdh1, logical block 3622796, lost async page write
Feb 21 19:25:28 Tower kernel: blk_update_request: I/O error, dev loop0, sector 175584
Feb 21 19:25:28 Tower kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 1, flush 0, corrupt 0, gen 0
Feb 21 19:25:28 Tower kernel: blk_update_request: I/O error, dev loop0, sector 2272736
Feb 21 19:25:28 Tower kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0

First error looks like a hardware issue (bad cache device or bad cable/controller), it dropped offline, so all the other errors are related, including the btrfs errors because the docker image is not accessible anymore.