[Users] Clarification - Thin Disk
------=_NextPartTM-000-a91c9107-4b77-48f8-9d90-42109529926d Content-Type: multipart/alternative; boundary="_000_12EF8D94C6F8734FB2FF37B9FBEDD173585B2712EXCHANGEcollogi_" --_000_12EF8D94C6F8734FB2FF37B9FBEDD173585B2712EXCHANGEcollogi_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, could someone clarify the term "thin disk" in the context of Templates. Up to now for me a thin disk is space that is allocated on demand. But if I create VM from a template and use type "Thin" it must be a little bit different. The newly created VM will operate on the frozen template data plus some delta file that stores the changed block. Is that right? Shouldn't that be a "linked-disk"? Extra question: Why can't I move a (thin provisioned) template disk and instead have to copy it and delete it afterwards? Thanks in advance. Markus --_000_12EF8D94C6F8734FB2FF37B9FBEDD173585B2712EXCHANGEcollogi_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html dir=3D"ltr"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> <style id=3D"owaParaStyle" type=3D"text/css">P {margin-top:0;margin-bottom:= 0;}</style> </head> <body ocsi=3D"0" fpstyle=3D"1"> <div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: = 10pt;">Hello,<br> <br> could someone clarify the term "thin disk" in the context of Temp= lates.<br> Up to now for me a thin disk is space that is allocated on demand.<br> <br> But if I create VM from a template and use type "Thin" it must be= a <br> little bit different. The newly created VM will operate on the frozen <br> template data plus some delta file that stores the changed block.<br> Is that right? Shouldn't that be a "linked-disk"?<br> <br> Extra question: Why can't I move a (thin provisioned) template disk <br> and instead have to copy it and delete it afterwards?<br> <br> Thanks in advance.<br> <br> Markus<br> </div> </body> </html> --_000_12EF8D94C6F8734FB2FF37B9FBEDD173585B2712EXCHANGEcollogi_-- ------=_NextPartTM-000-a91c9107-4b77-48f8-9d90-42109529926d Content-Type: text/plain; name="InterScan_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="InterScan_Disclaimer.txt" **************************************************************************** Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Über das Internet versandte E-Mails können unter fremden Namen erstellt oder manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine rechtsverbindliche Willenserklärung. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln Vorstand: Kadir Akin Dr. Michael Höhnerbach Vorsitzender des Aufsichtsrates: Hans Kristian Langva Registergericht: Amtsgericht Köln Registernummer: HRB 52 497 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. e-mails sent over the internet may have been written under a wrong name or been manipulated. That is why this message sent as an e-mail is not a legally binding declaration of intention. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln executive board: Kadir Akin Dr. Michael Höhnerbach President of the supervisory board: Hans Kristian Langva Registry office: district court Cologne Register number: HRB 52 497 **************************************************************************** ------=_NextPartTM-000-a91c9107-4b77-48f8-9d90-42109529926d--
On 12/19/2013 07:54 AM, Markus Stockhausen wrote:
Hello,
could someone clarify the term "thin disk" in the context of Templates. Up to now for me a thin disk is space that is allocated on demand.
But if I create VM from a template and use type "Thin" it must be a little bit different. The newly created VM will operate on the frozen template data plus some delta file that stores the changed block. Is that right? Shouldn't that be a "linked-disk"?
thin doesn't mean it has a snapshot, only its not pre-allocating the entire storage needed iirc.
Extra question: Why can't I move a (thin provisioned) template disk and instead have to copy it and delete it afterwards?
just wasn't a prominent use case to implement i guess (would also need to check no VMs/disks derive from the template of course).
participants (2)
-
Itamar Heim -
Markus Stockhausen