Date: Sat, 15 Apr 2023 21:23:36 +0300 From: Christos Chatzaras <chris@cretaforce.gr> To: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: =?utf-8?Q?Re=3A_OpenZFS_recently_=28was_=E2=80=A6_=5Bzfs_corrupti?= =?utf-8?Q?ons_without_block=5Fcloning_involved!=5D=29?= Message-ID: <DE67F1C0-C0E5-4074-B0C9-09C61722213A@cretaforce.gr> In-Reply-To: <29ec969d-1aa2-0e4d-ba35-6fc3a5ba2b61@freebsd.org> References: <2C2AB2E9-32B5-41D3-9A19-B8FEA6BA68F7.ref@yahoo.com> <2C2AB2E9-32B5-41D3-9A19-B8FEA6BA68F7@yahoo.com> <988674ff-d7a7-b271-4ec6-9f568e407945@freebsd.org> <ZDqpgUNN-YnjIOxm@int21h> <29ec969d-1aa2-0e4d-ba35-6fc3a5ba2b61@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 15 Apr 2023, at 20:56, Graham Perrin <grahamperrin@freebsd.org> = wrote: >=20 > On 15/04/2023 14:41, void wrote: >> On Sat, Apr 15, 2023 at 09:56:34AM +0100, Graham Perrin wrote: >>>=20 >>> Is the recent situation unusual enough to warrant an entry in = UPDATING? >>>=20 >>=20 >> yeah I'd say so. >>=20 >> Also does this affect 13-stable and the recent 13.2-RELEASE or just = -current? >=20 >=20 > If I'm looking in the right place: >=20 > <https://github.com/freebsd/freebsd-src/commit/2a58b31>; to main on = 2023-04-03, "zfs: merge openzfs/zfs@431083f75" >=20 > <https://cgit.freebsd.org/src/log/?h=3Dstable%2F13&qt=3Dgrep&q=3Dmerge>; = no comparable merge to stable/13. >=20 Looks like only CURRENT is affected.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DE67F1C0-C0E5-4074-B0C9-09C61722213A>