all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Stefan Reiter <s.reiter@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-qemu] pbs-restore: unref/close target block backend
Date: Wed, 24 Feb 2021 19:56:09 +0100	[thread overview]
Message-ID: <4725e9dc-cf09-4e80-3018-0f392e4f9957@proxmox.com> (raw)
In-Reply-To: <20210224133447.14692-1-s.reiter@proxmox.com>

On 24.02.21 14:34, Stefan Reiter wrote:
> Use blk_unref to drop the last reference, which will close the block
> backend and flush all caches and outstanding writes.
> 
> This is especially important for restoring to Ceph, as the userspace
> librbd caches will not be flushed if the application exits immediately,
> leading to potentially incomplete restores.
> 
> Reported-by: Eneko Lacunza <elacunza@binovo.es>
> Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
> ---
> 
> I was now able to reproduce the issue on Ceph, and this successfully fixes it
> for me. Hash sums of before and after the restore now match up.
> 
> Without this, the difference in restored images would manifest in the broken one
> simply missing some data at the back, instead just having zeroes there. This
> might also be why it's not too noticeable usually - most data would be stored in
> the earlier parts of the image, which always had enough time to be flushed.
> 
> This also brings it more in line with the code in vma.c, though we do a
> bdrv_close_all there too - I did not find that to be necessary here, as
> blk_unref already closes all attached block driver instances.
> 
>  ...ackup-pbs-restore-new-command-to-restore-from-p.patch | 9 +++++----
>  debian/patches/pve/0039-PVE-fixup-pbs-restore-API.patch  | 2 +-
>  2 files changed, 6 insertions(+), 5 deletions(-)
> 
>

applied, thanks!




      reply	other threads:[~2021-02-24 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 13:34 [pve-devel] " Stefan Reiter
2021-02-24 18:56 ` Thomas Lamprecht [this message]

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=4725e9dc-cf09-4e80-3018-0f392e4f9957@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.reiter@proxmox.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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal