Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75

On Apr 15, 2023, at 17:27, Mark Millard wrote: > On Apr 15, 2023, at 15:49, Mark Millard wrote: > >> . . . >>> >>> >>> (Mostly written as I progressed but some material later >>> inserted into/around previously written material.) >>> >>> Summary: >>> >>> As stands, it looks like reverting t

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75

A general question is all for this message. So far no commit to FeeeBSD's main seems to be analogous to the content of: https://github.com/openzfs/zfs/pull/14739/files After my existing poudriere bulk test finishes, should I avoid having the content of that change in place for future testing? Vs

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75

On Apr 15, 2023, at 15:49, Mark Millard wrote: > . . . >> >> >> (Mostly written as I progressed but some material later >> inserted into/around previously written material.) >> >> Summary: >> >> As stands, it looks like reverting the dnode_is_dirty >> code is what fixes the corruptions tha

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75

On Apr 15, 2023, at 15:33, Mark Millard wrote: > On Apr 15, 2023, at 13:30, Mateusz Guzik wrote: > >> On 4/15/23, FreeBSD User wrote: >>> Am Sat, 15 Apr 2023 07:36:25 -0700 >>> Cy Schubert schrieb: >>> In message <20230415115452.08911...@thor.intern.walstatt.dynvpn.de>, FreeBSD Us

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75

On Apr 15, 2023, at 13:30, Mateusz Guzik wrote: > On 4/15/23, FreeBSD User wrote: >> Am Sat, 15 Apr 2023 07:36:25 -0700 >> Cy Schubert schrieb: >> >>> In message <20230415115452.08911...@thor.intern.walstatt.dynvpn.de>, >>> FreeBSD Us >>> er writes: Am Thu, 13 Apr 2023 22:18:04 -0700

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75

On 4/15/23, FreeBSD User wrote: > Am Sat, 15 Apr 2023 07:36:25 -0700 > Cy Schubert schrieb: > >> In message <20230415115452.08911...@thor.intern.walstatt.dynvpn.de>, >> FreeBSD Us >> er writes: >> > Am Thu, 13 Apr 2023 22:18:04 -0700 >> > Mark Millard schrieb: >> > >> > > On Apr 13, 2023, at 21:

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75

On Apr 15, 2023, at 11:07, Cy Schubert wrote: > In message <5a47f62d-0e78-4c3e-84c0-45eeb03c7...@yahoo.com>, Mark Millard > write > s: >> On Apr 15, 2023, at 07:36, Cy Schubert = >> wrote: >> >>> In message <20230415115452.08911...@thor.intern.walstatt.dynvpn.de>,=20= >> >>> FreeBSD Us >>> er

Re: aarch64: lang/gcc1* build regression between Mar-28 and Apr-8 [zfs corruptions without block_cloning involved!]

On 14/04/2023 11:58, Mark Millard wrote: … zfs after the import corrupts data even without block_cloning having ever been in use, even as the code currently is. … (2023-04-12) discusses reported corruptions when block clonin

Re: OpenZFS recently (was … [zfs corruptions without block_cloning involved!])

On Sat, Apr 15, 2023, 11:56 AM Graham Perrin wrote: > 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 1

Re: OpenZFS recently (was … [zfs corruptions without block_cloning involved!])

> On 15 Apr 2023, at 20:56, Graham Perrin wrote: > > 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-

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75

In message <5a47f62d-0e78-4c3e-84c0-45eeb03c7...@yahoo.com>, Mark Millard write s: > On Apr 15, 2023, at 07:36, Cy Schubert = > wrote: > > > In message <20230415115452.08911...@thor.intern.walstatt.dynvpn.de>,=20= > > > FreeBSD Us > > er writes: > >> Am Thu, 13 Apr 2023 22:18:04 -0700 > >> Mark M

Re: OpenZFS recently (was … [zfs corruptions without block_cloning involved!])

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 ri

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75

On Apr 15, 2023, at 07:36, Cy Schubert wrote: > In message <20230415115452.08911...@thor.intern.walstatt.dynvpn.de>, > FreeBSD Us > er writes: >> Am Thu, 13 Apr 2023 22:18:04 -0700 >> Mark Millard schrieb: >> >>> On Apr 13, 2023, at 21:44, Charlie Li wrote: >>> Mark Millard wrote: >>>

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75

On Sat, 15 Apr 2023 18:07:34 +0200 Florian Smeets wrote: > On 15.04.23 17:51, FreeBSD User wrote: > > Am Sat, 15 Apr 2023 07:36:25 -0700 > > Cy Schubert schrieb: > >> > >> With an up-to-date tree + pjd@'s "Fix data corruption when cloning embedded > >> blocks. #14739" patch I didn't have any i

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75

In message <20230415175218.777d0...@thor.intern.walstatt.dynvpn.de>, FreeBSD Us er writes: > Am Sat, 15 Apr 2023 07:36:25 -0700 > Cy Schubert schrieb: > > > In message <20230415115452.08911...@thor.intern.walstatt.dynvpn.de>, > > FreeBSD Us > > er writes: > > > Am Thu, 13 Apr 2023 22:18:04 -0700

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75

On 15.04.23 17:51, FreeBSD User wrote: Am Sat, 15 Apr 2023 07:36:25 -0700 Cy Schubert schrieb: With an up-to-date tree + pjd@'s "Fix data corruption when cloning embedded blocks. #14739" patch I didn't have any issues, except for email messages with corruption in my sent directory, nowhere els

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75

Am Sat, 15 Apr 2023 07:36:25 -0700 Cy Schubert schrieb: > In message <20230415115452.08911...@thor.intern.walstatt.dynvpn.de>, > FreeBSD Us > er writes: > > Am Thu, 13 Apr 2023 22:18:04 -0700 > > Mark Millard schrieb: > > > > > On Apr 13, 2023, at 21:44, Charlie Li wrote: > > > > > > > Ma

Re: Status of Alder and Raptor lake on FreeBSD Current

> I was wondering what the status of Alder/Raptor lake support is on FreeBSD? > Does it boot? I am writing this message from 13.2 machine with i3-12100F (must be an Alder Lake; no integrated graphics in this one, though) in B660 motherboard. Previously the same machine was running 13.1. If it matt

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75

In message <20230415115452.08911...@thor.intern.walstatt.dynvpn.de>, FreeBSD Us er writes: > Am Thu, 13 Apr 2023 22:18:04 -0700 > Mark Millard schrieb: > > > On Apr 13, 2023, at 21:44, Charlie Li wrote: > > > > > Mark Millard wrote: > > >> FYI: in my original report for a context that has nev

Re: OpenZFS recently (was aarch64: lang/gcc1* build regression between Mar-28 and Apr-8 [zfs corruptions without block_cloning involved!])

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? --

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75

Am Thu, 13 Apr 2023 22:18:04 -0700 Mark Millard schrieb: > On Apr 13, 2023, at 21:44, Charlie Li wrote: > > > Mark Millard wrote: > >> FYI: in my original report for a context that has never had > >> block_cloning enabled, I reported BOTH missing files and > >> file content corruption in the

OpenZFS recently (was aarch64: lang/gcc1* build regression between Mar-28 and Apr-8 [zfs corruptions without block_cloning involved!])

On 14/04/2023 11:58, Mark Millard wrote: … zfs after the import corrupts data even without block_cloning having ever been in use, even as the code currently is. More problems are to be found and fixed yet, despite the several fixes now in place. See for example … Is the recent situation unu