msnz Posted March 13, 2021 Share Posted March 13, 2021 (edited) Hi there, Some help would be greatly appreciated - I'm unable to start the Docker service. Errors in logs relating to docker.img. I've tried recreating the docker.img as per advice elsewhere on this forum, but it doesn't seem to be able to create the new file. Upgrade to 6.9.1 yesterday - not sure if that's relevant. Have run a filesystem check on the cache drive and all appears ok. I get a out of space error if I run cp docker.img docker.img.20210313 but perhaps that would have occurred previously too. Quote Mar 13 09:14:34 Tower root: ERROR: failed to zero device '/mnt/cache/system/docker/docker.img': Input/output error Mar 13 09:14:34 Tower root: btrfs-progs v5.10 Mar 13 09:14:34 Tower root: See http://btrfs.wiki.kernel.org for more information. Mar 13 09:14:34 Tower root: Mar 13 09:14:34 Tower root: failed to create file system Mar 13 09:14:34 Tower emhttpd: shcmd (367): exit status: 1 Mar 13 09:14:34 Tower emhttpd: shcmd (380): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1 Mar 13 09:14:34 Tower kernel: BTRFS info (device loop2): using free space tree Mar 13 09:14:34 Tower kernel: BTRFS info (device loop2): has skinny extents Mar 13 09:14:34 Tower kernel: BTRFS info (device loop2): enabling ssd optimizations Mar 13 09:14:34 Tower root: Resize '/etc/libvirt' of 'max' Mar 13 09:14:34 Tower emhttpd: shcmd (382): /etc/rc.d/rc.libvirt start Mar 13 09:14:34 Tower root: Starting virtlockd... Mar 13 09:14:34 Tower root: Starting virtlogd... Mar 13 09:14:34 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 27440 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 Mar 13 09:14:34 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 27440 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 Mar 13 09:14:34 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 27440 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 Mar 13 09:14:34 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 27440 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 Mar 13 09:14:34 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 27440 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 Mar 13 09:14:34 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 27440 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Mar 13 09:14:34 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 27440 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 Mar 13 09:14:34 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 27440 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 Mar 13 09:14:34 Tower root: Starting libvirtd... Mar 13 09:14:34 Tower kernel: tun: Universal TUN/TAP device driver, 1.6 Mar 13 09:14:34 Tower emhttpd: nothing to sync Mar 13 09:14:34 Tower unassigned.devices: Mounting 'Auto Mount' Remote Shares... Mar 13 09:14:57 Tower nmbd[11616]: [2021/03/13 09:14:57.595445, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Mar 13 09:14:57 Tower nmbd[11616]: ***** Mar 13 09:14:57 Tower nmbd[11616]: Mar 13 09:14:57 Tower nmbd[11616]: Samba name server TOWER is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.2 Mar 13 09:14:57 Tower nmbd[11616]: Mar 13 09:14:57 Tower nmbd[11616]: ***** Mar 13 09:15:01 Tower crond[1750]: exit status 1 from user root docker exec -u www-data nextcloud /usr/local/bin/php -f /var/www/html/cron.php Mar 13 09:15:01 Tower sSMTP[11882]: Creating SSL connection to host Mar 13 09:15:01 Tower sSMTP[11882]: SSL connection using TLS_AES_256_GCM_SHA384 Mar 13 09:15:01 Tower sSMTP[11882]: RCPT TO:<[email protected]> (553 5.7.1 <[email protected]>: Sender address rejected: not owned by user [email protected]) Mar 13 09:15:05 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 75776 op 0x1:(WRITE) flags 0x1800 phys_seg 8 prio class 0 Mar 13 09:15:05 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 75872 op 0x1:(WRITE) flags 0x1800 phys_seg 8 prio class 0 Mar 13 09:15:05 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 76032 op 0x1:(WRITE) flags 0x1800 phys_seg 16 prio class 0 Mar 13 09:15:05 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 180608 op 0x1:(WRITE) flags 0x1800 phys_seg 8 prio class 0 Mar 13 09:15:05 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 180704 op 0x1:(WRITE) flags 0x1800 phys_seg 8 prio class 0 Mar 13 09:15:05 Tower kernel: blk_update_request: critical space allocation error, dev loop2, sector 180864 op 0x1:(WRITE) flags 0x1800 phys_seg 16 prio class 0 Mar 13 09:15:05 Tower kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2377: errno=-5 IO failure (Error while writing out transaction) Edited March 14, 2021 by msnz Redacting log files Quote Link to comment
JorgeB Posted March 13, 2021 Share Posted March 13, 2021 Cache is completely full, free up some space then re-start docker service. Quote Link to comment
msnz Posted March 13, 2021 Author Share Posted March 13, 2021 Thank you @JorgeB - when I run the mover it seems to be trying to copy files to the cache drive, rather than the other way around. Everything is set to no cache, or prefer cache, except plextemp which is always set to use the cache drive. Is this the expected behaviour? Or should I be looking to free up space on the cache drive in some other way. Thanks again Quote Link to comment
JorgeB Posted March 13, 2021 Share Posted March 13, 2021 1 minute ago, msnz said: or prefer cache Cache=prefer moves data from array to cache, you want cache=yes, see the GUI help for more details. Quote Link to comment
msnz Posted March 13, 2021 Author Share Posted March 13, 2021 That worked. Thank you @JorgeB! 1 Quote Link to comment
Recommended Posts
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.