From 71f3cb94a42d49dd2c5892c00b4327805d19ad83 Mon Sep 17 00:00:00 2001 From: DatuX Date: Wed, 27 Sep 2023 23:13:29 +0200 Subject: [PATCH] Updated Problems (markdown) --- Problems.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/Problems.md b/Problems.md index 0f5de45..577d3c1 100644 --- a/Problems.md +++ b/Problems.md @@ -4,17 +4,21 @@ You forgot to setup automatic login via SSH keys, look in the example how to do this. -## "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. ## "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 your target dataset has been modified somehow. + +Make sure you read how [[Mounting]] works. * You can use `--rollback` to automatically rollback such changes. - * Try using `--clear-mountpoint`, 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 target filesystems yourself. * Set the `readonly` property of the target filesystem to on. This prevents all modifications 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. + * Always use `--clear-mountpoint`, see [[Mounting]] + + +## "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. ## "internal error: Invalid argument"