So you say it returns to the prompt after 1 minute.
Does it show any error at that point?
Can you try running incus monitor --pretty in another terminal while this is going on?
My guess is that there’s something on the filesystem that’s making rsync upset, but I’d have expected that to lead to an error…
Can you show cat /proc/self/mountinfo on the source system?
It looks a lot like your source system is using multiple mounts and you didn’t pass those to incus-migrate, leading to a partial filesystem on the target.
thanks Graber. I think that you solve my problem. For future rfeferences see below ( I do not migrate logs ..80)
Please enter the number of your choice: 1
Name of the new instance: hercules1
Please provide the path to a root filesystem: /
Do you want to add additional filesystem mounts? [default=no]: yes
Please provide a path the filesystem mount path [empty value to continue]: /usr
Please provide a path the filesystem mount path [empty value to continue]: /srv/backup
Please provide a path the filesystem mount path [empty value to continue]: /tmp
Please provide a path the filesystem mount path [empty value to continue]: /home
Please provide a path the filesystem mount path [empty value to continue]: /var
Please provide a path the filesystem mount path [empty value to continue]: /var/www
Please provide a path the filesystem mount path [empty value to continue]: /var/lib
Please provide a path the filesystem mount path [empty value to continue]: /var/lib/postgresql
Please provide a path the filesystem mount path [empty value to continue]: /var/lib/mysql
Please provide a path the filesystem mount path [empty value to continue]: /srv/samba
Please provide a path the filesystem mount path [empty value to continue]:
Instance to be created:
Name: hercules1
Project: default
Type: container
Source: /
Mounts:
/usr
/srv/backup
/tmp
/home
/var
/var/www
/var/lib
/var/lib/postgresql
/var/lib/mysql
/srv/samba
Now it appears another problem , but I’ll look for after it. Its a samba with special permissions…80)
Transferring instance: hercules1: 3.16GB (6.63MB/s)Error: Failed creating instance on target: Rsync receive failed: /var/lib/incus/stor
age-pools/hercules1/containers/hercules1/: [exit status 23] (rsync: [receiver] rsync_xal_set: lsetxattr(“/var/lib/incus/storage-pools/h
ercules1/containers/hercules1/rootfs/var/lib/samba/sysvol”,“security.NTACL”) failed: Operation not permitted (1)
rsync: [receiver] rsync_xal_set: lsetxattr(“/var/lib/incus/storage-pools/hercules1/containers/hercules1/rootfs/var/lib/samba/sysvol/fra
gmentadoras.com.br”,“security.NTACL”) failed: Operation not permitted (1)
rsync: [receiver] rsync_xal_set: lsetxattr(“/var/lib/incus/storage-pools/hercules1/containers/hercules1/rootfs/var/lib/samba/sysvol/fra
gmentadoras.com.br/Policies”,“security.NTACL”) failed: Operation not permitted (1)
rsync: [receiver] rsync_xal_set: lsetxattr(“/var/lib/incus/storage-pools/hercules1/containers/hercules1/rootfs/var/lib/samba/sysvol/fra
gmentadoras.com.br/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}”,“security.NTACL”) failed: Operation not permitted (1)
rsync: [receiver] rsync_xal_set: lsetxattr(“/var/lib/incus/storage-pools/hercules1/containers/hercules1/rootfs/var/lib/samba/sysvol/fra
gmentadoras.com.br/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/.GPT.INI.EdNwfO”,“security.NTACL”) failed: Operation not permitted (
1)
humm tried to search something about this. I know that is related with xattr and rsync ,but at target I configure container as security.privileged: “yes” ( know that is not the best way for security…)
and besides not create containers hercules1 it deletes all files that has been transfered from source to target 8-(((
If it leaves at least all copied files and create container I could at least try somenting else..
security.NTACL is likely an xattr that can’t be directly set by userspace (rsync).
At the time of the transfer, it doesn’t make any difference if the container is going to be privileged or not, the transfer happens as root on the receiving end anyway.
You may be able to somehow strip the xattrs on the source side prior to performing the migration.