We encountered something similar a while ago and found that it was a permissions issue as suggested in another answer today. Did you look into that? This does not raise an error in vmadm send but breaks the restore/receive part. Just my 2ct. Peter
Using the file method I’ve discovered that the problem is on the receiving side. I was able to use vmadm to save the zone to a NFS share, when trying to import I get # gunzip -c /mnt/disk/a701146d-3790-4150-92b8-3e30731b7b34.backup.tgz |vmadm receive -v Command failed: /zones/a701146d-3790-4150-92b8-3e30731b7b34/root is not owned by root. could not verify zonepath /zones/a701146d-3790-4150-92b8-3e30731b7b34 because of the above errors. zoneadm: zone a701146d-3790-4150-92b8-3e30731b7b34 failed to verify I’m running as root in the GZ. From a log file in /var/log/vm/logs I pasted @ https://pastebin.com/mkT9iuPQ It looks like the problem might be with zoneadm, why I haven’t figured out yet. -Chad | ||
- [smartos-discuss] vmadm send -> receive not working Chad M Stewart
- Re: [smartos-discuss] vmadm send -> receive not wo... Matthew Parsons
- Re: [smartos-discuss] vmadm send -> receive no... Chad M Stewart
- AW: [smartos-discuss] vmadm send -> receiv... Peter Kelm
- Re: [smartos-discuss] vmadm send -> re... Chad M Stewart
- Re: [smartos-discuss] vmadm send -> receive not wo... Paul Sture
