From nobody Fri Feb 4 10:07:04 2022 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 6BE2119A1075; Fri, 4 Feb 2022 10:07:07 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Jqrmq241tz4n28; Fri, 4 Feb 2022 10:07:07 +0000 (UTC) (envelope-from avg@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643969227; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=RvUIV2G4d5RBuL0ufm9EKGobpYo1ErAUk6UXTMl8JV4=; b=TIn9k7abiQY1xVhhtngoliymQ7qOiYZFP0vjBUeIxbNO0cTeCc+lorXnLWkR6GCTy7nBan xTSxegY8s4GouSDcLOUcNYBvMs9ZUTGQ6FKcuQfqlNNyejuanym8p+1jQNatb0BKZk7qwt FRk+Yd5Df6iMpbAVrL3hwLD6mGNlFHNF/dqdfPtQHrlkEPxXgtv84XX4JthA5NQlZumoOC hiCWUWP4qrCgrsISRnplM/mc5zx67CaKQ7VeR93ExUFLSO+AJmkVJ9klqM5cquMhR8I9Jo WAr9x4Ph55dQ/34HApcVgStpSSPnFhJ0jTOqtsirty3tzSKUQ0lzcOJYALkmhw== Received: from [192.168.0.88] (unknown [195.64.148.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: avg/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id ADF542F6D5; Fri, 4 Feb 2022 10:07:06 +0000 (UTC) (envelope-from avg@FreeBSD.org) Message-ID: <556a2f46-9dac-e0bc-10a7-d81bf7c99f5a@FreeBSD.org> Date: Fri, 4 Feb 2022 12:07:04 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.5.1 Content-Language: en-US To: freebsd-fs , FreeBSD Current From: Andriy Gapon Subject: rc.d/zpool should require (rw) root? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643969227; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=RvUIV2G4d5RBuL0ufm9EKGobpYo1ErAUk6UXTMl8JV4=; b=crex5P316EbWtrsoIpcdIUB6JwesJq9Z6cxxYX3RI4YrOL9O9CAEQxbWB5AkD2zImH9BqM hC+j9pHmhawfIxrMKgLQSQIkeIU5PDtwYcfkHRqC8LgbTRwL24fCSRgOXhz5toZoL31/IL gjyux+NnojZBBJi7uD1xiLdf7yik9X5MD4lGpcffm0SCliRltdkkS3eSftd1eEUSsuhvtY qV7088GTiLnyyIbRk/ZAPHRpB/AKlYjLXYswiTOFsNSC5ma+fqqvExcxbQ3oOBXg47ti1Q eEo/bW83VGqWPm+ePR6rUjWkSLvUcOofVwWjJqeJXw0fpQVG433DpR/PAp0XdA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643969227; a=rsa-sha256; cv=none; b=DQTQzgxQtAPpI0s1fB7YGJt8iNRg4BlUGnZPgGNwUW8PG2uzA6x0lYuCuo6XKbmPvASCew ZnP8mpARrbd5qHF+QU+BBMDZU/ltNLI0B8bWZm27rNVY4tTF1sWwrg27qOK44zojLLFLze lAEq5V4eLJT1ob8YjZ7mRLYNS4ZnNXGUA5vEcg0cQXMPPfuKyz54rX7gnlIWPt6R0OmOo3 Oio1VB5TemC2TL0TZLRefqq80737nhgUA9Rkl2OTJiEV0lE/7rnTSdp9Bl9DoAsYY3xt3F 9Hncwh3TyBOd4I9Wp2ce3B3ivBteY7fLLo4NRP3AvueHZvhelvnvhTiXjwWCWw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N It seems that in some cases zpool import -c requires read/write access to the zpool.cache file. So, it probably makes sense to import "other" pools (non-root) after upgrading / to rw. What do you think? -- Andriy Gapon