February 15Feb 15 Would be greatful if someone could please take a look at my logs. Thought this was an issue to do with running out of space but has since happened with lots of free space. Hoping someone more knowledgeable can help me out here. Basically every week this seems to happen and I need to delete the docker Img and re-download all dockers. It's getting pretty old now. Thanks! camraid-diagnostics-20260216-0704.zip
February 15Feb 15 Were you filling up docker.img? 90G should be 3x larger than needed for most.An application writing to a path that isn't mapped is the usual cause for filling.
February 15Feb 15 Author I don't think it was filling beyond about 30g. I did increase it to 90 at one point just because I noticed it close or to try solve this issue I'm having. Will have to monitor.
February 15Feb 15 Any idea why your syslog is being spammed with ntpd entries?Post a screenshot of Date and Time Settings.
February 16Feb 16 Feb 16 01:28:29 CamRaid kernel: critical space allocation error, dev loop4, sector 1481120 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2Feb 16 01:28:29 CamRaid kernel: critical space allocation error, dev loop4, sector 3578272 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2Feb 16 01:28:29 CamRaid kernel: critical space allocation error, dev loop4, sector 1481152 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2Feb 16 01:28:29 CamRaid kernel: critical space allocation error, dev loop4, sector 3578304 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2Feb 16 01:28:29 CamRaid kernel: critical space allocation error, dev loop4, sector 1481184 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2Feb 16 01:28:29 CamRaid kernel: critical space allocation error, dev loop4, sector 3578336 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2Feb 16 01:28:29 CamRaid kernel: critical space allocation error, dev loop4, sector 1481216 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2Feb 16 01:28:29 CamRaid kernel: critical space allocation error, dev loop4, sector 3578368 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2Feb 16 01:28:29 CamRaid kernel: critical space allocation error, dev loop4, sector 1481248 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2Feb 16 01:28:29 CamRaid kernel: critical space allocation error, dev loop4, sector 3578400 op 0x1:(WRITE) flags 0x101000 phys_seg 4 prio class 2Feb 16 01:28:32 CamRaid emhttpd: read SMART /dev/sddFeb 16 01:28:33 CamRaid ntpd[1859]: Soliciting pool server 76.223.54.146Feb 16 01:28:53 CamRaid kernel: BTRFS error (device loop4 state A): Transaction aborted (error -5)Feb 16 01:28:53 CamRaid kernel: BTRFS: error (device loop4 state A) in do_free_extent_accounting:2983: errno=-5 IO failureFeb 16 01:28:53 CamRaid kernel: BTRFS info (device loop4 state EA): forced readonlyFeb 16 01:28:53 CamRaid kernel: BTRFS error (device loop4 state EA): failed to run delayed ref for logical 3658858496 num_bytes 4096 type 178 action 2 ref_mod 1: -5Feb 16 01:28:53 CamRaid kernel: BTRFS: error (device loop4 state EA) in btrfs_run_delayed_refs:2215: errno=-5 IO failureDocker image is running out of space and going read-only
February 16Feb 16 20 hours ago, trurl said:An application writing to a path that isn't mapped is the usual cause for filling.Reboot, do the usual recreate docker.img and reinstall Previous Apps.Then post new diagnostics and the results from CONTAINER SIZE on the DOCKER page.
February 18Feb 18 Author On 2/17/2026 at 4:33 AM, trurl said:Reboot, do the usual recreate docker.img and reinstall Previous Apps.Then post new diagnostics and the results from CONTAINER SIZE on the DOCKER page.OK. I didn't reboot, but rebuilt my dockers 2 days ago. Attached logs. Sorry been super busy. Container size only 2.82GBOn 2/16/2026 at 9:19 AM, trurl said:Any idea why your syslog is being spammed with ntpd entries?Post a screenshot of Date and Time Settings.I had a custom ntp server. From memory had issues with time. Without I see a 4min difference vs local time. Odd. Have removed for now.camraid-diagnostics-20260219-0747.zip Edited February 18Feb 18 by Camo200sx
February 19Feb 19 Filesystem Size Used Avail Use% Mounted on /dev/loop5 90G 27G 64G 30% /var/lib/docker
February 19Feb 19 What do you get from this command line now that it has been running for a while?df -h /dev/loop5
March 4Mar 4 Author On 2/19/2026 at 2:17 PM, trurl said:What do you get from this command line now that it has been running for a while?df -h /dev/loop5I'm back. I ended up disabling the VM backup plugin. I think it was causing the cache drive to become full and everything to grind to a halt. Filesystem Size Used Avail Use% Mounted on/dev/loop5 90G 26G 65G 29% /var/lib/docker
March 4Mar 4 docker.img usage not growing. Looks like you would have plenty to spare if you decreased it from 90G to 40G
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.