From owner-freebsd-fs@freebsd.org Sat Feb 24 15:13:10 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 06109F26D3A for ; Sat, 24 Feb 2018 15:13:10 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com [209.85.215.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6EC076836F for ; Sat, 24 Feb 2018 15:13:09 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f53.google.com with SMTP id t79so16384691lfe.3 for ; Sat, 24 Feb 2018 07:13:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=FVo0+ylTFMMeBdjBgDoTEnvkf9CMUNgmukiEXMqO6lQ=; b=Zvp5TNbvmSp+22VaM2xWsCqjyYMC9FyDHVxe7OgsKX3DKW9v6vxbjmoKz3Hq12077w Aia0uz9FCLuZnEZDlOa/kC3CRWu33pPiZeEBS01nw1FWgPRTFFTXiBSnbP2qx4irTWCe NoX66dTfgVXpn2mXyqR4tYbKNuoGRYeVHSyYvAHodo5wd2magHeR2iSLM6sz6bWINQve eSM0kh/2yvTZXFWRoNkEthy+kSUX4uIP/AZcCMoMufHjP37HRLpS6HZF/P+Z4YfG5ZEz STH1PmbPeobIYUe0VEUA6np7/ZfVWUx13XZdDnxabRHd3FvPjXWXMzjfQ74XYfIhNM9w c2fA== X-Gm-Message-State: APf1xPBdYQoZs2DV1Rz1rNmOBVILy14gtXwO/ablfFOTXSegGFic99I7 5rcF0+FIId9JGBP5WGwZ2+RCEbLM X-Google-Smtp-Source: AG47ELsK1McKTXn7l5SSrGxOPivRrJ7tktcxYA6kNaeyHOoplIritehp4S6NprRLJIMN97aMd2/ClA== X-Received: by 10.25.217.69 with SMTP id q66mr3977175lfg.62.1519485181750; Sat, 24 Feb 2018 07:13:01 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id p190sm998215lfp.3.2018.02.24.07.12.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 24 Feb 2018 07:12:59 -0800 (PST) Subject: Re: cannot receive incremental stream: destination foo has been modified To: Nikos Vassiliadis , FreeBSD Filesystems References: From: Andriy Gapon Message-ID: <50293f13-86d8-34c5-82d6-61aabcec0bfd@FreeBSD.org> Date: Sat, 24 Feb 2018 17:12:58 +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: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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 15:13:10 -0000 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? 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). -- Andriy Gapon