[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] 'qemu-nbd' explicite flush to disk
From: |
Mark Trumpold |
Subject: |
Re: [Qemu-devel] 'qemu-nbd' explicite flush to disk |
Date: |
Thu, 13 Sep 2012 15:01:40 -0700 |
Paolo,
Awesome!!! I just tried your patch, and it works beautifully.
I've been struggling with the lack of '--cache=writeback' for
months now with many work-arounds/kludges.
Thank you again for responding.
Qemu rocks!
Best regards,
Mark Trumpold
> -----Original Message-----
> From: Paolo Bonzini [mailto:address@hidden On Behalf Of Paolo
> Bonzini
> Sent: Wednesday, September 12, 2012 11:30 PM
> To: Mark Trumpold
> Cc: address@hidden
> 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
> >
> >
> > 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
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. If you and we have a
confidentiality agreement or other non-disclosure obligations between us, this
Notice shall be deemed to mark and identify the content of this email and any
attachments as confidential and proprietary. If any reader of this
communication is not the intended recipient, unauthorized use, disclosure or
copying is strictly prohibited, and may be unlawful. If you have received this
communication in error, please immediately notify the sender by return e-mail,
and delete the original message and all copies from your system. Thank you.
IRS Circular 230 Disclosure: To ensure compliance with requirements imposed by
the IRS, please be advised that any U.S. federal tax advice contained in this
communication (including any attachments) is not intended or written to be used
or relied upon, and cannot be used or relied upon, for the purpose of (i)
avoiding penalties under the Internal Revenue Code, or (ii) promoting,
marketing or recommending to another party any transaction or matter addressed
herein.
E-mail is susceptible to data corruption, interception, unauthorized amendment,
tampering and viruses, and we only send and receive e-mails on the basis that
we are not liable for any such corruption, interception, amendment, tampering
or viruses or any consequences thereof.