From: Paolo Bonzini <pbonzini@redhat.com>
To: Mark Trumpold <markt@netqa.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, markt@tachyon.net
Subject: Re: [Qemu-devel] 'qemu-nbd' explicit flush
Date: Fri, 24 May 2013 14:10:26 +0200 [thread overview]
Message-ID: <519F58B2.50302@redhat.com> (raw)
In-Reply-To: <W4504910164140841369346311@atl4webmail30>
Il 23/05/2013 23:58, Mark Trumpold ha scritto:
> I have a working configuration using the signal approach suggested by Stefan.
>
> 'qemu-nbd.c' is patched as follows:
>
> do {
> main_loop_wait(false);
> + if (sighup_reported) {
> + sighup_reported = false;
> + bdrv_drain_all();
> + bdrv_flush_all();
> }
> } while (!sigterm_reported && (persistent || !nbd_started || nb_fds > 0));
>
> The driving script was patched as follows:
Yes, a patch along these lines would be acceptable.
> mount -o remount,ro /dev/nbd0
> blockdev --flushbufs /dev/nbd0
> + kill -HUP <qemu-nbd process id>
>
> I needed to retain 'blockdev --flushbufs' for things to work. Seems
> the 'bdrv_flush_all' is flushing what is being missed by the blockdev
> flush. I did not go back an retest with 'fsync' or other approaches I
> had tried before.
Right. That said, I think a newer kernel would do what you want.
Perhaps you can look at the actual patches that went into 3.9 and
backport them.
Paolo
next prev parent reply other threads:[~2013-05-24 12:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 21:58 [Qemu-devel] 'qemu-nbd' explicit flush Mark Trumpold
2013-05-24 9:05 ` Stefan Hajnoczi
2013-05-25 17:42 ` Mark Trumpold
2013-05-27 12:36 ` Stefan Hajnoczi
2013-05-24 12:10 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-28 18:00 Mark Trumpold
2013-05-29 7:42 ` Stefan Hajnoczi
2013-05-29 15:29 ` Mark Trumpold
2013-06-07 14:00 ` Mark Trumpold
2013-05-23 23:35 Mark Trumpold
2013-05-24 9:06 ` Stefan Hajnoczi
2013-05-22 16:10 Mark Trumpold
2013-05-21 20:01 Mark Trumpold
2013-05-22 9:47 ` Stefan Hajnoczi
2013-05-22 11:07 ` Paolo Bonzini
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=519F58B2.50302@redhat.com \
--to=pbonzini@redhat.com \
--cc=markt@netqa.com \
--cc=markt@tachyon.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.