Hi, sorry for the delay. The reason things are failing when you try and
strace the restore is that CRIU also tries to ptrace its children to
restore certain things, and the kernel only allows one tracer at a time.
It is expected that /var/lib/lxd/shmounts/sample is empty, it's really
just a
I just thought: /var/lib/lxd/shmounts/sample/ is empty on the source
machine. Is that expected?
root@nuc1:~# ls -A /var/lib/lxd/shmounts/
sample
root@nuc1:~# ls -A /var/lib/lxd/shmounts/sample/
root@nuc1:~#
Also:
root@nuc1:~# mount | grep lxd
/dev/sda2 on /var/lib/lxd/shmounts type ext4
Using inotifywait -mr on the target:
~~~
root@nuc2:~# inotifywait -mr /var/lib/lxd/shmounts
Setting up watches. Beware: since -r was given, this may take a while!
Watches established.
/var/lib/lxd/shmounts/ CREATE,ISDIR sample2
/var/lib/lxd/shmounts/ OPEN,ISDIR sample2
/var/lib/lxd/shmounts/
Thank you. I have updated to lxd/xenial-proposed on both nodes. Now I am
back to the original problem:
root@nuc1:~# lxc move sample nuc2:sample2
error: Error transferring container data: restore failed:
(00.173165) 1: Error (mount.c:2406): mnt: Can't mount at
./dev/.lxd-mounts: No such file
You're probably hitting https://github.com/lxc/lxd/issues/1944 now. I
think LXD 2.0.1 has a fix for this if you want to enable xenial-
proposed. Otherwise, just deleting the container and recreating it
should fix that (until it modifies the disk in such a way that it breaks
again :)
--
You
The rsync --server processes remained on the target, so I've rebooted
both boxes, and also deleted the (stopped) target container.
The container to be migrated is running, and has a shell open running a simple
loop:
while [ 1 ]; do date; sleep 0.5; done
Same problem:
* The migration has frozen
[I should add: these systems are using plain dir backend on ext4: no
zfs, btrfs etc]
> Hmm. This means that either the source of the mount or the mount target
> didn't exist. I would expect LXD to create /var/lib/lxd/shmounts on the
> target host when it starts a migration (you can verify that
Hmm. This means that either the source of the mount or the mount target
didn't exist. I would expect LXD to create /var/lib/lxd/shmounts on the
target host when it starts a migration (you can verify that this happens
by `inotifywait /var/lib/lxd/shmounts` which should tell you that the
directory
** Attachment added: "Logs from nuc1 (migration source)"
https://bugs.launchpad.net/ubuntu/+source/criu/+bug/1580765/+attachment/4660910/+files/nuc1.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Logs from nuc2 (migration target)"
https://bugs.launchpad.net/ubuntu/+source/criu/+bug/1580765/+attachment/4660911/+files/nuc2.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
10 matches
Mail list logo
