From: Paolo Bonzini <pbonzini@redhat.com>
To: Mark Trumpold <Mark.Trumpold@tachyon.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] 'qemu-nbd' explicite flush to disk
Date: Thu, 13 Sep 2012 08:30:15 +0200 [thread overview]
Message-ID: <50517D77.80903@redhat.com> (raw)
In-Reply-To: <CDB9B1D21E35BB4C9E8124D05FD86BB189CA7ACE46@Etamin.tachyon.net>
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
>
>
> Confidentiality Notice: The information contained in this electronic
> e-mail and any accompanying attachment(s) is intended only for the use
> of the intended recipient and is confidential and/or privileged.
I doubt so, since this is a public mailing list.
Paolo
next prev parent reply other threads:[~2012-09-13 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 21:28 [Qemu-devel] 'qemu-nbd' explicite flush to disk Mark Trumpold
2012-09-13 6:30 ` Paolo Bonzini [this message]
2012-09-13 22:01 ` Mark Trumpold
-- strict thread matches above, loose matches on Subject: below --
2012-10-22 15:10 Mark Trumpold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50517D77.80903@redhat.com \
--to=pbonzini@redhat.com \
--cc=Mark.Trumpold@tachyon.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).