January 10, 201511 yr root@localhost:# /usr/bin/docker rmi 5df711ae9559 Error response from daemon: open /var/lib/docker/repositories-btrfs: read-only file system 2015/01/10 09:26:07 Error: failed to remove one or more images The command failed.
January 10, 201511 yr You likely ran out of space inside your docker.img file and BTRFS shat the bed as it died corrupting everything or if you still had space somehow else BTRFS shat the bed and corrupted itself. I have not seen anyone every recover from a BTRFS corruption ever. The scrub button and command on the docker page never seems to help. BTRFS is proving itself to be quit unreliable and immature as far as file systems go. You will likely need to delete your docker.img file, and recreate it larger, and then read all the docker images you had setup before. Maybe it really would be better if unraid docker wasn't forced to use BTRFS or a loop back image and instead just used normal files on the cache drive whatever filesystem you chose.
January 10, 201511 yr Author Thanks for the reply, the docker.img size is 20 GB. I installed everything (picture attached) is very small relative to the size 20 gb.
January 10, 201511 yr The log still says that the docker.img is read-only. You can either run the scrub on it (the button should be just below where your screenschot ended) or delete docker.img and re-create it. Personally, this only happened to me once, and rather runnning scrub on it (which BRit states may or may not do anything), I just deleted docker.img and recreated it, and let the system redownload everything. Hopefully all of your appdata isn't stored within the container itself, so the process should be painless. As an aside, the only time this ever happened was when my cache drive was formatted as BTRFS. Since LT has gone with the loopback device, the cache drive's file system doesn't matter. I switched mine to XFS and have never had a problem since
January 10, 201511 yr Thanks for the reply, the docker.img size is 20 GB. I installed everything (picture attached) is very small relative to the size 20 gb. Those current image sizes may be small, but if you used any of the auto-update features of the containers then you likely chewed through the 20GB of space.
January 10, 201511 yr Author It seems there is no choice del the file and reinstall docker.img btrfs scrub start /var/lib/docker -B -R -d 2>&1 ERROR: scrubbing /var/lib/docker failed for device id 1 (Read-only file system) scrub device /dev/loop8 (id 1) canceled scrub started at Sat Jan 10 17:51:20 2015 and was aborted after 0 seconds data_extents_scrubbed: 0 tree_extents_scrubbed: 0 data_bytes_scrubbed: 0 tree_bytes_scrubbed: 0 read_errors: 0 csum_errors: 0 verify_errors: 0 no_csum: 0 csum_discards: 0 super_errors: 0 malloc_errors: 0 uncorrectable_errors: 0 unverified_errors: 0 corrected_errors: 0 last_physical: 0
January 10, 201511 yr You could always give scrub a shot and not abort the process. But it could take quite a while to complete. Just don't close the pop up window
January 10, 201511 yr You could always give scrub a shot and not abort the process. But it could take quite a while to complete. Just don't close the pop up window Looks like it aborted itself because of it being a read-only filesystem.
Archived
This topic is now archived and is closed to further replies.