From: "Stéphane Caminade" <stephane.caminade@ias.u-psud.fr>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] backup to PBS: unable to acquire lock on snapshot directory
Date: Thu, 7 Oct 2021 12:09:25 +0200 [thread overview]
Message-ID: <46ec5de2-dfeb-2ea3-a622-e88da9de1b12@ias.u-psud.fr> (raw)
In-Reply-To: <93f43c26-001b-13f7-ef13-a4e484f7a0d3@ias.u-psud.fr>
Hi,
No one has encountered a similar problem?
Cheers,
Stephane
Le 29/09/2021 à 17:34, Stephane Caminade a écrit :
> Hello,
>
> I have a question regarding a problem I encounter when running backups
> with PBS.
>
> *Context*:
>
> A cluster of 9 Proxmox nodes running 84 VM, and backing up to a remote
> PBS
>
> *Versions*:
>
> pve-manager/6.4-13/9f411e79 (running kernel: 5.4.128-1-pve) with
> proxmox-backup-client 1.1.12-1
>
> proxmox-backup-server 2.0.10-1 running version: 2.0.9
>
> *Problem*:
>
> Regularly, some of my VMs (3 regularly, and others randomly - or I
> have not yet determined the common factor -) will fail their backup
> with the following error (example of a regular failing one, but
> similar message for all the failed backups):
>
> /ERROR: Backup of VM 297 failed - VM 297 qmp command 'backup' failed -
> backup connect failed: command error: unable to acquire lock on
> snapshot directory
> "/mnt/inf-proxmox-bkp/PBS-STORAGE/vm/297/2021-09-29T10:01:43Z" - base
> snapshot is already locked by another operation/
>
>
> Any pointers as to where I could look for the source of this problem?
>
> Best regards,
>
> Stephane
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
next prev parent reply other threads:[~2021-10-07 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 15:34 Stephane Caminade
2021-10-07 10:09 ` Stéphane Caminade [this message]
2021-10-08 5:02 Dietmar Maurer
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=46ec5de2-dfeb-2ea3-a622-e88da9de1b12@ias.u-psud.fr \
--to=stephane.caminade@ias.u-psud.fr \
--cc=pve-user@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 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.