On Sun, Mar 20, 2016 at 6:19 AM, Martin Steigerwald <mar...@lichtvoll.de> wrote: > On Sonntag, 20. März 2016 10:18:26 CET Patrick Tschackert wrote: >> > I think in retrospect the safe way to do these kinds of Virtual Box >> > updates, which require kernel module updates, would have been to >> > shutdown the VM and stop the array. *shrug* >> >> >> After this, I think I'll just do away with the virtual machine on this host, >> as the app contained in that vm can also run on the host. I tried to be >> fancy, and it seems to needlessly complicate things. > > I am not completely sure and I have no exact reference anymore, but I think I > read more than once about fs benchmarks running faster in Virtualbox than on > the physical system, which may point at an at least incomplete fsync() > implementation for writing into Virtualbox image files. > > I never found any proof of this nor did I specificially seeked to research it. > So it may be true or not.
Sure but that would only affect the guest's file system, the one inside the VDI. It's the host managed filesystem that's busted. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
