From: Marco Gaiarin <gaio@lilliput.linux.it>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Overlapping replicas?!
Date: Mon, 22 Aug 2022 09:51:51 +0200 [thread overview]
Message-ID: <l5pbti-pif.ln1@hermione.lilliput.linux.it> (raw)
We got sporadically errors/warnings like:
command 'zfs snapshot rpool-data/vm-127-disk-0@__replicate_127-0_1659141017__' failed: got timeout
digging into it, seems that happen when replicas 'overlap', eg the scheduled
replica start when the previous scheduled replica have not just ended.
Could be? Replicas can be a bit smarter and not warn about this?
Thanks.
--
Vedi, è che in gastronomia ci sono quello che mangia e quello che cucina.
Nella nostra politica, quello che cucina, manca??? (Emanuele Pucciarelli)
reply other threads:[~2022-08-22 18:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=l5pbti-pif.ln1@hermione.lilliput.linux.it \
--to=gaio@lilliput.linux.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox