patrick/zfs_autobackup
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated Problems (markdown)

DatuX
2022-02-24 13:34:00 +01:00
parent 9baab01072
commit 30cac035e1
1 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
Problems.md

@ -1,32 +1,34 @@
## Common problems you might encounter ## Common problems you might encounter
> It keeps asking for my SSH password ## It keeps asking for my SSH password
You forgot to setup automatic login via SSH keys, look in the example how to do this. You forgot to setup automatic login via SSH keys, look in the example how to do this.
> cannot receive incremental stream: invalid backup stream ## cannot receive incremental stream: invalid backup stream
This usually means you've created a new snapshot on the target side during a backup. If you restart zfs-autobackup, it will automaticly abort the invalid partially received snapshot and start over. This usually means you've created a new snapshot on the target side during a backup. If you restart zfs-autobackup, it will automaticly abort the invalid partially received snapshot and start over.
> cannot receive incremental stream: destination has been modified since most recent snapshot ## cannot receive incremental stream: destination has been modified since most recent snapshot
This means files have been modified on the target side somehow. This means files have been modified on the target side somehow.
You can use --rollback to automaticly rollback such changes. Also try destroying the target dataset and using --clear-mountpoint on the next run. This way it wont get mounted. * You can use `--rollback` to automatically rollback such changes.
* Try using `--clear-mountpoint` on the next run, so the filesystems wont be mounted. Mounting will sometimes lead to changes since it might have to create mount-point directories in filesystems. `--clear-mountpoint` only affects newly received filesystems, so you might have to set the `canmount=noauto` property on existing filesystems yourself.
* Set the `readonly` property of the target filesystem to on. This prevents changes on the target side. Note that readonly prevents changes to the CONTENTS of the dataset directly. Its still possible to receive new datasets and manipulate properties etc.
> internal error: Invalid argument ## internal error: Invalid argument
In some cases (Linux -> FreeBSD) this means certain properties are not fully supported on the target system. In some cases (Linux -> FreeBSD) this means certain properties are not fully supported on the target system.
Try using something like: --filter-properties xattr or --ignore-transfer-errors. Try using something like: --filter-properties xattr or --ignore-transfer-errors.
> zfs receive fails, but snapshot seems to be received successful. ## zfs receive fails, but snapshot seems to be received successful.
This happens if you transfer between different Operating systems/zfs versions or feature sets. This happens if you transfer between different Operating systems/zfs versions or feature sets.
Try using the --ignore-transfer-errors option. This will ignore the error. It will still check if the snapshot is actually received correctly. Try using the --ignore-transfer-errors option. This will ignore the error. It will still check if the snapshot is actually received correctly.
> cannot receive incremental stream: kernel modules must be upgraded to receive this stream. ## cannot receive incremental stream: kernel modules must be upgraded to receive this stream.
This happens if you forget to use --encrypt, while the target datasets are already encrypted. (Very strange error message indeed) This happens if you forget to use --encrypt, while the target datasets are already encrypted. (Very strange error message indeed)