#195 closed defect (fixed)
Data write problem
| Reported by: | cman | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | |
| Keywords: | Data write | Cc: | |
| Guest type: | other | Host type: | other |
Description
I have a problem when I copy a big files from a shared directory and also when I extract files of a .rar. I haver vbox 1.3.8 and Opensuse 10.2 host. the guest machine is windows for legacy pcs. Windows give me an error message like in screenshot. Sorry for my english. Diego
Attachments (2)
Change History (6)
by , 17 years ago
| Attachment: | problem_vbox.png added |
|---|
comment:1 by , 17 years ago
Can you please provide a release log (found in ~/.VirtualBox/Machines/VMNAME/Logs/VBox.log) from a run in which such an error occurred? The only occasion where I've seen such errors so far were indirectly caused by host OS problems, when the host filesystem took ages to write a 64K block (the maximum VBox writes in a single chunk). There should be an indication of that in the release log.
Guests have very limited patience (20 - 60 seconds for any IDE operation). But on normal host hardware it should be no big deal meeting those deadlines. But misconfiguration and/or failing hardware on the host can lead to guests timing out commands (which ultimatively can end up the way you observe).
by , 17 years ago
comment:2 by , 17 years ago
Ok there are the logs(I found four logs).. I understand the problem but in other hand I was a VMware user before virtualbox and I had no problem. In this case the problem is when I move a folder from a fat32 shared folder to the virtualdisk.
comment:3 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Thanks for the log files, they allowed me to track down the problem.
After much head scratching (the error in the log means that VirtualBox doesn't recognize the OS error code at all), I found the reason: VirtualBox always keeps VDI files in one piece (unlike VMware, which splits big image files into smaller chunks), and you hit the file size limit of the filesystem on which you placed the VDI (judging from the VDI path it's most likely a FAT32 filesystem, right?). The Linux FAT32 implementation supports only 2GByte IIRC, less than the 4G defined by the filesystem specification.
Next version of VirtualBox will handle this more gracefully (similarly to disk full, suspending the VM if this happens). VDIs will however still remain in one piece, so you need to place them on a file system which supports large files.
image with the message error