BTRFS scrub errors on docker volume

[Jaybau]

I ran a BTRFS scrub on the docker image/volume/file docker.img.

I received checksum errors, and the log provided the offending file path, presumably within the docker.img file.

How do I know which container has the problem, so I can connect to the container to fix the file?  Or where is this file with the error?

Bonus question: Are there instructions for creating a BTRFS snapshot of the docker.img volume so I can have BTRFS self-correct the errors in the future?

 

UUID:             f5d16644-b1de-4be0-be96-754d644a9601
Scrub started:    Wed Dec 20 14:35:19 2023
Status:           finished
Duration:         0:04:57
Total to scrub:   39.49GiB
Rate:             136.17MiB/s
Error summary:    csum=2
  Corrected:      0
  Uncorrectable:  0
  Unverified:     0

 

Dec 20 14:36:35 Tower kernel: BTRFS warning (device loop2): checksum error at logical 9904988160 on dev /dev/loop2, physical 10450247680, root 3978, inode 10459, offset 8192, length 4096, links 1 (path: usr/lib/python3.11/unittest/result.py)
Dec 20 14:36:35 Tower kernel: BTRFS warning (device loop2): checksum error at logical 9904988160 on dev /dev/loop2, physical 10450247680, root 3977, inode 10459, offset 8192, length 4096, links 1 (path: usr/lib/python3.11/unittest/result.py)
Dec 20 14:36:35 Tower kernel: BTRFS warning (device loop2): checksum error at logical 9904988160 on dev /dev/loop2, physical 10450247680, root 3976, inode 10459, offset 8192, length 4096, links 1 (path: usr/lib/python3.11/unittest/result.py)
Dec 20 14:36:35 Tower kernel: BTRFS warning (device loop2): checksum error at logical 9904988160 on dev /dev/loop2, physical 10450247680, root 3975, inode 10459, offset 8192, length 4096, links 1 (path: usr/lib/python3.11/unittest/result.py)
Dec 20 14:36:35 Tower kernel: BTRFS warning (device loop2): checksum error at logical 9904988160 on dev /dev/loop2, physical 10450247680, root 3974, inode 10459, offset 8192, length 4096, links 1 (path: usr/lib/python3.11/unittest/result.py)
Dec 20 14:36:35 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 7, gen 0
Dec 20 14:36:43 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 8, gen 0

 

Thank you.

tower-diagnostics-20231220-1444.zip

Edited December 21, 2023 by Jaybau

[itimpi]

It is normally easier to simply recreate the docker.img file and then reinstall your containers with their previous settings via Apps->Previous Apps.

[Jaybau]

1 hour ago, itimpi said:

It is normally easier to simply recreate the docker.img file and then reinstall your containers with their previous settings via Apps->Previous Apps.

 

Okay...I might have to do that.  I have a few custom dockers that I created via Portainer that don't make it quick/easy.  I may need to learn how to create custom containers the Unraid way.

 

Thank you.

[johnomaz]

On 12/20/2023 at 2:58 PM, itimpi said:

It is normally easier to simply recreate the docker.img file and then reinstall your containers with their previous settings via Apps->Previous Apps.

 Man, not often I find a great answer on the first link.  I had no idea that the Apps tab had the Previous Apps option.  My docker.img file decided to end itself today and I was just about to start installing them one by one from the appdata folders.  😊 🖖