Re: After the FreeBSD VM crash, file system in VM got rolled back to some old previous state causing data loss
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 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: After the FreeBSD VM crash, file system in VM got rolled back to some old previous state causing data loss
I hit this unexpected problem: my host had an ungraceful shutdown while FreeBSD 9.1 STABLE was running in the VirtualBox VM. After reboot of the host and VM, local ufs file system was missing all recent updates for at least 20 hours (!!!) My question is, how is this possible? Is this related to journaled soft-updates which were enabled in VM? not possible in FreeBSD with UFS. but if you run virtualbox under linux i cannot say much... ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: After the FreeBSD VM crash, file system in VM got rolled back to some old previous state causing data loss
Virtualbox is very aggressive about caching writes. This is how it achieves its perceived speed. I wouldn't expect to see this happen on real hardware. I might have to try this out though and see if I can reproduce it reliably. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: After the FreeBSD VM crash, file system in VM got rolled back to some old previous state causing data loss
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 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
After the FreeBSD VM crash, file system in VM got rolled back to some old previous state causing data loss
I hit this unexpected problem: my host had an ungraceful shutdown while FreeBSD 9.1 STABLE was running in the VirtualBox VM. After reboot of the host and VM, local ufs file system was missing all recent updates for at least 20 hours (!!!) My question is, how is this possible? Is this related to journaled soft-updates which were enabled in VM? Losing data looks like a critical issue. I had a backup outside VM so no real data loss for me, but this is bad. Fedora VM, that was shut down in the same way didn't suffer from the same issue (local ext4). Host shutdown was caused by the frozen Xorg, I had to kill it and reboot. VirtualBox processes got killed in the process. Yuri ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
