Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If the zfs command failed then the command hung. by calling maniwg.Do… #467

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

recunius
Copy link
Contributor

@recunius recunius commented Jun 3, 2022

…ne() in this case the program can exit.

No improper side effects noticed, at least for the error, "Error waiting for zfs command to finish - exit status 1: WARNING: could not send X incremental source Y is not earlier than it"

This fixes issue #466 at least for this specific ZFS error that I encountered.

…ne() in this case the program can exit.

No improper side effects noticed, at least for the error, "Error waiting for zfs command to finish - exit status 1: WARNING: could not send X incremental source Y is not earlier than it"
jdfalk added a commit to jdfalk/zfsbackup-go that referenced this pull request Nov 13, 2022
Copy link
Owner

@someone1 someone1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I appreciate your contribution though have some concerns about the proposed fix!

@@ -373,6 +373,8 @@ func Backup(pctx context.Context, jobInfo *files.JobInfo) error {
case fileBuffer <- true:
}
case <-ctx.Done():
log.AppLogger.Debugf("manifest copy: ctx.Done(): err = %v", ctx.Err())
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

concern: I'm not sure this is the correct spot for this - line 287 should trigger above should any error raise from the underlying zfs backup stream, perhaps actually we should add this to line 300 while waiting to pass along the volume?

Also looking through here, line 358 may also warrant a call to maniwg.Done()...

Perhaps a larger issue here is all the corner cases this method of sync'ing between goroutines has and addressing the TODO below on line 385.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants