Repository navigation
cannot receive incremental stream #316
Unanswered
velocity08
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi All
im running into this mount issue even though the target dataset is unmounted.
even after running the correct command to include --clear-mountpoint we are still seeing this issue.
# zfs-autobackup -v --clear-mountpoint --strip-path=1 newpool goliath2before i look at using either --rollback (or --force) i would like to understand what the implications may be.
im currently working on migrating a pool to new disks.
there is a bit of data about 60 TB to move and all is done aside from getting the error on the destination parent pool/ dataset.
If we do a
forceorrollback(there are only old snapshots pre dating zfs_autobackup on the destination pool, what sort of behavior should we expect from the process?see snapshot comparison list below.
what i want to avoid is loosing the entire destination pool and forcing a resync from scratch as this will mean a number of days lost to resync again.
any assistance in resolving this issue would be greatly appreciated.
""Cheers
G
All reactions