From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Eneko Lacunza <elacunza@binovo.es>,
Stefan Reiter <s.reiter@proxmox.com>,
pve-user@lists.proxmox.com
Subject: Re: [PVE-User] PBS backup/restore issue
Date: Wed, 24 Feb 2021 20:03:46 +0100 [thread overview]
Message-ID: <06a2bbdd-8496-14b0-472d-ce74c59abbcb@proxmox.com> (raw)
In-Reply-To: <6120d3f8-67c8-873f-164c-1913c2016a54@binovo.es>
Hi!
On 24.02.21 12:53, Eneko Lacunza wrote:
> El 24/2/21 a las 11:34, Stefan Reiter escribió:
>> On 2/23/21 8:46 AM, Eneko Lacunza wrote:
>>> Yesterday I hit a problem with PBS. My sequence of actions was:
>>>
>>> 1.a Install debian 10 VM (updated to latest, only system utilities and SSH server)
>>> 1.b Add SSH access key to root
>>> 1.c Shutdown VM
>>> 1.d Backup to PBS and to NFS vía regular backup.
>>> 1.e Start VM and install various packages - all OK.
>>> 1.f Stop VM
>>>
>>> 2.a Restore VM from PBS backup
>>> 2.b Start VM and install various packages - apt complains about no newline in linux-image-amd64 file manifest, can't install new packages.
>>> 2.c Stop VM
>>>
>>> 3.a Restore VM from NFS regular backup
>>> 3.b Start VM and install various packages - all OK.
>>>
[snip]
> My original restores were to a ceph storage (r2 on HDD with SSD journal/DB). So i have restored again both, to that ceph storage:
[snip]
>
> Hope this info helps you to replicate the issue.
FYI: Stefan could replicate it and send a patch[0] which is included now.
It boiled down to caches not being flushed to disk for storage attached through
user-space libraries (vs. kernel) by QEMU in the PBS restore case.
In your case you probably do not have the "KRBD" checkbox ticked for the Ceph
storage entry in PVE, so the user-space librbd is used for accessing that storage
through QEMU, where this issue then hit on restore.
If you want to try the fix out, there's a new QEMU package available on pvetest:
http://download.proxmox.com/debian/pve/dists/buster/pvetest/binary-amd64/pve-qemu-kvm_5.2.0-2_amd64.deb
sha256sum: 6a086e0b669447f0b8a7899f9194a26785e6b0070f3dec1be4f95067bc707c7a
cheers,
Thomas
[0]: https://lists.proxmox.com/pipermail/pve-devel/2021-February/047131.html
next prev parent reply other threads:[~2021-02-24 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c390959d-e5b5-9a95-770c-ff6853357cbe@binovo.es>
2021-02-24 10:34 ` Stefan Reiter
[not found] ` <6120d3f8-67c8-873f-164c-1913c2016a54@binovo.es>
2021-02-24 19:03 ` Thomas Lamprecht [this message]
[not found] <mailman.28.1614066435.365.pve-user@lists.proxmox.com>
2021-02-23 8:06 ` Dietmar Maurer
2021-02-24 9:44 ` mj
[not found] ` <mailman.44.1614161184.365.pve-user@lists.proxmox.com>
2021-06-13 18:36 ` proxmox
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=06a2bbdd-8496-14b0-472d-ce74c59abbcb@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=elacunza@binovo.es \
--cc=pve-user@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox