From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:40596) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QFSNh-0006ml-G1 for qemu-devel@nongnu.org; Thu, 28 Apr 2011 10:39:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QFSNg-0000QO-GY for qemu-devel@nongnu.org; Thu, 28 Apr 2011 10:39:49 -0400 Received: from mx1.redhat.com ([209.132.183.28]:13577) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QFSNg-0000QH-8D for qemu-devel@nongnu.org; Thu, 28 Apr 2011 10:39:48 -0400 Message-ID: <4DB97CCC.2010601@redhat.com> Date: Thu, 28 Apr 2011 16:42:20 +0200 From: Kevin Wolf MIME-Version: 1.0 References: <1303136821-13333-1-git-send-email-Jes.Sorensen@redhat.com> <1303136821-13333-2-git-send-email-Jes.Sorensen@redhat.com> <20110427120520.74e348d9@doriath> <4DB969E5.2060501@redhat.com> <4DB96E9E.6020300@redhat.com> <4DB96FA9.5000202@redhat.com> In-Reply-To: <4DB96FA9.5000202@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v2 1/1] Add QMP bits for blockdev-snapshot-sync. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jes Sorensen Cc: Markus Armbruster , qemu-devel@nongnu.org, Luiz Capitulino Am 28.04.2011 15:46, schrieb Jes Sorensen: > On 04/28/11 15:41, Kevin Wolf wrote: >>>> Finally, what's the expect behavior when -snapshot is used? I'm getting >>>>>> this: >>>>>> >>>>>> (qemu) snapshot_blkdev ide0-hd0 snap-test >>>>>> Could not open '/tmp/vl.6w8YXA' >>>>>> (qemu) >>>> >>>> What type of file system is your /tmp? You need to provide full path to >>>> the snapshot file if you don't want it created next to where your qemu >>>> binary is being executed. >> I think the problem is that this is a temporary file, i.e. unlinked >> directly after it has been opened. Trying to reopen a deleted file is a >> bad idea. > > True, but if /tmp is tmpfs, it isn't possible to open things O_DIRECT, > which could also be the source of the problem here. Not really, -snapshot is very clearly the problem here. Note that what's failing here is not opening the new snapshot but the old temporary image created by -snapshot. Kevin