Error 11 moving disk

N

network_potato

Member
Oct 23, 2022
5
0
6
Hi,

I have a system disk for a container that I want to move from local zfs to a Synology NAS iSCSI target.

When moving the disk, rsync exits with error code 11.

Code: 
Logical volume "vm-105-disk-0" created.
Creating filesystem with 2097152 4k blocks and 524288 inodes
Filesystem UUID: 41382c16-f6d3-4371-9d4d-9af3ab7c43a2
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
rsync: [receiver] write failed on "/var/lib/lxc/105/.copy-volume-1/var/log/daemon.log": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(378) [receiver=3.2.3]
rsync: [sender] write error: Broken pipe (32)
  Logical volume "vm-105-disk-0" successfully removed
TASK ERROR: command 'rsync --stats -X -A --numeric-ids -aH --whole-file --sparse --one-file-system '--bwlimit=0' /var/lib/lxc/105/.copy-volume-2/ /var/lib/lxc/105/.copy-volume-1' failed: exit code 11

It seems it thinks there is not enough space but either disk is nowhere near full.

What do I do?
 
Hi,
the issue could be that ZFS uses compression, so the data actually takes less space on the volume before the move. You can try to resize the source volume first. Then the target volume will be allocated with that bigger size too, but since you didn't actually add more data on the source, the move could then work.
 
But the container's disk is only 8GB and the ZFS volume that it is stored on right now has about 100GB free.

So can that really be the issue?
 
You're sure you still have space on root?
What do you get with
Code: 
df /
 
network_potato said:
But the container's disk is only 8GB and the ZFS volume that it is stored on right now has about 100GB free.
Click to expand...
I'm not sure what you mean. The container disk is a ZFS volume/dataset. Do you mean the underlying ZFS pool still has 100 GB free?

The issue can arise if the data that's actually stored on the container disk is more than 8GB logically, but fits in the disk because of compression (or sparse files). When the LVM disk is then allocated with 8GB and the data is copied over, it might not fit, because there is no compression on the target side anymore (or if sparse files are handled differently).
 
Fiona, it is not a problem of the volume/dataset. Rsync is unable to write the log file in /var/lib/...
So I still guess there is no free space left on root.
 
JensF said:
Fiona, it is not a problem of the volume/dataset. Rsync is unable to write the log file in /var/lib/...
So I still guess there is no free space left on root.
Click to expand...
No, /var/lib/lxc/105/.copy-volume-1 is where the file system for the target volume is mounted. That does not mean that the root FS on the host has no space.
 
fiona said:
No, /var/lib/lxc/105/.copy-volume-1 is where the file system for the target volume is mounted. That does not mean that the root FS on the host has no space.
Click to expand...
Ah yes, I see. Good to know. Thank you. :)
 
You must log in or register to reply here.
Top Bottom