From owner-freebsd-fs@freebsd.org Sat Feb 24 12:36:56 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97B97F0ABDE for ; Sat, 24 Feb 2018 12:36:56 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EF6D67FFC2 for ; Sat, 24 Feb 2018 12:36:55 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from moby.local ([79.107.33.9]) by mail.gmx.com (mrgmx103 [212.227.17.174]) with ESMTPSA (Nemesis) id 0Mhhr5-1f2xKF3aWR-00Mw8Q for ; Sat, 24 Feb 2018 13:36:49 +0100 From: Nikos Vassiliadis Subject: cannot receive incremental stream: destination foo has been modified To: FreeBSD Filesystems Message-ID: Date: Sat, 24 Feb 2018 14:36:41 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:Wj2Ys8Qf993lVMA5yQP8zZRAqAjMU7oUgsgO7HrlgiAiVC80lTd 1TpDWslDE0n9uQDeIrf5G6Ug+OtxEKbPehXhabEsB50AEk6rxTCNpK7oIgB2u5h41R2i9Ts vQsTYt1EjdaQLTWjHPrdAML+2DJ33IQgHCAD+G2ejq40vIzYvCQtkJ1zj7nd/H8i3vvV4YP 4Pf9T/bc6pZNM22Jf9pFw== X-UI-Out-Filterresults: notjunk:1;V01:K0:d55N3l/kG8g=:jAVd7S+gCIvIjQd8X7Z76w DiVMUVtQ1g5tmRtb2LzXAVk667xuuaNUSa/3OJVq9+/9F7wMeRhd9DRL40PGvYrFDzb2lCFRa RFwINVqkrHHYl9s+VN1XmXnqF9TJ789gFp9QUQsdm4+A8uekAtQTPYUCCt547gr/9yEgs9hq3 dw53C++UZQ2kngr7bdw6y9u7oxeB+eHwEb8Ns9oEFXlZKqCbKfkGWGE3xoCvIyRJ5GAMM4bbR +LVrVvy5rn8te9FcAQY+xZ/d+l6hNQ0C0rDe1ndMsYUu4seO2KTYASnJO/HvCLfLNylOvWKdz OOjz/93pTJNzx/GlHRLEy4YN+YCVUWCowxILhvaL5okMHrZhj7MXKMu0EB7GPjSWvfYVL7vBY K/CAUQdsmuNaShOPIb30y13PGuia9AmJmeheUDICH4DAbseRWaxanZGAHNTuQk4BktrOCspRq s8emmzd6MEt5YypkBbR9wk5883nUv1ptnYaZ19K8NvKc3BUTJcZXAbgrR2iSkWjkV3a388DUO 8rBUoel+JyA+bbi279NcyOAFPX+WTwwyjFZ3S/h0U1coMHnLdmfDujnz/raP2rSTSs0aqCOw6 DGlmGtUScKUEiGVTRzvKAUlsBksLIqEDlZNkgURBlLQSaD7Laubkz1MYTUZMNZfj7uwgJh0VY Ns2wXvsc6GtdPxebEWS27l+L+JgBf89+AhlyolB8exVdw/EnAhq+bs8ypjX2RsOkM5hF5StdB hiBztH6btki2Y+dAjflO5wjEzG2wrFk2HB9jyG6kLWEHC2mLOAC9H8WgZAHRrWNhd78+uKFSo NpT2Imt1Mrjt0qDBW7KZyjpzfzJSPfWOf9XqUcj9KBjsza+0xk= X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Feb 2018 12:36:56 -0000 Hi everybody, From time to time my backup scripts break because "zfs recv" complains that a destination filesystem is modified (1). That should not be the case as the filesystems in the backup server are not mounted and "zfs receive" is always using the -u arg which also suggests that filesystems won't be mounted at the receiving side. Of course this is easily fixed with the help of -F on the receiving side which forces a rollback to the most recent snapshot. It just doesn't feel correct to blindly force it every time. I haven't noticed when exactly this happens, maybe it's related to a network failure while sending. I am not sure what would modify a filesystem... It happens maybe once every few months. The commands doing the backups are these: sending:> zfs send -R -i @2018-02-24_12.30.00--10d storage@BACKUP-2018-02-24_14.30.49--1m receiving:> zfs recv -u storage Has anybody else seen this? Am I doing something wrong? 1: > cannot receive incremental stream: destination storage/home/foo has been modified > since most recent snapshot Thanks! Nikos