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
zfs send -R fails, but subsequent -I succeeds #7576
Comments
|
Not entirely surprisingly, both 0.7.9 and git tip (as of 1a5b96b) as receivers will die identically. |
|
This is as stupid as I thought it was - it's trying to report it can't set the checksum property on the dataset and dies with an internal error when trying to do that. I've now got a core file with some variables optimized out in it if anyone cares to look. I'll probably try to look at it tomorrow since I suspect #7755's backtrace will be identical. |
This change modifies how 'checksum' and 'dedup' properties are verified in zfs_check_settable() handling the case where they are explicitly inherited in the dataset hierarchy when receiving a recursive send stream. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Tom Caputi <tcaputi@datto.com> Signed-off-by: loli10K <ezomori.nozomu@gmail.com> Closes #7755 Closes #7576 Closes #7757
This change modifies how 'checksum' and 'dedup' properties are verified in zfs_check_settable() handling the case where they are explicitly inherited in the dataset hierarchy when receiving a recursive send stream. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Tom Caputi <tcaputi@datto.com> Signed-off-by: loli10K <ezomori.nozomu@gmail.com> Closes openzfs#7755 Closes openzfs#7576 Closes openzfs#7757
This change modifies how 'checksum' and 'dedup' properties are verified in zfs_check_settable() handling the case where they are explicitly inherited in the dataset hierarchy when receiving a recursive send stream. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Tom Caputi <tcaputi@datto.com> Signed-off-by: loli10K <ezomori.nozomu@gmail.com> Closes openzfs#7755 Closes openzfs#7576 Closes openzfs#7757 Requires-spl: refs/pull/707/head
This change modifies how 'checksum' and 'dedup' properties are verified in zfs_check_settable() handling the case where they are explicitly inherited in the dataset hierarchy when receiving a recursive send stream. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Tom Caputi <tcaputi@datto.com> Signed-off-by: loli10K <ezomori.nozomu@gmail.com> Closes openzfs#7755 Closes openzfs#7576 Closes openzfs#7757 Requires-spl: refs/pull/707/head
This change modifies how 'checksum' and 'dedup' properties are verified in zfs_check_settable() handling the case where they are explicitly inherited in the dataset hierarchy when receiving a recursive send stream. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Tom Caputi <tcaputi@datto.com> Signed-off-by: loli10K <ezomori.nozomu@gmail.com> Closes openzfs#7755 Closes openzfs#7576 Closes openzfs#7757 Requires-spl: refs/pull/707/head
This change modifies how 'checksum' and 'dedup' properties are verified in zfs_check_settable() handling the case where they are explicitly inherited in the dataset hierarchy when receiving a recursive send stream. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Tom Caputi <tcaputi@datto.com> Signed-off-by: loli10K <ezomori.nozomu@gmail.com> Closes openzfs#7755 Closes openzfs#7576 Closes openzfs#7757
This change modifies how 'checksum' and 'dedup' properties are verified in zfs_check_settable() handling the case where they are explicitly inherited in the dataset hierarchy when receiving a recursive send stream. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Tom Caputi <tcaputi@datto.com> Signed-off-by: loli10K <ezomori.nozomu@gmail.com> Closes openzfs#7755 Closes openzfs#7576 Closes openzfs#7757
System information
Describe the problem you're observing
Wanted to test migrating a dataset over to using
checksum=edonr, so I set up a datasetdst/testbedwithchecksum=edonron a pool withfeature@edonr=enabled, and then ran:zfs send -Re source/dataset@lastsnap | zfs recv -v -x checksum -e dst/testbedIt gets through the oldest snapshot, "one-and-done", then apparently while transferring the next snapshot, "zfs-auto-snap_weekly-2016-11-06-1147", it dies with:
At that point,
zfs list -t all -r dst/testbedsays:Strangely, if I then run
zfs send -Re -I dst/testbed/3ds_sd@{one-and-done,lastsnap} | zfs recv -v -x checksum -e dst/testbedor just
zfs send -Re -i dst/testbed/3ds_sd@{one-and-done,zfs-auto-snap_weekly-2016-11-06-1147} | zfs recv -v -x checksum -e dst/testbedit will progress to completion unremarkably.
Removing the -e flag from send doesn't affect the initial failure.
I tried using -s to make an easily resumable failure, but there's no receive-resume-token generated when receive aborts. Oh well.
The text was updated successfully, but these errors were encountered: