From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:40573) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TR3AL-0000QZ-S6 for qemu-devel@nongnu.org; Wed, 24 Oct 2012 11:46:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TR3AF-0003ed-MG for qemu-devel@nongnu.org; Wed, 24 Oct 2012 11:46:45 -0400 Received: from mail-pb0-f45.google.com ([209.85.160.45]:56041) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TR3AF-0003eH-CB for qemu-devel@nongnu.org; Wed, 24 Oct 2012 11:46:39 -0400 Received: by mail-pb0-f45.google.com with SMTP id rp2so1239964pbb.4 for ; Wed, 24 Oct 2012 08:46:38 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <50880D57.3000307@gnu.org> Date: Wed, 24 Oct 2012 17:46:31 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] FW: 'qemu-nbd' explicite flush to disk List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mark Trumpold Cc: paolo.bonzini@gmail.com, qemu-devel@nongnu.org Il 23/10/2012 04:50, Mark Trumpold ha scritto: > Hello Paolo, > > Before anyone expends any cycles on my last message, I have new > information. > > Today I was able to eliminate the file corruption issue by doing a > 'blockdev --flushbufs' prior to taking a snapshot. Makes sense. Even better, you could do fsfreeze -f before and fsfreeze -u afterwards. Paolo