From owner-freebsd-hackers@FreeBSD.ORG  Thu Aug  8 13:57:30 2013
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id A889F6C7
 for <freebsd-hackers@freebsd.org>; Thu,  8 Aug 2013 13:57:30 +0000 (UTC)
 (envelope-from slobodyanyuk.sergey@gmail.com)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com
 [IPv6:2a00:1450:400c:c05::233])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 40B5B2495
 for <freebsd-hackers@freebsd.org>; Thu,  8 Aug 2013 13:57:30 +0000 (UTC)
Received: by mail-wi0-f179.google.com with SMTP id hr7so603304wib.0
 for <freebsd-hackers@freebsd.org>; Thu, 08 Aug 2013 06:57:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:date:message-id:subject:from:to:cc:content-type;
 bh=C26ZbdMTE84wIZRL5ffQTfWxkKHeE3RHmCTjhARmEpU=;
 b=lR34BlOgPYSbq1Lffqmrf8Ae3R3OccCHisxrP/674uNcBIX+e6w350PXus5X5zXThz
 eTLuOy9qD0ef/9sjNDf3HaKvwPTXUXBqdWhP2g5R0Su/mL3AZnDeMTF84yBp6iXxwlNg
 R399W1K8cJnpL6g/ke7lwjeSQftVOUqBUMMtQ2SA22ZyhOsNkgiEpwSVcGrgAiPhCKqu
 ZTj4lXzmkS1xc/b+xz78IMD4o9WTqBsVvneT00jSZWX7VMsKfOzYiEIlHtXmIpZbq/06
 DKDu33lIqRQxJbY0sKQDwXAsxpBcwmzkXag+2zdCHha3k6O/pKxxBZhU1ngyjVxL6Xz/
 p9sw==
MIME-Version: 1.0
X-Received: by 10.180.212.112 with SMTP id nj16mr5199574wic.31.1375970248534; 
 Thu, 08 Aug 2013 06:57:28 -0700 (PDT)
Sender: slobodyanyuk.sergey@gmail.com
Received: by 10.194.61.52 with HTTP; Thu, 8 Aug 2013 06:57:28 -0700 (PDT)
Date: Thu, 8 Aug 2013 16:57:28 +0300
X-Google-Sender-Auth: ECVUpwNl2yI1KSObZBwXEnF9zTA
Message-ID: <CALx9bBpOgxV0+uO54ngZoRPO2RokCyGHvs+Ua2AF-A3ujYn_VQ@mail.gmail.com>
Subject: Re: After the FreeBSD VM crash, file system in VM got rolled back to
 some old previous state causing data loss
From: Sergey Slobodyanyuk <ssv.lkml@gmail.com>
To: yuri@rawbw.com
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: freebsd-hackers@freebsd.org
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 13:57:30 -0000

>
> 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