Re: zfs replication tool

From: Julien Cigar <julien_at_perdition.city>
Date: Fri, 23 Sep 2022 09:52:15 UTC
On Fri, Sep 23, 2022 at 11:25:35AM +0200, Julien Cigar wrote:
> On Fri, Sep 23, 2022 at 01:57:54AM -0700, David Christensen wrote:
> > On 9/23/22 01:03, Julien Cigar wrote:
> > 
> > > I'm still getting replication errors with zrepl on my test installation,
> > > see https://github.com/zrepl/zrepl/issues/631 for details. The initial
> > > transfer works, but after that I'm getting weird "cannot receive
> > > incremental stream: destination ..." messages, despite all snapshots
> > > have been well preserved on both side
> > 
> > 
> > Does zrepl script the zfs(8) command or does zrepl make ZFS API calls?
> 
> I *think* raw zfs(8) is used, it's written in Go
> 
> > 
> > 
> > Does zrepl have xtrace, verbose, debug, etc., options?
> > 
> 
> yes, but I haven't found an explanation why some snapshots aren't
> transferred
> 
> > 
> > I wrote homebrew scripts to automate ZFS replication and I saw that error
> > message many times in the past.  The solution was to add the '-F' option to
> > the 'zfs receive' commands.  Is there a way to do this with zrepl?
> > 
> 
> I'm not sure, and even if there was the possibility I'd like to
> understand why it is needed as all snapshots are there. Rollback to the
> most recent snapshot shouldn't be necessary in this case..

mmh could it be because target dataset is mounted and because of atime
(or ...) issues...?

> 
> > 
> > David
> > 
> 
> -- 
> Julien Cigar
> PGP fingerprint: EEF9 F697 4B68 D275 7B11  6A25 B2BB 3710 A204 23C0
> 
> No trees were killed in the creation of this message.
> However, many electrons were terribly inconvenienced.



-- 
Julien Cigar
PGP fingerprint: EEF9 F697 4B68 D275 7B11  6A25 B2BB 3710 A204 23C0

No trees were killed in the creation of this message.
However, many electrons were terribly inconvenienced.