Virtual Disk .vmdik file taking too much space
up vote
0
down vote
favorite
I am runing 4 virtual machines on my macbook pro, But i realized recently that virtual disk vmdk files are taking way too much space, I will very much like to delete these .vmdk files but i am not sure if deleting them will affect my existing virtual machines. everywhere I have looked so far provides mixed information that doest not help my current situation. Attached is a screenshot of my system information.
virtual-machine vmware-fusion vmdk
edited Dec 3 at 19:37
Hennes
58.8k792141
asked Oct 15 at 18:45
christian x
2328
|
show 3 more comments
up vote
0
down vote
favorite
I am runing 4 virtual machines on my macbook pro, But i realized recently that virtual disk vmdk files are taking way too much space, I will very much like to delete these .vmdk files but i am not sure if deleting them will affect my existing virtual machines. everywhere I have looked so far provides mixed information that doest not help my current situation. Attached is a screenshot of my system information.
virtual-machine vmware-fusion vmdk
edited Dec 3 at 19:37
Hennes
58.8k792141
asked Oct 15 at 18:45
christian x
2328
You have to look at the settings of all your virtual machines to see where these disks are used. If these are system disks, their size is entirely normal. Is it possible that you have created the disks with "Allocate all disk space now"?
– harrymc
Oct 15 at 19:12
The settings under Virtual Disk.vmdk is set to: split into multiple files. I am not sure that is an issue or not
– christian x
Oct 15 at 19:22
Does this mean that they all belong to the same VM (are all in the same folder)? Have you created the disk with "Allocate all disk space now"?
– harrymc
Oct 15 at 19:24
no they don't all be all belong to the same vm but different VMs, when clicking they description point to the VM the files belong to. my worry is that what will happen if I deleted these file
– christian x
Oct 15 at 19:28
1
I think so, unless you can locate which disk belongs to which VM. In any case, you must remove the disk from the VMware settings of the machine before deleting the file. Blindly deleting files leads to damaged VM.
– harrymc
Oct 15 at 19:36
|
show 3 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am runing 4 virtual machines on my macbook pro, But i realized recently that virtual disk vmdk files are taking way too much space, I will very much like to delete these .vmdk files but i am not sure if deleting them will affect my existing virtual machines. everywhere I have looked so far provides mixed information that doest not help my current situation. Attached is a screenshot of my system information.
virtual-machine vmware-fusion vmdk
edited Dec 3 at 19:37
Hennes
58.8k792141
asked Oct 15 at 18:45
christian x
2328
I am runing 4 virtual machines on my macbook pro, But i realized recently that virtual disk vmdk files are taking way too much space, I will very much like to delete these .vmdk files but i am not sure if deleting them will affect my existing virtual machines. everywhere I have looked so far provides mixed information that doest not help my current situation. Attached is a screenshot of my system information.
virtual-machine vmware-fusion vmdk
virtual-machine vmware-fusion vmdk
edited Dec 3 at 19:37
Hennes
58.8k792141
asked Oct 15 at 18:45
christian x
2328
edited Dec 3 at 19:37
Hennes
58.8k792141
asked Oct 15 at 18:45
christian x
2328
edited Dec 3 at 19:37
Hennes
58.8k792141
edited Dec 3 at 19:37
Hennes
58.8k792141
edited Dec 3 at 19:37
Hennes
58.8k792141
58.8k792141
asked Oct 15 at 18:45
christian x
2328
asked Oct 15 at 18:45
christian x
2328
asked Oct 15 at 18:45
christian x
2328
2328
You have to look at the settings of all your virtual machines to see where these disks are used. If these are system disks, their size is entirely normal. Is it possible that you have created the disks with "Allocate all disk space now"?
– harrymc
Oct 15 at 19:12
The settings under Virtual Disk.vmdk is set to: split into multiple files. I am not sure that is an issue or not
– christian x
Oct 15 at 19:22
Does this mean that they all belong to the same VM (are all in the same folder)? Have you created the disk with "Allocate all disk space now"?
– harrymc
Oct 15 at 19:24
no they don't all be all belong to the same vm but different VMs, when clicking they description point to the VM the files belong to. my worry is that what will happen if I deleted these file
– christian x
Oct 15 at 19:28
1
I think so, unless you can locate which disk belongs to which VM. In any case, you must remove the disk from the VMware settings of the machine before deleting the file. Blindly deleting files leads to damaged VM.
– harrymc
Oct 15 at 19:36
|
show 3 more comments
You have to look at the settings of all your virtual machines to see where these disks are used. If these are system disks, their size is entirely normal. Is it possible that you have created the disks with "Allocate all disk space now"?
– harrymc
Oct 15 at 19:12
The settings under Virtual Disk.vmdk is set to: split into multiple files. I am not sure that is an issue or not
– christian x
Oct 15 at 19:22
Does this mean that they all belong to the same VM (are all in the same folder)? Have you created the disk with "Allocate all disk space now"?
– harrymc
Oct 15 at 19:24
no they don't all be all belong to the same vm but different VMs, when clicking they description point to the VM the files belong to. my worry is that what will happen if I deleted these file
– christian x
Oct 15 at 19:28
1
I think so, unless you can locate which disk belongs to which VM. In any case, you must remove the disk from the VMware settings of the machine before deleting the file. Blindly deleting files leads to damaged VM.
– harrymc
Oct 15 at 19:36
You have to look at the settings of all your virtual machines to see where these disks are used. If these are system disks, their size is entirely normal. Is it possible that you have created the disks with "Allocate all disk space now"?
– harrymc
Oct 15 at 19:12
You have to look at the settings of all your virtual machines to see where these disks are used. If these are system disks, their size is entirely normal. Is it possible that you have created the disks with "Allocate all disk space now"?
– harrymc
Oct 15 at 19:12
The settings under Virtual Disk.vmdk is set to: split into multiple files. I am not sure that is an issue or not
– christian x
Oct 15 at 19:22
The settings under Virtual Disk.vmdk is set to: split into multiple files. I am not sure that is an issue or not
– christian x
Oct 15 at 19:22
Does this mean that they all belong to the same VM (are all in the same folder)? Have you created the disk with "Allocate all disk space now"?
– harrymc
Oct 15 at 19:24
Does this mean that they all belong to the same VM (are all in the same folder)? Have you created the disk with "Allocate all disk space now"?
– harrymc
Oct 15 at 19:24
no they don't all be all belong to the same vm but different VMs, when clicking they description point to the VM the files belong to. my worry is that what will happen if I deleted these file
– christian x
Oct 15 at 19:28
no they don't all be all belong to the same vm but different VMs, when clicking they description point to the VM the files belong to. my worry is that what will happen if I deleted these file
– christian x
Oct 15 at 19:28
1
1
I think so, unless you can locate which disk belongs to which VM. In any case, you must remove the disk from the VMware settings of the machine before deleting the file. Blindly deleting files leads to damaged VM.
– harrymc
Oct 15 at 19:36
I think so, unless you can locate which disk belongs to which VM. In any case, you must remove the disk from the VMware settings of the machine before deleting the file. Blindly deleting files leads to damaged VM.
– harrymc
Oct 15 at 19:36
|
show 3 more comments
1 Answer
1
active
oldest
votes
up vote
0
down vote
You cannot physically delete files as long as they are included in the
definition of a VM or you risk damaging it.
You must remove the disk from the VMware settings of the VM before deleting the file.
If the file is the system disk of the VM, you might as well delete the VM itself.
I find it strange that all the files have the same size, so I ask myself if
you have pre-allocated them all. Files should be defined as growable to use
minimal space. It is still possible to convert a static file to growable
if that's the case, but reducing it is a longer story.
answered Oct 15 at 20:44
harrymc
251k11259559
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1367032%2fvirtual-disk-vmdik-file-taking-too-much-space%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You cannot physically delete files as long as they are included in the
definition of a VM or you risk damaging it.
You must remove the disk from the VMware settings of the VM before deleting the file.
If the file is the system disk of the VM, you might as well delete the VM itself.
I find it strange that all the files have the same size, so I ask myself if
you have pre-allocated them all. Files should be defined as growable to use
minimal space. It is still possible to convert a static file to growable
if that's the case, but reducing it is a longer story.
answered Oct 15 at 20:44
harrymc
251k11259559
add a comment |
up vote
0
down vote
You cannot physically delete files as long as they are included in the
definition of a VM or you risk damaging it.
You must remove the disk from the VMware settings of the VM before deleting the file.
If the file is the system disk of the VM, you might as well delete the VM itself.
I find it strange that all the files have the same size, so I ask myself if
you have pre-allocated them all. Files should be defined as growable to use
minimal space. It is still possible to convert a static file to growable
if that's the case, but reducing it is a longer story.
answered Oct 15 at 20:44
harrymc
251k11259559
add a comment |
up vote
0
down vote
up vote
0
down vote
You cannot physically delete files as long as they are included in the
definition of a VM or you risk damaging it.
You must remove the disk from the VMware settings of the VM before deleting the file.
If the file is the system disk of the VM, you might as well delete the VM itself.
I find it strange that all the files have the same size, so I ask myself if
you have pre-allocated them all. Files should be defined as growable to use
minimal space. It is still possible to convert a static file to growable
if that's the case, but reducing it is a longer story.
answered Oct 15 at 20:44
harrymc
251k11259559
You cannot physically delete files as long as they are included in the
definition of a VM or you risk damaging it.
You must remove the disk from the VMware settings of the VM before deleting the file.
If the file is the system disk of the VM, you might as well delete the VM itself.
I find it strange that all the files have the same size, so I ask myself if
you have pre-allocated them all. Files should be defined as growable to use
minimal space. It is still possible to convert a static file to growable
if that's the case, but reducing it is a longer story.
answered Oct 15 at 20:44
harrymc
251k11259559
answered Oct 15 at 20:44
harrymc
251k11259559
answered Oct 15 at 20:44
harrymc
251k11259559
answered Oct 15 at 20:44
harrymc
251k11259559
251k11259559
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1367032%2fvirtual-disk-vmdik-file-taking-too-much-space%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You have to look at the settings of all your virtual machines to see where these disks are used. If these are system disks, their size is entirely normal. Is it possible that you have created the disks with "Allocate all disk space now"?
– harrymc
Oct 15 at 19:12
The settings under Virtual Disk.vmdk is set to: split into multiple files. I am not sure that is an issue or not
– christian x
Oct 15 at 19:22
Does this mean that they all belong to the same VM (are all in the same folder)? Have you created the disk with "Allocate all disk space now"?
– harrymc
Oct 15 at 19:24
no they don't all be all belong to the same vm but different VMs, when clicking they description point to the VM the files belong to. my worry is that what will happen if I deleted these file
– christian x
Oct 15 at 19:28
1
I think so, unless you can locate which disk belongs to which VM. In any case, you must remove the disk from the VMware settings of the machine before deleting the file. Blindly deleting files leads to damaged VM.
– harrymc
Oct 15 at 19:36