From: Stefan Reiter <s.reiter@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>, Graeme Seaton <lists@graemes.com>
Subject: Re: [pbs-devel] Template backup failure in 0.8-13
Date: Thu, 3 Sep 2020 11:18:00 +0200 [thread overview]
Message-ID: <7e4e9d26-dfbf-2563-a33b-9919d414619e@proxmox.com> (raw)
In-Reply-To: <beff72e2-1e71-8e92-fedf-2006458b75ac@graemes.com>
On 9/2/20 11:41 PM, Graeme Seaton wrote:
> Thanks Stefan. Every developers favourite question :-) - any indication
> of when this might be released to the test (non-enterprise) repo?
Every users favourite answer: As soon as it's ready ;) (but probably not
too long)
We're already testing the 5.1 build internally, but as it entails a new
upstream version this takes a bit longer than usual.
~ Stefan
>
> Regards,
>
> Graeme
>
> On 02/09/2020 08:54, Stefan Reiter wrote:
>> On 9/2/20 9:07 AM, Graeme Seaton wrote:
>>> Hi,
>>>
>>> Receiving the following error message with 0.8-13:
>>>
>>> INFO: Starting Backup of VM 10019 (qemu)
>>> INFO: Backup started at 2020-09-02 00:47:01
>>> INFO: status = stopped
>>> INFO: backup mode: stop
>>> INFO: ionice priority: 7
>>> INFO: VM Name: ubnt1604tmpl
>>> INFO: include disk 'scsi0' 'tank0:base-10019-disk-0' 2252M
>>> INFO: creating Proxmox Backup Server archive
>>> 'vm/10019/2020-09-01T23:47:01Z'
>>> INFO: starting kvm to execute backup task
>>> generating cloud-init ISO
>>> ERROR: VM 10019 qmp command 'backup' failed - Node 'drive-scsi0'
>>> is read only
>>> INFO: stopping kvm after backup task
>>> trying to acquire lock...
>>> OK
>>> ERROR: Backup of VM 10019 failed - VM 10019 qmp command 'backup'
>>> failed - Node 'drive-scsi0' is read only
>>> INFO: Failed at 2020-09-02 00:47:02
>>>
>>
>> Hi!
>>
>> The fix for this is already in our git[0] and will be available in an
>> upcoming pve-qemu-kvm package (presumable QEMU 5.1 based).
>>
>> ~ Stefan
>>
>> [0]
>> https://git.proxmox.com/?p=pve-qemu.git;a=commit;h=a5feeebc519cdbe7225652e1d2faefa90e39cca3
>>
>>
>>> All clients and server are on latest versions.
>>>
>>> Regards,
>>>
>>> Graeme
>>>
>>>
>>>
>>> _______________________________________________
>>> pbs-devel mailing list
>>> pbs-devel@lists.proxmox.com
>>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
>>>
>>
>
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2020-09-03 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 7:07 Graeme Seaton
2020-09-02 7:54 ` Stefan Reiter
2020-09-02 21:41 ` Graeme Seaton
2020-09-03 9:18 ` Stefan Reiter [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=7e4e9d26-dfbf-2563-a33b-9919d414619e@proxmox.com \
--to=s.reiter@proxmox.com \
--cc=lists@graemes.com \
--cc=pbs-devel@lists.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