From owner-freebsd-fs@freebsd.org Sat Feb 24 16:39:42 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 B3273F2D083 for ; Sat, 24 Feb 2018 16:39:42 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 172706BCF2; Sat, 24 Feb 2018 16:39:42 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from moby.local ([79.107.33.9]) by mail.gmx.com (mrgmx002 [212.227.17.184]) with ESMTPSA (Nemesis) id 0LuPYt-1eiAEL2Az9-011hRJ; Sat, 24 Feb 2018 17:39:34 +0100 Subject: Re: cannot receive incremental stream: destination foo has been modified To: Andriy Gapon , FreeBSD Filesystems References: <50293f13-86d8-34c5-82d6-61aabcec0bfd@FreeBSD.org> From: Nikos Vassiliadis Message-ID: <3f239091-c278-fcae-571c-3c4dc346b24d@gmx.com> Date: Sat, 24 Feb 2018 18:39:25 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <50293f13-86d8-34c5-82d6-61aabcec0bfd@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:aEpC3VhYKfElmzsq0g9YGvBcqoWINE2KH0jxwFJg5owUlYI6G9J LL5+wythBv47OAy1KYPR7ze+TgTZZFQVrHui1e/2iBBSTZ/D37KU8x2Zx1Kt3AI5H4N5+JK q4sm3E+OKqaXl85gwlK2iIaAr6yr00cJF5QtoX+6ysUMgrga2QpuQj2tWKeOaanY7jQfswQ gSCDLZGVw+4rvjyhnXRzQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:9Qc01enB9pY=:4nST1/kB0Po86PRoPPGEAC 58ucR7g9v6abjIA42RudtM86x3YhVSF6EEqWvgsK5OzQZop9TXTBAVVqFqutKyJHGJ5mu1Rvo 1Sw0iEABNrjVQOjrh+iMBkWcNPmWFDz0SqTUrxP9OYH0Yo3L+i+f9M7vNS8rBbZJqRDQHVchT u59feyimKg5rxsJhBHT+zzMTUXeNg1iiZ1Wa+OCtKo3rpuAmBezkaUNOQh1cJusAHd/7BUslK XsprfkKosLI9sYoPd6L7JR7zBbubKImq4DWpvoAz472uuJDyE9U6XfUPX/aznmv0cVrE9dBhu qkLkqZY5ZPnPRX4iJCuR+PBlKihwoH2zmhyHNj1xsObHVqs/JMfxXHlbFa9Ap9AOzpYteHIW4 w9UlDJ6EEGOoEE5kSChlVTiTu6kTRsKlL3JBOCCK0wV+i5MNIcNl0OQZ4KOypAimw1PHAfYOR n+KZYoPoP50fGhTBFt/RZxdlNEIvPFQM2k3QiZgJ2CUUfmgAfmPzvfrXft6Smn59QHRVjunxL G0sLpv1ntAAtILLd3j9WBlVCpGc61ygXTefmwZyT1PabwsMBMXygUZImQIAy8tF3zv4zbrzFx 3czmatccPmpobRCO3dqFqJ1nIt1QXCXJ7HCV/5t8mhTVj5M7CPWw7W2t7XEIyhdpYSTE4rZ2i lM8p7TjhE4s+6eXhBk351m54SiyFqYmh2FV0JcgIX91HPVIh/skPq+1c4EHoDqkGell4novMi oSkp+PFTvXZMEokGGhumzxVsq2pVAZ0MqmAyCYkO//JsiQ1ZHpOEPgLTKPk4OMPVi0NDX+B3H Jf/SdkRTezv4B/YWzM2eNgcRcpJOaTx0JGOdHGUvFEUfc7CAx0= 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 16:39:42 -0000 On 02/24/18 17:12, Andriy Gapon wrote: > On 24/02/2018 14:36, Nikos Vassiliadis wrote: >> 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. > > > Are you absolutely sure that the affected filesystems are never mounted? Yes, since I didn't see mounted filesystems after the error. > receive -u ensures that a filesystem is not mounted right after being received, > but without additional steps it does not ensure that the filesystem won't be > mounted after a reboot of the backup server (or export / import of the backup pool). > You're correct, this can/will happen after a reboot. Unfortunately, this is not the case. It happened a few days ago and the backup server was not rebooted and no filesystems were mounted. I am the only sysadmin of the backup server too so I can say that everything seems ok. It happens though after a network disconnect while sending/receiving. So maybe there is something there. More specifically I have seen this on a very limited bandwidth link (60-70KB/s) and only now and then. I have tried to simulate network failures but the problem never happened. I am not sure what to do next... Thanks for your ideas, Nikos