and judging by what I see, *zones/34d66287-0a73-cc80-c64f-da753975429c-disk0* is not a child to a dataset *zones/34d66287-0a73-cc80-c64f-da753975429c*
[root@bacula ~]# zfs list | grep 34d66287-0a73-cc80-c64f-da753975429c zones/34d66287-0a73-cc80-c64f-da753975429c 657M 9.36G 657M /zones/34d66287-0a73-cc80-c64f-da753975429c zones/34d66287-0a73-cc80-c64f-da753975429c-disk0 66.0G 1.33T 17.2G - 2016-12-28 23:36 GMT+02:00 Tiraen <[email protected]>: > Changing the zvol size requires cooperation from the guest. Upsizing may > be possible by increasing the zone quota, then increasing the zvol size, > then repartitioning the virtual disk in the guest. It's possible, but not > directly supported. > > Thank you, it has now become clear. Last point then to clarify: > > Take for example the same VM: > > [root@bacula ~]# vmadm list | grep KVM > 34d66287-0a73-cc80-c64f-da753975429c KVM 8048 running > backend_kvm > > It is installing from zero > > "disks": [ > { > "boot": true, > "model": "virtio", > "size": 50000 > } > ], > > Here are some of json file which describes the disc > > The machine works normally, but at the same time > > *[root@bacula ~]# vmadm get 34d66287-0a73-cc80-c64f-da753975429c | grep > quota* > > > > > > > > > * "quota": 10,That corresponds:[root@bacula ~]# zfs list | grep > 34d66287-0a73-cc80-c64f-da753975429czones/34d66287-0a73-cc80-c64f-da753975429c > 657M 9.36G 657M /zones/34d66287-0a73-cc80-c64f-da753975429c > - This datasetzones/34d66287-0a73-cc80-c64f-da753975429c-disk0 66.0G > 1.35T 17.2G -* > > > > 2016-12-28 23:06 GMT+02:00 Brian Bennett <[email protected]>: > >> The quota on a dataset needs to be large enough to contain all child >> datasets. It needs to be large enough to hold both virtual disks, plus >> space for the zone itself. >> >> Changing the zvol size requires cooperation from the guest. Upsizing may >> be possible by increasing the zone quota, then increasing the zvol size, >> then repartitioning the virtual disk in the guest. It's possible, but not >> directly supported. >> >> -- >> Brian Bennett >> Systems Engineer, Cloud Operations >> Joyent, Inc. | www.joyent.com >> >> On Dec 28, 2016, at 11:58 AM, Tiraen <[email protected]> wrote: >> >> The questions were as follows: >> >> >> >> *1) What is in this zone, given the fact that the for information create >> a separate dataset? (disk-0)* >> For KVM VMs, this value is >> the quota for the Zone containing the VM, which is not directly >> available to users. >> >> >> zones/34d66287-0a73-cc80-c64f-da753975429c 657M 9.36G >> 657M /zones/34d66287-0a73-cc80-c64f-da753975429c >> >> Why may be necessary increase the quota for this dataset for example >> >> >> * 2) Besides the standard zfs set/get volsize through vmadm increase in >> drive sizes possible in online?* >> zones/34d66287-0a73-cc80-c64f-da753975429c-disk0 66.0G 1.35T >> 17.2G - >> >> Through vmadm have the opportunity to increase this dataset? >> >> 2016-12-28 21:51 GMT+02:00 Tiraen <[email protected]>: >> >>> Demonstrating this to friends who are used to dealing with lesser >>> hypervisors will shock and amaze them. >>> >>> Thank you, I appreciated the humor, but he was not out of place. If you >>> did not work out, read the email subgect. It describes which type of VM it >>> is set. >>> >>> I am more than a detailed description of the question, but oh well, >>> let's again: >>> >>> For example, we have such KVM machine: >>> >>> *[root@bacula ~]# vmadm list | grep KVM* >>> *34d66287-0a73-cc80-c64f-da753975429c KVM 8048 running >>> backend_kvm* >>> >>> When you create a VM you get a set of datasets: >>> *[root@bacula ~]# zfs list | grep 34d66287-0a73-cc80-c64f-da753975429c* >>> zones/34d66287-0a73-cc80-c64f-da753975429c 657M 9.36G >>> 657M /zones/34d66287-0a73-cc80-c64f-da753975429c >>> zones/34d66287-0a73-cc80-c64f-da753975429c-disk0 66.0G 1.35T >>> 17.2G - >>> zones/cores/34d66287-0a73-cc80-c64f-da753975429c 23K 100G >>> 23K /zones/34d66287-0a73-cc80-c64f-da753975429c/cores >>> >>> Drive directly to the KVM machine data this: >>> >>> *zones/34d66287-0a73-cc80-c64f-da753975429c-disk0 66.0G 1.35T >>> 17.2G* >>> [root@bacula ~]# zfs get volsize zones/34d66287-0a73-cc80-c64f- >>> da753975429c-disk0 >>> NAME PROPERTY VALUE >>> SOURCE >>> zones/34d66287-0a73-cc80-c64f-da753975429c-disk0 volsize 55G >>> local >>> >>> This corresponds primarily installed when installing the machine >>> >>> And its size is not changed through vmadm >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> 2016-12-28 21:35 GMT+02:00 Rob Seastrom <[email protected]>: >>> >>>> >>>> > On Dec 28, 2016, at 9:49 AM, Tiraen <[email protected]> wrote: >>>> > >>>> > quota: >>>> > >>>> > >>>> > 1) Zone containing the VM >>>> > >>>> > What is in this zone, given the fact that the for information create >>>> a separate dataset? (disk-0) >>>> >>>> I'm not sure I understand the question. >>>> >>>> > 2) Besides the standard zfs set/get volsize through vmadm increase in >>>> drive sizes possible in online? >>>> >>>> vmadm update <uuid> quota=100 >>>> >>>> will set your quota to 100 gigabytes, on a running zone, takes effect >>>> instantly, no need to reboot. You can adjust up or down, and remember it's >>>> a quota not a reservation - you can oversubscribe the zpool size and so >>>> long as everyone doesn't grab space at the same time you're fine (powerful, >>>> but potentially dangerous in the wrong hands). >>>> >>>> Demonstrating this to friends who are used to dealing with lesser >>>> hypervisors will shock and amaze them. >>>> >>>> -r >>>> >>> >>> >>> >>> -- >>> With best regards, >>> >>> Vyacheslav Yakushev, >>> >>> Unix system administrator >>> >> >> >> -- >> With best regards, >> >> Vyacheslav Yakushev, >> >> Unix system administrator >> > > > -- > With best regards, > > Vyacheslav Yakushev, > > Unix system administrator > -- With best regards, Vyacheslav Yakushev, Unix system administrator ------------------------------------------- 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
