![]() ![]()
Vm has more disk space than reported by netapp plus#Each vm has it's own datasore the size of the vm plus 20 GB for snapshots (1 or 2 at the most, mainly for backup).Įach datastore is mapped to its own LUN on my SAN. I just want to zero out the deleted files used by the guest operating system, which in turn will shrink the vm.Ĥth - I do not want to take down the vm as I would have to with vConverter.Įxplanation for reason #2 - I didn't put all my vm's into one giant datastore. So no, I'm not doing that.ģrd - Like I mentioned earlier, I do not want to resive the partition or vm disk. So, how can I accomplish this?ġst - Why should I have to clone the VM just to make sure the vm is as small as possible, its just overkill?Ģnd - It would required the creation of a completely separate datastore, then after the clone process I would have to copy the disk back into the correct datastore. Vm has more disk space than reported by netapp how to#I know there are program(s) for $$$$$ out there that can do this, but I'm a cheapscate who would rather learn how to do it himself. Vm has more disk space than reported by netapp free#I want to clean, flush, free up all the space in my vm that is actually not being used. So my question is how to I "shrink" this vm? When I search through the kb all I find is how to shrink a vmdk file from 50 to 30 GB, but that is not what I want. Vm has more disk space than reported by netapp windows#Where in the world did that extra data come from? I'm assuming its because the geust os is windows, and since windows never really deletes a file, just its markers, this could be why. Wow, over 6 times of the amount of data that is in the VM. When I go to my SAN manager and look at the LUN this (and only this) VM sits on, it says there is 65.76 GB of used space. R2 w/SP2 that has a C: with 5.32 GB of used space and a with 4.19 GB of used space (almost 10 GB). You can have things like snapshoting, de-duplication, transparent compression, etc.I have several VM's that appear to be taking up a lot more space on my SAN than the VM has data in it. The questions of "how much space do I have" or "how much space does this file take up" don't always have simple answers. These days, there are lots of advanced ways of saving space on filesystems. The file is said to be taking up more space than it really is. ![]() You can also do similar (but not the same) things with sparse files. Then when you do a du, your system makes an NFS call to say "how big is this file", upon which the remote system can respond however it wants. When you run df, your system makes an NFS call to say "how big is this filesystem", in which the remote system can respond however it wants. This may seem like an oddity, but it's perfectly legal (in terms of NFS, kernel, etc). When analyzed, each snapshot looks like the same size as the original volume. So what the NetApp is likely doing is letting you access those snapshots through its /backup/.snapshot directory. But the 2 filesystems share the same data (physical volume blocks) until that data is changed on one of them. If you mount it, you've now got 2 100GB filesystems mounted. But you can also take this snapshot and mount it up like a normal volume. Now any files (blocks really) that are modified on the logical volume are copied so that the snapshot will have access to the original data. Then you create a snapshot of that logical volume. You do some stuff, put some files on it, etc. Now you create a 100GB logical volume on that volume group. Lets say you have a 1TB physical disk with 100% of it mapped to an LVM volume group. This sounds like it's operating very similar to how Linux's LVM operates. ![]() It's been a while since I've used NetApp, and so I can't answer with absolute authority, but I can provide an explanation for this type of behavior. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |