Re:_OpenZFS_recently_(was_…_[zfs_corruption s_without_block_cloning_involved!])

Reply: Christos Chatzaras : "Re:_OpenZFS_recently_(was_…_[zfs_corrupti ons_without_block_cloning_involved!])"
Reply: Warner Losh : "Re:_OpenZFS_recently_(was_…_[zfs_corruptions_witho ut_block_cloning_involved!])"
In reply to: void : "Re: OpenZFS recently (was aarch64: lang/gcc1* build regression between Mar-28 and Apr-8 [zfs corruptions without block_cloning involved!])"
Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: Graham Perrin <grahamperrin_at_freebsd.org>
Date: Sat, 15 Apr 2023 17:56:21 UTC

On 15/04/2023 14:41, void wrote:
> On Sat, Apr 15, 2023 at 09:56:34AM +0100, Graham Perrin wrote:
>>
>> Is the recent situation unusual enough to warrant an entry in UPDATING?
>>
>
> yeah I'd say so.
>
> Also does this affect 13-stable and the recent 13.2-RELEASE or just 
> -current?


If I'm looking in the right place:

<https://github.com/freebsd/freebsd-src/commit/2a58b31> to main on 
2023-04-03, "zfs: merge openzfs/zfs@431083f75"

<https://cgit.freebsd.org/src/log/?h=stable%2F13&qt=grep&q=merge> no 
comparable merge to stable/13.