I vaguely remember having this when the blocksize did not match 4k from
a HDD pool to 16k for SSD pool.
Regards
Jorge
On 2016-11-29 10:26, Gjermund Gusland Thorsen wrote:
Did you stop the vm first?
vmadm stop 557ba0c0-b09c-678f-b1bc-a6bf2cc7b439; vmadm send
557ba0c0-b09c-678f-b1bc-a6bf2cc7b439 | ssh [email protected] vmadm
receive
G
On 29 Nov, 2016, at 10:08, Kilian Ries <[email protected]> wrote:
Hello,
yesterday i encountered the following problem:
I wanted to move a KVM from one host to another via "vmadm send"
command, but that ended up in the following error:
###
vmadm send 557ba0c0-b09c-678f-b1bc-a6bf2cc7b439 | ssh
[email protected] vmadm receive
Invalid value(s) for: disks.*.size
This socket is closed.
###
Reading the vmadm manual i figured out that
• disks.*.size MUST be an integer
• if you have a ZVOL, disks.*.size is depending on the size from the
ZVOL and cannot be updated via vmadm
So i think SmartOS does somewhere calculate wrong disksizes, because
there should always be an integer but that isn't the case in reallity,
for example:
-> first, output of vmadm get UUID
-> second, output of zfs get all zones/UUID-disk0
###
Example 1:
vmadm get UUID
"disks": [
{
...
"size": 117187.5,
...
}
]
volsize 114G
Example 2:
"disks": [
{
...
"size": 29296,875
...
}
]
volsize 28,6G
###
Why does SmartOS calculate wrong numbers here? These should all be
integers ...
Thanks
Greets
Kilian
smartos-discuss | Archives | Modify Your Subscription
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
