From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:47435) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TQJek-00088n-5b for qemu-devel@nongnu.org; Mon, 22 Oct 2012 11:11:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TQJed-0003Pr-E2 for qemu-devel@nongnu.org; Mon, 22 Oct 2012 11:11:06 -0400 Received: from atl4mhob08.myregisteredsite.com ([209.17.115.46]:37119) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TQJed-0003PQ-9D for qemu-devel@nongnu.org; Mon, 22 Oct 2012 11:10:59 -0400 Received: from mailpod.hostingplatform.com (mail.networksolutionsemail.com [205.178.146.50]) by atl4mhob08.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id q9MFAvsN028097 for ; Mon, 22 Oct 2012 11:10:57 -0400 Date: Mon, 22 Oct 2012 08:10:45 -0700 From: Mark Trumpold Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: Re: [Qemu-devel] 'qemu-nbd' explicite flush to disk List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: paolo.bonzini@gmail.com Cc: qemu-devel@nongnu.org Paolo, Please recall you had sent me the link below to a kernel patch to allow 'qemu-nbd' to flush to disk. The patch was applied with good success. However, recent testing indicates that filesystem corruption issue I am seeing seems to be tied to large (>500mbyte) filesystem writes. I also observe the kernel 'flush' thread approaching 100% cpu at times, and i/o wait % as reported by 'top' increasing sharply during the copy/write. Was wondering if perhaps there are any special kernel config options that I may be missing for 'nbd', or any other information that might help. Best regards, Mark Trumpold >-----Original Message----- >From: Paolo Bonzini [mailto:paolo.bonzini@gmail.com] On Behalf Of Paolo >Bonzini >Sent: Wednesday, September 12, 2012 11:30 PM >To: Mark Trumpold >Cc: qemu-devel@nongnu.org >Subject: Re: 'qemu-nbd' explicite flush to disk >Il 12/09/2012 23:28, Mark Trumpold ha scritto: >> So, I've been experimenting with 'qemu-nbd --cache=writeback ..' >> This nicely eliminates the 'checkpoint' issue; however, I have as >> yet been unable to explicitely flush things to disk -- which I would >>like to >> do just before a 'nilfs' snapshot. >The Linux kernel driver for NBD does not support flushes. Patches were >sent to the maintainer, but he never applied them. >You can get them at >http://thread.gmane.org/gmane.linux.drivers.nbd.general/1108 and try >them. >> Subsequently I've been trying to call 'bdrv_co_flush(bs)' directly, but >>I can't >figure out how to dereference 'bs' for the call. >> >> I'm probably out in the weeds on this one. >> Any guidance would be greatly appreciated. >> >> I am running: >> qemu-1.2.0 >> linux kernel 3.3.1 >> >> Thank you, >> Mark Trumpold