From owner-freebsd-stable@freebsd.org Tue Feb 9 22:40:56 2021 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3E4D552DF1C for ; Tue, 9 Feb 2021 22:40:56 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ot1-f51.google.com (mail-ot1-f51.google.com [209.85.210.51]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DZyXl413Bz4TCB for ; Tue, 9 Feb 2021 22:40:55 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ot1-f51.google.com with SMTP id e5so8456otb.11 for ; Tue, 09 Feb 2021 14:40:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=dnnnefckrgv07h09y1jXDnikLrDUWcTEfJ+tl6lu+pI=; b=E3lGlzCt5y86Mr+UdoKdItTqBUKh3i74USO3m6M46NavaBfnr1xDe2Ng8Fq9Ky7jjB iHWi4qUR+OudmWDRIU1i5yX56711SWgvj/AwcF4TvR5eGxazq3i0m0e6StNdNKn6xPzo 383lr8OLhgzc12GXnhqcvmrqDNWDjGTbyaou0tbmtPLY5xilEx/HXB38JG0T4PpzgL4y yssIWlZxnaLmYbxT/LxxAlmaXIuTSrFyHBSEyT0NQAQLsk++QbCjkyB9ZRS0k0OTAXaQ P3z+7CuNyATTx4k2PgsDz2k5q+L9JJhT7yOfYMEVgnvTkXlbqT2qJ0I8iLtRVUzYAM5J NZKw== X-Gm-Message-State: AOAM531VPoG5f8VU60Rt/mHo9mdjMRBv5XqUtwFdiPe9318+gXWyISD+ nLytwiBX6aJUG4AcupeaSyRo79MPEUsXOgKFDu3Ufgz6pz0= X-Google-Smtp-Source: ABdhPJxl2Gh6FHJU7/UvYdeSvouG02s51rb1uA6IE5ibsoM19kEqprDYZ6NH869UP/eShXMtMozM5upcJm+LIKLfyZ0= X-Received: by 2002:a9d:4e81:: with SMTP id v1mr16744164otk.18.1612910454220; Tue, 09 Feb 2021 14:40:54 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Alan Somers Date: Tue, 9 Feb 2021 15:40:43 -0700 Message-ID: Subject: Re: stable/13 and zfs <> openzfs To: FreeBSD X-Rspamd-Queue-Id: 4DZyXl413Bz4TCB X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.210.51 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RWL_MAILSPIKE_GOOD(0.00)[209.85.210.51:from]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[209.85.210.51:from]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_DOM_EQ_FROM_DOM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEFALL_USER(0.00)[asomers]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[209.85.210.51:from:127.0.2.255]; R_DKIM_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[209.85.210.51:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-stable] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Feb 2021 22:40:56 -0000 On Tue, Feb 9, 2021 at 3:28 PM tech-lists wrote: > Hi, > > I need to build a new zpool (arch=amd64). The machine needs upgrading > from stable/12 to stable/13. The process I envisaged following is: > > 1. backup all data to a non-zpool disk > 2. upgrade the OS stable/12 to stable/13 > 3. destroy the original zpool [1] > 4. build new zpool and restore data > > stable/13 seems to have openzfs as the default zfs. Is there anything > more I need do? [2] The system is havdling remote zfs receive from a > 12.2-p3 system that uses the earlier default FreeBSD zfs. [3] > > [1] the original zpool was going to be destroyed anyway due to wrong > ashift for these new disks. > > [2] like, does /etc/rc.conf need modifying? Things like that. > > [3] is the newer openzfs compatible with the older one? I mean will the > older one still be able to send zfs snapshots for backup, or does > something need to be changed at either end? > > thanks, > -- > J. > The new ZFS is backwards compatible with the old one. So your 12.2-p3 system will be able to zfs send, and the stable/13 will be able to zfs recv. You can go the other direction too, if you're careful to create the new pool using the old format, and don't turn on any of the new features. /etc/rc.conf shouldn't need any changes. Your upgrade plan sounds fine. But for the "backup all data" step, I would recommend using zfs send/recv to do the backup. That will do a better job of ensuring your files' integrity than something like rsync or cp. -Alan