Opened 14 years ago
Closed 9 years ago
#8620 closed defect (obsolete)
file io problems with large files across shared network forlders or locally too
Reported by: | art | Owned by: | |
---|---|---|---|
Component: | shared folders | Version: | VirtualBox 4.0.4 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Windows |
Description (last modified by )
Hello,
I am seeing problems when either reading large files across a shared network folder and or saving files across shared network folders. This also occurs with the same large files when they are copied locally to the vb. The problems seem to occur only on large files say 500mg - 3gig in size. Do not see problem on smaller files. The failure is not always in the same spot, but the internal buffers of vb must be getting messed up somehow, since the data being passed back to my app is corrupted or the data that ends up being written is corrupted. I have tried this with two separate applications which both do a tremendous amount file i/o. If these apps are run in a non-vb environment they perform fine with the file io. If the apps are taken to a vmware environment, they also perform fine. I did not see this behavior in vb 3x. There just seems to be some instability when doing a tremendous amount of continuous file io. sorry i cannot be more specific, but never had these problems prior to vb4
thank you, art
Attachments (1)
Change History (5)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if still relevant with VBox 4.0.8. In that case please also attach a VBox.log file of such a VM session.
by , 14 years ago
comment:3 by , 14 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Still see problems with v4.0.8, attached log file. thank you.
comment:4 by , 9 years ago
Description: | modified (diff) |
---|---|
Resolution: | → obsolete |
Status: | reopened → closed |
Please reopen if still relevant with a recent VirtualBox release.
Your VBox.log file is missing. Please test if the test build from #8826 makes any difference.