From owner-freebsd-stable@freebsd.org Thu May 18 03:42:55 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35938D716E3 for ; Thu, 18 May 2017 03:42:55 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (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 E2C431FFE for ; Thu, 18 May 2017 03:42:54 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by mail-qk0-x231.google.com with SMTP id a72so26239359qkj.2 for ; Wed, 17 May 2017 20:42:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kraus-haus-org.20150623.gappssmtp.com; s=20150623; h=subject:mime-version:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rRuiv0UMmsKXc6sLWxRBps3uE0ATm9YCKhbN2tZaT18=; b=ig7hl1yw+beA31TLcXiZQWzvMQTg1W8ojgFBJsYjKIs7GxlKa26DmOOAgNu/UkuXi/ tqvsohreC5RHpWjDGpZwusaIEaKcuwbUzstaYYI1QAge+a2p/KUUjp9JB2XpTbKfPXjC UkVi7WsOIS6JyhqfJpi1gAn+O8qNjfE8QtMcutmrywA9mUCPsG7FrzknQ7f0TqKZIufx h3FkHxUSOSLJY6NPDoLmlduCtMWuv8x/B/AiTKbO4tB0/aM2Iugqdo6VzNKpujHiDgAo 3+nagrBVhzFEjFqMO8gHVqlu47SWzOiaLfZvBhmui8/AypcGSYC4uz6uDSYIjIy83LjE /5LQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rRuiv0UMmsKXc6sLWxRBps3uE0ATm9YCKhbN2tZaT18=; b=EpaObCRlU3FjUdYytbrG07zhEvi4ivkOB3L0q9ur32DUkbmB1w9u5zgEfrf/cnvtgf WnaiEJYGLY3DcBKsX+rWJ71ZwdMERn2uIE4V7rrIyGI2vCQVFzen1dTlQKh85s8GID21 3TFVajOaGebI5GOYesKZAsk7ZlEtTims7pJLD/lkxaDhMUDlXn7tpWYv/ECy5DK7UHFd 1MQEymp6dXmB8//RVIDesLCHS5X0eDnBTIrunWINw8lrbN+H+Mm1mmqtDFK9wW9mII2w GsbZAIm5ki0U7ONfrC5OnFOJaDmD9TGoUIXeKH5O2LeUlCqpy/fcwKrg2qXv3Adocaga MGOg== X-Gm-Message-State: AODbwcCfYcUJsD01CEl6lS0DGrK4Jg+HxfYFFIEuPwkrCU1mzWEKr1tU 3MH0MMXKYPL1c0dh X-Received: by 10.55.129.65 with SMTP id c62mr1894367qkd.229.1495078973857; Wed, 17 May 2017 20:42:53 -0700 (PDT) Received: from [192.168.2.65] (pool-74-109-188-83.albyny.fios.verizon.net. [74.109.188.83]) by smtp.gmail.com with ESMTPSA id l10sm2690871qte.15.2017.05.17.20.42.52 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 17 May 2017 20:42:53 -0700 (PDT) Subject: Re: zpool imported twice with different names (was Re: Fwd: ZFS) Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: text/plain; charset=utf-8 From: Paul Kraus In-Reply-To: Date: Wed, 17 May 2017 23:42:52 -0400 Cc: Nikos Vassiliadis , FreeBSD FS , freebsd-stable Content-Transfer-Encoding: quoted-printable Message-Id: References: <7c059678-4af4-f0c9-ff3b-c6266e02fb7a@gmx.com> <20170516170802.71c2a470@fabiankeil.de> To: Brandon Allbery X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 May 2017 03:42:55 -0000 > On May 17, 2017, at 2:13 PM, Brandon Allbery = wrote: >=20 > Sorry, no, that's not a bug. The bug is that, if importing on another > system is a common administrative operation, it should not require you = to > disable *all* checking. I'd rather prefer specific support for that, = e.g. > "import -F expectedhostname" to import a zpool on a different host = from > expectedhostname --- now you have sanity checking for a potentially > dangerous operation as well as not turning off *all* error/sanity = checking. The assumption at work here is that you have exported the zpool from the = system that was using it. At that point, zpool import with no = -f will work fine. It is only the special case of a zpool that was NOT = exported that requires the use of the -f option. I don=E2=80=99t see this as an unreasonable expectation. You unmount = non-ZFS (and under the covers ZFS) filesystems before moving them to = other systems. Why should we not be expected to export a zpool before = moving it ? Note that in the case of a crashed or failed or otherwise _unexpected_ = move of a zpool from one system to another you still need to force the = import. Just as you are forced to either fsck or replay journals on = non-ZFS filesystems before you can mount them.=