From nobody Fri Feb 07 16:37:37 2025 X-Original-To: freebsd-stable@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 4YqKQT6F78z5mSG8 for ; Fri, 07 Feb 2025 16:37:53 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ed1-f47.google.com (mail-ed1-f47.google.com [209.85.208.47]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YqKQT2jqPz3pcQ for ; Fri, 07 Feb 2025 16:37:53 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-f47.google.com with SMTP id 4fb4d7f45d1cf-5dcd3454922so4694402a12.1 for ; Fri, 07 Feb 2025 08:37:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738946270; x=1739551070; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=1GIdWI9zBW3xfQuHpqx33p3s2V84bPViRwiBOP3qXIA=; b=KOY2zbi9HqGsVa0D21exPuomV5jKPrwk10CMtD8dpIF1B9bI43bgMJI4dtisBUvyVi ji3pTtpT08XZgmYHoZYTiE4fxzFrhGxC2NuI9+iL3a3JV8EKeilsLucaLvvrhJ36YYMZ n7NIFFTJi6Dflo8fOnFL3SyyuKH0pg2vWp9tCUr1S8NPvqW1wK4N5OcPW+EqX2x5xDPJ hmegBz4n1cNtYmp7RDwApJl3/k2mTvU88jxRatQjYEkdNYYSxnQ7ca+dJSvPdHmuAAJy rPPEhRhN3u6xV3+utAZOAr36wWvuJLvVrb2Ay1vxPdOfyU4h5ljxbqPR+dSXcbLWVTc7 8/wQ== X-Gm-Message-State: AOJu0Yx+86rMIZecE4mkwTT1eFceJjc31xUVHNkBCVu/txZk1vusNo/d Wz8R8DhB03mftygFyn/+CO1Nw8WlZ//+aMt1yIQZDTqMTge0mb7Auw3jo6ELyfolM6S0JZzPN+T B5VLIfIauLN2AlSmpFrkAWtf2DFI= X-Gm-Gg: ASbGncvr1S8b/WzMBlbuE+fF9jrc373uRYG0Ir6FDKgBr4G6y/yukzouh4B3z5cQ9Hc DCcw4m4WX+o1zfx3Ko48dj9qtRFa5DVNl9ayyt+WdoP8iKsBr2HNCo3n2GNCr75w74IBLOzRx X-Google-Smtp-Source: AGHT+IESSae6ADVJplfUoVLTKAVMDbbnqDcDXhSOnYSDeaP4v0i4hTt04SdpUaO9exIA664Wk39hNhfjhuTJv3mRDyI= X-Received: by 2002:a05:6402:40c9:b0:5de:4acc:8a99 with SMTP id 4fb4d7f45d1cf-5de4acc8d50mr3534183a12.18.1738946269761; Fri, 07 Feb 2025 08:37:49 -0800 (PST) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 References: <29dd6361-08c8-4321-bd3a-e8dd39d8a865@sentex.net> In-Reply-To: <29dd6361-08c8-4321-bd3a-e8dd39d8a865@sentex.net> From: Alan Somers Date: Fri, 7 Feb 2025 09:37:37 -0700 X-Gm-Features: AWEUYZkWq1YkUPoWArUGi79SXwRov9DmQvFTSbP4h4zfDpdoC9cNw9v4O8CYqKM Message-ID: Subject: Re: zfs encrypted datasets and snapshots To: mike tancsa Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4YqKQT2jqPz3pcQ X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] On Fri, Feb 7, 2025 at 7:42=E2=80=AFAM mike tancsa wrote: > > I have a project coming up that I would like to make use of this feature > set. For replication, we use zrepl quite a bit. In the past there were > a lot of cases of corruption of snapshots and pool errors when these > features were used together. > > e.g. to name just one > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282622 > > But some reports have 14.x more stable. I set up a test vm using 14.2R > with a jail that lives on an encrypted dataset and gets snapshotted > every 10min with the snapshots sent to another server. In the VM I am > just doing buildworld over and over again for now to create a load with > some disk io. Are there any particular loads that would trigger the > issue more often than not ? > > > ---Mike Search the issues at https://github.com/openzfs/zfs . There are still reports of corruption with ZFS crypto. One user reported that taking recursive snapshots while a "zfs send" is in progress can trigger corruption, but I think there are others, too.