Martin Felker wrote: Also it looks like you've confused two threads you started. This causes great confusion for anyone replying.
The only one greatly confused here is you! All KaL4 did in a thread he originally started and was resolved in Jan was to ask me if the .vmx configuration file I provided him was the cause of the current issue, which of course it's not, and then asked me why I though the error (of this thread) was being caused. It certainly made more sense to provide the answer here. I referenced the original thread since André had already provided an adequate simliar answer and I didn't want it to look like I was just butting in.
The bottom line is since the space is reclaimed upon Host reboot Ka4L needs to ascertain what explicitly and specifically is consuming that space and once that is known it can be properly dealt with. He has already been told by André and I what utilities can aid in uncovering that! Image may be NSFW.
Clik here to view.
