VB broke my USB? [HELP]

[MarshalBox]

Hello, I have to share this as i'be seen 0 post talking about this anywere.
It happened to me like 3 times, and I did not know the possible cause since today.

I exported a virtual machine to my USB device, the fact is that my USB had like 20MB left and I didnt realized, obvious the .ova was going to be heavier than 20MB so the exportation got stuck in 20% and the time left counter went higher to like 14 days until I realized that it was stuck, cheked the USB capacity without stopping exportation, it had 0 space left, i deleted like 80MB from two old .ovas, exportation still stuck, checked again my USB, still at 0 space left (after cleaning 80MB). I canceled the exportation and cursor went on the small_clock_above_him_mode like is going to close the window, but nope, dosn't get closed.

I had to shutdown virtualbox manually as it wasn't able to close by itself. I went to my USB to see if the .ova was exported correctly, only 20MB, it wasnt the full ova, cheked the free space of the USB and still in 0 bytes.

So thats it, my USB has no space left, even when i delete stuff it keeps at 0 bytes of free space. I can still open the images, files and stuff i have in it, i can copy the stuff to my computer. I can take off but cant put in because it has no space left.

Hope someone knows this issue and can help me to solve it, thx for reading since my english is not the best.

Working on:
- Ubuntu 12.04,
- VB version 4.1.44_Ubuntu r104071

[mpack]

You are describing a problem with the Ubuntu filesystem, encountered while using an Ubuntu fork of VirtualBox - which around here means it isn't VirtualBox. For both those reasons I don't think we can have much of a discussion about your issue here.

[MarshalBox]

How I can aboid this to happen again?

Thx for reply

[socratis]

Uninstall the VirtualBox fork. Download and install the official VirtualBox (and its matching Extension Pack if you wish).

[mpack]

It would still have nothing to do with VirtualBox, even if it was real VirtualBox.

VirtualBox doesn't do anything special to access host files, it uses the host OS file API. So if the host OS leaves any filesystem in an unusable state then that's a support issue for the host OS developers.