BTRFS Errors - Should be aligned to 4096

[thestraycat]

Can anyone advise why i might be recieving hese BTRFS Critical errors? And potentially how to fix them?

 

Sep 21 09:48:02 MediaServer avahi-daemon[6041]: Joining mDNS multicast group on interface veth067bcf5.IPv6 with address fe80::b401:81ff:fe0d:14c3.
Sep 21 09:48:02 MediaServer avahi-daemon[6041]: New relevant interface veth067bcf5.IPv6 for mDNS.
Sep 21 09:48:02 MediaServer avahi-daemon[6041]: Registering new address record for fe80::b401:81ff:fe0d:14c3 on veth067bcf5.*.
Sep 21 09:53:45 MediaServer kernel: BTRFS critical (device loop2): corrupt node: root=13186 block=9007972352 slot=65, unaligned pointer, have 119556632994638117 should be aligned to 4096
Sep 21 09:53:45 MediaServer kernel: BTRFS critical (device loop2): corrupt node: root=13186 block=9007972352 slot=65, unaligned pointer, have 119556632994638117 should be aligned to 4096
Sep 21 09:53:55 MediaServer kernel: BTRFS critical (device loop2): corrupt node: root=13186 block=9007972352 slot=65, unaligned pointer, have 119556632994638117 should be aligned to 4096
Sep 21 09:53:55 MediaServer kernel: BTRFS critical (device loop2): corrupt node: root=13186 block=9007972352 slot=65, unaligned pointer, have 119556632994638117 should be aligned to 4096

[JorgeB]

If loop2 is the docker image, and if you're not sure post your diags, just delete and recreate it.

[thestraycat]

Thanks Johnnie - I'm creating the diags as we speak... Will post in a few minutes... Your right it may well be..

[thestraycat]

Here we go.

 

mediaserver-diagnostics-20180921-1145.zip

[JorgeB]

Yes, it's the docker image, delete and recreate.

[trurl]

And in case you don't know, you can get all your dockers back just like they were at Apps - Previous Apps.

[thestraycat]

Thanks guys - I was sure the last time i did this my container all persisted and recreated when they were restarted without having to readd them... I have round 30 so my only fear is certain configs may be lost if theyve been badly created and settings etc. Are resident within the container image potentially.

[trurl]

Just now, thestraycat said:

Thanks guys - I was sure the last time i did this my container all persisted and recreated when they were restarted without having to readd them... I have round 30 so my only fear is certain configs may be lost if theyve been badly created and settings etc. Are resident within the container image potentially.

No, you must have misremembered.

 

It's your docker configs that won't be lost since they are on flash. And any configuration within the applications themselves will be in appdata. It is the dockers themselves that will be gone and will have to be readded as I mentioned. Since the configs are on flash, Community Applications can readd them with the same configuration as before using the Previous Apps feature. And when started, they will pick up just as before because their appdata is still in place.

[thestraycat]

I agree. It's more about obscure containers I've added manually or that arnt maintained as well where the config hasnt been outputted to appdata and is held locally inside the container due to bad container provisioning or when I've had to exec into the shell of the container itself and ammend a value.