public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
* Re: [PVE-User] Fwd: Replication Job: 101-0 failed
       [not found] ` <CADzj91YrSzGGEsMYYp0vvhLasE2g4dSOFTn1ix2OuhhxZzknzw@mail.gmail.com>
@ 2022-09-16 11:28   ` Marco Gaiarin
       [not found]     ` <CADzj91Y=aCwbb+WgPFj+MbLoNd9EyhH-c-XwvpOr9nY0R+XiiQ@mail.gmail.com>
  0 siblings, 1 reply; 2+ messages in thread
From: Marco Gaiarin @ 2022-09-16 11:28 UTC (permalink / raw)
  To: Julival Santos Reis Júnior, pve-user

Mandi! Julival Santos Reis Júnior
  In chel di` si favelave...

> I'm having this same problem.
> Did you manage to solve it, or discover something?

Ops, forgot to report on list.

The message seems is generated by 'overlapping' replication tasks, eg when a
replication task does not end before the next one start. And so, is totally
harmless.


Also, but i have to test better, performance of replication can be inproved
simply by increasing the 'blocksize' parameters in the ZFS storage
configuration.

AFAI've understood, the 'blocksize' is the 'transfer unit' of a ZFS
replication operation, and so augmenting it (i'm testing 32k) can improve
performance.




^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PVE-User] Fwd: Replication Job: 101-0 failed
       [not found]     ` <CADzj91Y=aCwbb+WgPFj+MbLoNd9EyhH-c-XwvpOr9nY0R+XiiQ@mail.gmail.com>
@ 2022-09-19 19:18       ` Marco Gaiarin
  0 siblings, 0 replies; 2+ messages in thread
From: Marco Gaiarin @ 2022-09-19 19:18 UTC (permalink / raw)
  To: Julival Santos Reis Júnior, pve-user

Mandi! Julival Santos Reis Júnior
  In chel di` si favelave...

> Thanks for the feedback!

Please, don't reply personally, use the list!!!


> I had solved this problem in version 6 of proxmox.
> There was a parameter that I increased the timeout, and the system stopped
> giving these errors. But now it changed to version 7 and the problem came back.
> sending a print of the file in version 7, from the place I moved. I also read
> that the problem is solved by putting good quality SSD enterprise hard drives.

'timeout' isthe simplier consequence of other things, typically
load/iodelay.
So augmenting the timeout you are only curing the symptom, not the disease.

Try increase the blocksize (or, sure, spend more money and by good
enterprise SSD drives! ;-), instead of modifying the code for increase the
timeout...




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-09-19 19:20 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20220915150037.61E429509@prox01.portoseguro>
     [not found] ` <CADzj91YrSzGGEsMYYp0vvhLasE2g4dSOFTn1ix2OuhhxZzknzw@mail.gmail.com>
2022-09-16 11:28   ` [PVE-User] Fwd: Replication Job: 101-0 failed Marco Gaiarin
     [not found]     ` <CADzj91Y=aCwbb+WgPFj+MbLoNd9EyhH-c-XwvpOr9nY0R+XiiQ@mail.gmail.com>
2022-09-19 19:18       ` Marco Gaiarin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal