Error in Syslog - BTRFS critical (device loop0): corrupt leaf, bad key order

[ltoolio]

Hey all,

Had a prior issue where I was getting some errors on one of my drives, which ended up being a bad seating of a cable:

https://lime-technology.com/forum/index.php?topic=51083.msg490140#msg490140

 

That has since been rectified, but I now have the following errors showing up in my syslog:

 

Aug 20 14:28:17 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:17 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:18 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:18 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:18 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:18 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:18 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:18 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:18 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:18 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:18 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:18 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:19 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:19 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:19 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:19 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:19 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:19 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:19 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:19 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:19 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:19 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:20 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:20 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:20 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:20 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:20 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8
Aug 20 14:28:20 Tower kernel: BTRFS critical (device loop0): corrupt leaf, bad key order: block=119750656,root=1, slot=8

 

I'm presuming I need to do a FS scan/repair, but can't seem to find a method to do it properly (either here or via a google search).

 

Any pointers?

 

Thanks!

[Squid]

Its actually the docker.img reporting that error. (loop0)  You can try scrubbing the docker.img, but you're probably going to have less aggravation just deleting the docker.img file and recreating it, and then adding your applications again via CA's previous apps section.  You won't need to adjust any templates or anything.  After the downloads are finished, it'll be like nothing happened.

[ltoolio]

adding your applications again via CA's previous apps section.

 

Thanks, but what is the Previous Apps section?

 

BTW - beer on the way

[John_M]

Top row, third button from the left.

[Squid]

Just looked at your syslog, and you don't have CA installed (why not?    )  (You can get it from the link in my sig)

 

If you don't want to install it then after you delete and recreate your docker.img then from the docker tab, add a container, and select one of the MY templates from the template drop down.

[Squid]

BTW - beer on the way

Thanks alot... It won't go to waste 

[ltoolio]

Just looked at your syslog, and you don't have CA installed (why not?    )  (You can get it from the link in my sig)

 

Wasn't even aware of it....installing it now.

 

One question about it, and a big reason I don't want to completely wipe my docker.img file - does it retain the data within the dockers?  I've got a bunch of stuff / config within my mariadb, and the thought of recreating it isn't overly appealing.

[ltoolio]

BTW - beer on the way

Thanks alot... It won't go to waste 

 

I'm having one right now, so cheers

[lionelhutz]

Just looked at your syslog, and you don't have CA installed (why not?    )  (You can get it from the link in my sig)

 

Wasn't even aware of it....installing it now.

 

One question about it, and a big reason I don't want to completely wipe my docker.img file - does it retain the data within the dockers?  I've got a bunch of stuff / config within my mariadb, and the thought of recreating it isn't overly appealing.

 

No, all the config stuff is stored in the appdata directory unless you manually edited the docker after installing it.

[BRiT]

You shouldn't have data stored inside your docker image file anyways, just program images. For a database docker, the database files should be external and use mapped volumes.