Date: Thu, 8 Aug 2013 16:57:28 +0300 From: Sergey Slobodyanyuk <ssv.lkml@gmail.com> To: yuri@rawbw.com Cc: freebsd-hackers@freebsd.org Subject: Re: After the FreeBSD VM crash, file system in VM got rolled back to some old previous state causing data loss Message-ID: <CALx9bBpOgxV0%2BuO54ngZoRPO2RokCyGHvs%2BUa2AF-A3ujYn_VQ@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
> > On 08/07/2013 01:56, Wojciech Puchar wrote: > > > > not possible in FreeBSD with UFS. > > > > but if you run virtualbox under linux i cannot say much... > > This happened with FreeBSD guest with UFS (journaled soft-updates) and > FreeBSD host. > What is out of normal, it rolled back for many hours (~20). > > Yuri > > Could be you are using *Immutable images *as type of disk for guest VM 1. *Immutable images.* When an image is switched to "immutable" mode, a differencing image is created as well. As with snapshots, the parent image then becomes read-only, and the differencing image receives all the write operations. Every time the virtual machine is started, all the immutable images which are attached to it have their respective differencing image thrown away, effectively resetting the virtual machine's virtual disk with every restart. http://www.virtualbox.org/manual/ch05.html //BR, Sergey
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALx9bBpOgxV0%2BuO54ngZoRPO2RokCyGHvs%2BUa2AF-A3ujYn_VQ>