(SOLVED) Version 6.8.3 - BTRFS info (device loop2): forced readonly

[cheesemarathon]

Hi all

I was having some issues with docker images failing to pull. So I rebooted my unRAID machine to see if that would fix things and now the docker service failed to start and loop2 is in read-only mode. I have done nothing after tuning the machine back on and seeing the error. Any help would be much appreciated, don't want to lose any data! Syslog attached.

derek-diagnostics-20200408-1415.zip

Edited April 9, 2020 by cheesemarathon

[JorgeB]

Cache is completly full, free up some space.

[cheesemarathon]

Perfect, thank you! Looking at it now, that was bloody obvious!

[cheesemarathon]

2 hours ago, johnnie.black said:

Cache is completly full, free up some space.

Ok, still isn't quite fixed. I can start up fine. Managed to remove some unused containers so docker service starts now. 30GB free on cache disk, but I still can't pull an image. Puts the cache disk into read only.

 

Apr 8 16:53:57 Derek kernel: BTRFS error (device loop2): bad tree block start, want 168460288 have 0
Apr 8 16:53:57 Derek kernel: BTRFS error (device loop2): bad tree block start, want 168460288 have 0
Apr 8 16:53:57 Derek kernel: BTRFS: error (device loop2) in btrfs_run_delayed_refs:2935: errno=-5 IO failure
Apr 8 16:53:57 Derek kernel: BTRFS info (device loop2): forced readonly

 

derek-diagnostics-20200408-1713.zip

Edited April 8, 2020 by cheesemarathon

[JorgeB]

Due to cache running out of space the docker image got corrupted, but it's easy to re-create.

[cheesemarathon]

18 hours ago, johnnie.black said:

Due to cache running out of space the docker image got corrupted, but it's easy to re-create.

Perfect! Thank you