From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Marco Gaiarin <gaio@lilliput.linux.it>
Subject: Re: [PVE-User] Replication failed, got tiemout?
Date: Tue, 5 Apr 2022 09:26:33 +0200 [thread overview]
Message-ID: <3c6d1ee7-991c-50af-7427-f152ccdbe869@proxmox.com> (raw)
In-Reply-To: <q5mqhi-sod.ln1@hermione.lilliput.linux.it>
Is the pool using HDDs? Could be that other things are happening at that moment and HDDs are really not great for random IO. I had that as well sometimes. Went away when I changed to SSDs. A dedicated special device vdev on (mirrored) SSDs should also improve the situation while not needing as many SSDs. Snapshots are a metadata operation. See [0] or `man zpoolconcepts` and look for "special device"
Cheers Aaron
[0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_zfs_special_device
On 4/4/22 10:17, Marco Gaiarin wrote:
>> New installed PVE6 2-node cluster, totally unloaded; only some test VMs that
>> are replicated between the two nodes, conected via a 10G direct cable.
>> Sometimes we get:
>> command 'zfs snapshot rpool/data/vm-103-disk-0@__replicate_103-0_1648656014__' failed: got timeout
>> What can be?! Thanks.
>
> We catch a log on /var/log/pve/replicate/, but seems, at least to me, not
> providing some more clue:
>
> 2022-04-02 14:00:14 103-0: start replication job
> 2022-04-02 14:00:14 103-0: guest => VM 103, running => 5167
> 2022-04-02 14:00:14 103-0: volumes => local-zfs:vm-103-disk-0
> 2022-04-02 14:00:16 103-0: create snapshot '__replicate_103-0_1648900814__' on local-zfs:vm-103-disk-0
> 2022-04-02 14:00:21 103-0: end replication job with error: command 'zfs snapshot rpool/data/vm-103-disk-0@__replicate_103-0_1648900814__' failed: got timeout
>
> I'm seeking info. Thanks.
>
next prev parent reply other threads:[~2022-04-05 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 16:24 Marco Gaiarin
2022-04-04 8:17 ` Marco Gaiarin
2022-04-05 7:26 ` Aaron Lauterer [this message]
2022-04-05 15:55 ` Marco Gaiarin
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=3c6d1ee7-991c-50af-7427-f152ccdbe869@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=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 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.