Confusion of thin or thick disk

Hi all

I have a strange problem.

We have a several s vm disk who told me are thick, but all I can see suggests that they are thin.

In the data of one of the disks store, it says the following: size and put into service, which shows me the disc is thin.

disk.JPG

Do not know why the size shows still as provisioned, while the Linux operating system is no indication that 52 GB is used out of the 100 GB provisioned

When your right click on the vmdk, you have the ability to inflate the disc, this also highlights the disc being thin provisioned.

According to my understanding, the inflation option should be grayed out, be they vmdk is supplied thickness.

When you right-click the virtual machine, select edit it also shows the drive as being thin

thindisk.JPG

Someone has seen a question similar to this one before or can help clarify if my argument of the disk being thin is correct or not.

Thank you

JIT

According to your screenshots, discs are THIN provisioned. If the disk is THICK you get a column 'Provisioned size' (screenshot Ref first). I assume you are using the VI client.

Also you don't get not "inflate the option" If the disk is THICK. You are right.

Post edited by: vVision

Tags: VMware

Similar Questions

  • Thin and thick disks on the same virtual machine?

    Is this possible with vsphere ESX 4... to have a disc thin and thick, attached to the same Virtual Machine... ? Is this documented place... ?

    Thanks,-Nicodemus

    Yes...

    Page 247

    http://books.Google.com/books?id=b12tupvbqEAC&PG=PA247&LPG=PA247&DQ=VMware mixingthinandthick+disk&source=bl&ots=FOCD-X9lMP&sig=z720_K5b3M99GfOLqtlBkeixXBU&hl=en&ei=YkAhTOWCMcbonQeL4MRy&sa=X&oi=book_result&ct=result&resnum=3&ved=0CCcQ6AEwAg#v=onepage&q=It%27s%20possible%20for%20a%20VM%20to%20have%20a%20mix%20of%20both%20thick%20and%20thin%20virtual%20disks&f=false

  • Need advice on thin or thick disk

    I need to install a few servers with openSuse11.1x64 and Oracle11.1 on vSphere4 and esx4i. Each server has a data store of 1 GB on the shared SAS storage.

    The databases will grow up to 1 TB.

    I have a big dilemma, what type of disc it is (thin or thick) and which is usually the best practice in this situation?

    I notice, for example, if I create a thickness of 1 TB disk, after that one or two snapshoot an error disk is full. If I create a thin disk it does not error, but what about thin disk IO performance?

    Thanks to all the good advice.

    Hello

    1 Vmware tools on openSUSE are "obsolete." How do I install them?

    The 'normal' fact. Select "Update VMware Tools" in the menu VM and OpenSUSE should see the latest VMware Tools CDROM. Maybe then you will need to run the installer of your self... However, if you use open VMware tools is another topic and there anotehr forum for this. The way to tell is to look at your list of openSuse packages and checks if there is a package named open-vm-tools, if yes, then you are using the open version. Let me know if I can redirect to the right position.

    2. If I did only a single VM on the server, the number of vCPU and memory is the best option?

    Do you plan on adding several virtual machines?

    3. my datastore has 4 MB block size because I need the 1 TB drive. Is this ok? Can I create with the lower block size 1 TB drive.

    N ° to create a 1 to VMDK file, you need the largest block size.

    For a VMFS with > 2 TB - 512 bytes of space, you would use "Extensions" to bring together multiple LUNS up to 64 TB - 512 byte MAX. There is an option to consider going forward... However, a single VMDK can only be 2 TB you would then look to add new disks and for strong transactional use DB I would forget in fact on the use of vmdk in all.

    In your case, I would use Raw Disk cards out of your storage device... Not VMDK and use several RDM for data/logs/etc.

    Best regards
    Edward L. Haletky VMware communities user moderator, VMware vExpert 2009

    Now available: url = http://www.astroarch.com/wiki/index.php/VMware_Virtual_Infrastructure_Security'VMware vSphere (TM) and Virtual Infrastructure Security' [/ URL]

    Also available url = http://www.astroarch.com/wiki/index.php/VMWare_ESX_Server_in_the_Enterprise"VMWare ESX Server in the enterprise" [url]

    Blogs: url = http://www.virtualizationpractice.comvirtualization practice [/ URL] | URL = http://www.astroarch.com/blog Blue Gears [url] | URL = http://itknowledgeexchange.techtarget.com/virtualization-pro/ TechTarget [url] | URL = http://www.networkworld.com/community/haletky Global network [url]

    Podcast: url = http://www.astroarch.com/wiki/index.php/Virtualization_Security_Round_Table_Podcastvirtualization security Table round Podcast [url] | Twitter: url = http://www.twitter.com/TexiwillTexiwll [/ URL]

  • Reference Dell HDS - recommended VMware virtual disk - drives provided - basic and dynamic thin and thick.

    Can someone point me to the literature on best practices for guest disc formats?

    I know all the Compellent thin-provisions. However, in VMware 5.5, when you set up a virtual disk in the comments you have several choices:

    • Lazy provisioned to zero thickness
    • Eager provisioned to zero thickness
    • Provision of thin

    And then, at the level of the OS, you have the choice of:

    • Base
    • Dynamics

    I would like a pointer to the technical document explaining the advantages/disadvantages of each choice and recommended best practices.

    Kind regards

    Kath

    I would like to either thin or thick lazy to zero.  The two will take the same amount of data on the HDS.  The main decision is where you want to manage your storage space?  If dilute you on thin you need to make sure that you make no provision in both places.  If you have thick lazy to zero, then you can only on commissioning on one side.

    Say that I always thin on thin.  Recovery of the space at the level of the virtual computer is not officially supported immediately, but maybe someday.

    In a virtualized environment, always keep it simple.  There is no dynamic performance with virtualization

  • Storage motioned to VM with thick disk thin disc?

    Recently, we tried using SMotion to convert the current thick disk of our VM provisioning, but it won't expand the c:\ partition when we increase the size of the disk in the vSphere client. According to the official docs it is supported using SMotion so if anyone can help me I would be grateful.

    No, just launch extpart on the virtual machine that you want to extend the volume on (after you have extended the volume in the settings of the virtual machine) from the command line and you will be asked to provide the letter of volume, then the size of developing.   If you have trouble with it I can do a screen cast for you in my environment if it would help.

    ---

    If you have found any of my reviews useful please consider giving points to 'Correct' or 'useful '. Thank you!!!

    www.beyondvm.com

  • NFS datastore on does not create the thick disk

    Hi Experts

    We have 4 and 5 from esx esx in our workplaces.

    I observed something strange with ESX 5, we cannot create thick disk for VM on NFS data warehouses

    While the same was collaborating with ESX 4. I'm still able to create thick disk using the same NFS volume.

    Nothing has changed in ESX 5.X? which does not allow users to create thick disk in NFS.

    Srinivas-

    NFS data with hardware acceleration warehouses and VMFS data storages are supported the following political drive of provisioning. On NFS warehouses that do not support hardware acceleration, that thin format is available. Link

  • convert thin in thickness but with less space

    Hello

    I create a Virtual Machine with 50 GB disc (using 10/15 GB) as thin on an ESX Server.

    I know how to create a thick disk, but I would like to create about 25/30 or not 50 Gb

    Is possible?

    How can I do?

    Thanks in advance

    IIRC, you will find the possibility to drive volume base conversion-based advanced settings for the 'disk '.

    André

  • Utility SSMove transforms THIN in THICKNESS discs!

    I'm cleaning off a LUN to use elsewhere. One of my collegaues brought to my attention that the SSMove utility seems to make thin records of THICKNESS after the move process. So I tested it myself, and of course, I was able to prove it.

    Although Lab Manager still displays the object as being thin provisioned, after the move, viewing the actual file and its content by browsing the data store in vSphere Client shows the truth.

    What was a thin disk supplied 3.6 g, became a real thick disk of 15 GB after the move. Screenshots are attached so you can see for yourself.

    This is quite alarming because it kinda defeats the purpose to have SSMove and support of thin disk. I mean, you can't have and use both!

    • Director of the laboratory 4.0.2.1269
    • vCenter Server and vSphere CLient v4.1.0 (Build 345043)
    • ESXi v4.1.0 (4.1 Update 1, Build 381591)

    I think that it is a known problem with Lab Manager (and its support tools).

    http://www.VMware.com/support/labmanager40/doc/releasenotes_labmanager401.html#thindiskissues

    There is a manual procedure to set records that have been made in thickness, but it's not pretty for many machines...

    http://communities.VMware.com/message/1498165

  • Thin VS. thick

    Pessoal,

    Gostaria to hear little but thin in thickness quanto ao e um...

    Ex. Tenho uma VM com 2 don't discos tolls (vmdk) em modo that thin, no cylindrical assim, o Datastore used e um NFS Windows operating system.

    C:\ TAM used 30 = 13 = Go book = 17 GB

    D:\ TAM = 40 used book 14GB = = 25GB

    Na tela vSphere Client, wave mostra os dados do Datastore (figura annex), apreenta o seguinte:

    Put into service = 72,00 GB storage

    No shared storage = 35,58 GB

    Storage used = 35,58 GB

    Finally, I would understand what estes dados are Querenda me say, quando os dados comparo

    that are no OS da VM com mostra o na tela vSphere Client. JA tive outros casos than olhando

    only para has tela vSphere Client a printing that is o Disco tem da VM esta cheio, very

    Quando observado dentro do OS ele esta por exemplo using 50% size.

    Busquei documents talking sober isso, mas will someone wake uma forma but easy (didatica) me

    get works do, Agradea§o desde ja esta como.

    Valeu!

    Fábio Rafael (moussoui)

    Samquejo wrote:

    Hi moussoui

    Thickness mode is a prealloue disk and thin mode is a stretch drive.

    In thick mode, you allways see the same size that provides you with.

    In fine mode, offers you a maximum size and drive grow until this size, but no shrink.

    If you have a thin disk of 10 GB, you can write to 5 GB and the disk drive to catch, but he maintence will sice that size if you format your virtual disk.

    Concerning

    VMTools will decrease the size of the vmdk file...

  • How can change the end of thick disk when a virtual machine has been placed on the disk?

    After you have moved the virtual computer to another stage, chose the thin disk bad. Now, the virtual machine cannot start. the error message says that it must be thick for clustering. So, I need to change it back if possible. Then I moved it back and thick chosed. But, after that, I got a same error. So, after you move, the atatuse disk was not be changed. Is it a way not both directions? How can change the staus thin to thick?

    Thank you!

    George

    Hello George,.

    You can also convert virtual disks in eagerzeroedthick from the command line.

    vmkfstools-j VMname.vmdk allows to convert a thin disk in eagerzeroedthick

    vmkfstools k VMname.vmdk that will do it on a thick disk

    It can also work for a thin disk, click with the right button on the vmdk in browser data store, and then click 'inflate '.

    André

  • Thin Provisioning of disks

    Looking to find the pros and cons or the pitfalls of provisioning of the disks. I guess that this is still done through vmkfstools. It also works back thick disks conversion?

    Thank you

    Mike

    To convert a thin disk to a drive do you use SVmotion or simple with vmkfstools-j (-inflatedisk).

    André

    * If you found this device or any other answer useful please consider awarding points for correct or helpful answers

  • Creating a series of thin to thick lines

    Ive done this before, but forget the tool it does.  I have a thin line and a thick line.  I want to fill the empty area between the two with several passages ranging from thin to thick.  There is a tool that does this automatically, where and how was it?

    According to me, that the tool degraded, it is what you are looking for. The keyboard shortcut is W.

  • thin VMDK and datstore thin or thick thick datastore vmdk

    Hello

    What is a better option regarding implementing vmdk thin or thick

    thin VMDK on the thin data store

    thick VMDK on the thick datastore?

    Hey tdubb123,

    It is mostly a choice preferably nothing these days as suppliers to support both options.  I know that some vendors recommend same end/end to get the most out of your storage space / KING.  However, whenever you make a thin provision you have another metric you need to monitor or alarms configuration for.  Personally, unless I am attached to the space I use thick on the SAN and thick on VMware.  However if I'm tight on space I'll do a store of data usually SAN thick and thin provision on VMware.  In this way the only place to look for a provisioning is in the Web of the customer/vSphere.  As for the API more get released and plugins are available to attach in the VI client/web Client it will become probably easier to manage.

    Keep in mind if dilute you available to a virtual machine, and from this data store is running out of space, the next time that VM requires space he will enter pause / stop state until there is a space available, if its something you'll deffiently want alarms setup for if go you end/thick thick/end, or end/end

    I hope this has helped.

  • Cannot convert thick disk of 10 GB on the thin disk

    I made the migration of storage a week ago to convert thin (10 GB hard drive) and he has succeeded at that time and I saw, it was transformed to thin. After a few days, it was automatically converted to thick. and it happened a few times already, also tried on a few other virtual machines that have 10GB, same thing happens, after a few days of thick back conversion.  I was wondering if there is no drive required to do the migration of storage? someone has an idea? I made large capacity disks more than 50 GB, they are very good. Just having trouble with low size disks

    -Thank you,

    Rahul

    John,

    When you do the storage vMotion, you selected a different data store then the one on which the virtual machine is? If this is not the case, try this one.

  • Conversion of thick disks into thin, but not for any space back

    Hi all

    We have been the conversion of the virtual disks from thick to thin over 30 servers using the method in offline mode, as we don't have storage vmotion:

    vmkfstools-i SERVERNAME.vmdk d thinSERVERNAME.vmdk thin

    The virtual machine is a good mix of NT4 until 2008, vsphere 4.1 all patches installed until 01/05/11. Some we have been recovery of space well when comparing the original vmdk and sizes of vmdk converted file on the console with 'ls s' and 'Browse datastore' in the viclient, but others that we do not get something back into space?

    Using Windows disk defrag to analyze the disks it shows there are no data at the end of the disc also surely the disc should shrink to where the last piece of data on the disk is?

    What you have to do to thin to reclaim any unused space on the virtual FRONT thickness conversion machine drive?

    Once that a disk block was written for her data even if the files have been deleted. You must use something like sdelete before use vmkfstools. Products like sdelete zero free space allowing you to reduce the disk.

Maybe you are looking for