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

On Apr 18, 2023, at 15:02, José Pérez wrote: > El 2023-04-18 21:37, Mark Millard escribió: >>> In this case it does because the value is "active". If it's "enabled" >>> you do not need to do anything. >> Well, if block_cloning is disabled it would not become active. > [...] >> So, in progressing

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

El 2023-04-18 21:37, Mark Millard escribió: In this case it does because the value is "active". If it's "enabled" you do not need to do anything. Well, if block_cloning is disabled it would not become active. [...] So, in progressing past the vintage that corrupt zfs data, one could end up

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

José_Pérez wrote on Date: Tue, 18 Apr 2023 16:59:03 UTC : > El 2023-04-17 21:59, Pawel Jakub Dawidek escribió: > > José, > > > > I can only speak of block cloning in details, but I'll try to address > > everything. > > > > The easiest way to avoid block_cloning-related corruption on the > >

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

El 2023-04-17 21:59, Pawel Jakub Dawidek escribió: José, I can only speak of block cloning in details, but I'll try to address everything. The easiest way to avoid block_cloning-related corruption on the kernel after the last OpenZFS merge, but before e0bb199925 is to set the compress property

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

On 4/17/23 21:28, José Pérez wrote: Hi Pawel, thank you for your reply and for the fixes. I think there is a 4th issue that needs to be addressed: how do we recover from the worst case scenario which is a machine with a kernel > 2a58b312b62f and ZFS root upgraded with block cloning enabled.

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

José_Pérez wrote on Date: Mon, 17 Apr 2023 12:28:40 UTC : > El 2023-04-17 12:43, Pawel Jakub Dawidek escribió: > > On 4/17/23 18:15, Pawel Jakub Dawidek wrote: > >> There were three issues that I know of after the recent OpenZFS merge: > >> > >> 1. Data corruption unrelated to block cloning, so

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

El 2023-04-17 12:43, Pawel Jakub Dawidek escribió: On 4/17/23 18:15, Pawel Jakub Dawidek wrote: There were three issues that I know of after the recent OpenZFS merge: 1. Data corruption unrelated to block cloning, so it can happen even with block cloning disabled or not in use. This was the

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

On 4/17/23 18:15, Pawel Jakub Dawidek wrote: There were three issues that I know of after the recent OpenZFS merge: 1. Data corruption unrelated to block cloning, so it can happen even with block cloning disabled or not in use. This was the problematic commit:

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

Hi Pawel, thank you for the patch. Can you please elaborate a little more? Did you run any tests? Is it safe to use your patch to access pools with feature@block_cloning active? Is it possible to build a kernel from such a pool? Asking for others: is this fixing any corrupted data? Thank

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

On 4/16/23 01:07, Florian Smeets wrote: On the pool that has block_cloning enabled I see the above insta panic when poudriere starts building. I found a workaround though: --- /usr/local/share/poudriere/include/fs.sh.orig    2023-04-15 18:03:50.090823000 +0200 +++

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

On Apr 16, 2023, at 10:40, Mark Millard wrote: > On Apr 16, 2023, at 01:34, Mark Millard wrote: > >> On Apr 15, 2023, at 19:13, Mark Millard wrote: >> >>> A general question is all for this message. >>> >>> So far no commit to FeeeBSD's main seems to be >>> analogous to the content of: >>>

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

On Apr 16, 2023, at 01:34, Mark Millard wrote: > On Apr 15, 2023, at 19:13, Mark Millard wrote: > >> 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 >> >>

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

On Apr 15, 2023, at 19:13, Mark Millard wrote: > 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

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

On Apr 15, 2023, at 21:31, Mark Millard wrote: > 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.)

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

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?

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

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

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

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

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

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

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

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

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

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

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

On Thu, Apr 13, 2023 at 06:48:14PM -0400, Charlie Li wrote: > Shawn Webb wrote: > > Does the ZFS project have some sort of automated testing to catch > > data-gobbling, pool killing bugs? It seems like this would have been > > caught with some CI/CD stress testing automation scripts. > > > I

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

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 poudriere-devel bulk build >> testing. This predates: >>

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

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 poudriere-devel bulk build testing. This predates: https://people.freebsd.org/~pjd/patches/brt_revert.patch but had the

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

On Apr 13, 2023, at 21:27, Charlie Li wrote: > > Pawel Jakub Dawidek wrote: >> On 4/14/23 09:23, Charlie Li wrote: >>> Pawel Jakub Dawidek wrote: Here is the change that reverts most of the modifications and disables cloning new blocks. It does retain ability to free existing cloned

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

Pawel Jakub Dawidek wrote: On 4/14/23 09:23, Charlie Li wrote: Pawel Jakub Dawidek wrote: Here is the change that reverts most of the modifications and disables cloning new blocks. It does retain ability to free existing cloned blocks and keeps block_cloning feature around, so upgraded pools

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

On 4/14/23 09:23, Charlie Li wrote: Pawel Jakub Dawidek wrote: Here is the change that reverts most of the modifications and disables cloning new blocks. It does retain ability to free existing cloned blocks and keeps block_cloning feature around, so upgraded pools can be imported and

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

On 4/14/23, Charlie Li wrote: > Pawel Jakub Dawidek wrote: >> On 4/14/23 07:52, Charlie Li wrote: >>> Pawel Jakub Dawidek wrote: thank you for your testing and patience so far. I'm working on a patch to revert block cloning without affecting people who already upgraded their pools.

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

Pawel Jakub Dawidek wrote: Here is the change that reverts most of the modifications and disables cloning new blocks. It does retain ability to free existing cloned blocks and keeps block_cloning feature around, so upgraded pools can be imported and existing cloned blocks freed. It does not

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

Pawel Jakub Dawidek wrote: On 4/14/23 07:52, Charlie Li wrote: Pawel Jakub Dawidek wrote: thank you for your testing and patience so far. I'm working on a patch to revert block cloning without affecting people who already upgraded their pools. Testing with mjg@ earlier today revealed that

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

On 4/14/23 07:52, Charlie Li wrote: Pawel Jakub Dawidek wrote: thank you for your testing and patience so far. I'm working on a patch to revert block cloning without affecting people who already upgraded their pools. Testing with mjg@ earlier today revealed that block_cloning was not the

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

On 4/14/23 07:40, Pawel Jakub Dawidek wrote: On 4/13/23 22:56, Cy Schubert wrote: I'm in the process of building a branch reverting the merge altogether and will test it on my sandbox machine later today. Cy, thank you for your testing and patience so far. I'm working on a patch to revert

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

Pawel Jakub Dawidek wrote: thank you for your testing and patience so far. I'm working on a patch to revert block cloning without affecting people who already upgraded their pools. Testing with mjg@ earlier today revealed that block_cloning was not the cause of poudriere bulk build (and

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

Shawn Webb wrote: Does the ZFS project have some sort of automated testing to catch data-gobbling, pool killing bugs? It seems like this would have been caught with some CI/CD stress testing automation scripts. I can't speak about how the OpenZFS project does things, but this particular

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

On 4/13/23 22:56, Cy Schubert wrote: I'm in the process of building a branch reverting the merge altogether and will test it on my sandbox machine later today. Cy, thank you for your testing and patience so far. I'm working on a patch to revert block cloning without affecting people who

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

On 4/13/23 23:05, Shawn Webb wrote: I've learned over the years downstream that it's not really my place to tell upstream what to do or how to do it. However, I think given the seriousness of this, upstream might do well to revert the commit until a solid fix is in place. Upstream might want to

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

On Thu, Apr 13, 2023 at 06:56:35AM -0700, Cy Schubert wrote: > In message om> > , Mateusz Guzik writes: > > On 4/13/23, Cy Schubert wrote: > > > On Thu, 13 Apr 2023 19:54:42 +0900 > > > Pawe=C5=82 Jakub Dawidek wrote: > > > > > >> On Apr 13, 2023, at 16:10, Cy Schubert wrote= > > : > > >> > >

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

In message , Mateusz Guzik writes: > On 4/13/23, Cy Schubert wrote: > > On Thu, 13 Apr 2023 19:54:42 +0900 > > Pawe=C5=82 Jakub Dawidek wrote: > > > >> On Apr 13, 2023, at 16:10, Cy Schubert wrote= > : > >> > > >> > =EF=BB=BFIn message <20230413070426.8a54f...@slippy.cwsent.com>, Cy Sc= >

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

On 4/13/23, Cy Schubert wrote: > On Thu, 13 Apr 2023 19:54:42 +0900 > Paweł Jakub Dawidek wrote: > >> On Apr 13, 2023, at 16:10, Cy Schubert wrote: >> > >> > In message <20230413070426.8a54f...@slippy.cwsent.com>, Cy Schubert >> > writes: >> > In message

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

On Thu, 13 Apr 2023 19:54:42 +0900 Paweł Jakub Dawidek wrote: > On Apr 13, 2023, at 16:10, Cy Schubert wrote: > > > > In message <20230413070426.8a54f...@slippy.cwsent.com>, Cy Schubert writes: > > In message <20230413064252.1e5c1...@slippy.cwsent.com>, Cy Schubert writes: > >> In message ,

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

On Apr 13, 2023, at 04:04, Charlie Li wrote: > Paweł Jakub Dawidek wrote: >> Can you please try this patch: >> >> Unfortunately I don’t see how this can happen with block cloning disabled. > This patch made no difference in poudriere; corruption still

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

Danilo Egea Gondolfo wrote: I'm having a funny issue here and I'm wondering if it is related. When building one of my ports I will, eventually, not always, get a file full of zeros as a result. The build will create copies of crispy-setup and, every once in a while, one of them will be a

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

Paweł Jakub Dawidek wrote: Can you please try this patch: Unfortunately I don’t see how this can happen with block cloning disabled. This patch made no difference in poudriere; corruption still rolled in. -- Charlie Li …nope, still don't have an

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

On 13/04/2023 06:28, Mark Millard wrote: From: Charlie Li wrote on Date: Wed, 12 Apr 2023 20:11:16 UTC : Charlie Li wrote: Mateusz Guzik wrote: can you please test poudriere with https://github.com/openzfs/zfs/pull/14739/files After applying, on the md(4)-backed pool regardless of

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

On Apr 12, 2023, at 23:52, Alexander Leidinger wrote: > Quoting Mark Millard (from Wed, 12 Apr 2023 22:28:13 > -0700): > >> A fair number of errors are of the form: the build >> installing a previously built package for use in the >> builder but later the builder can not find some file >>

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

In message <20230413070426.8a54f...@slippy.cwsent.com>, Cy Schubert writes: > In message <20230413064252.1e5c1...@slippy.cwsent.com>, Cy Schubert writes: > > In message , Mark Millard > > write > > s: > > > [This just puts my prior reply's material into Cy's > > > adjusted resend of the original.

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

In message <20230413064252.1e5c1...@slippy.cwsent.com>, Cy Schubert writes: > In message , Mark Millard > write > s: > > [This just puts my prior reply's material into Cy's > > adjusted resend of the original. The To/Cc should > > be coomplete this time.] > > > > On Apr 12, 2023, at 22:52, Cy

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

Quoting Mark Millard (from Wed, 12 Apr 2023 22:28:13 -0700): A fair number of errors are of the form: the build installing a previously built package for use in the builder but later the builder can not find some file from the package's installation. As a data point, last year I had such

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

In message , Mark Millard write s: > [This just puts my prior reply's material into Cy's > adjusted resend of the original. The To/Cc should > be coomplete this time.] > > On Apr 12, 2023, at 22:52, Cy Schubert = > wrote: > > > In message , Mark = > Millard=20 > > write > > s: > >> From: Charlie

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

[This just puts my prior reply's material into Cy's adjusted resend of the original. The To/Cc should be coomplete this time.] On Apr 12, 2023, at 22:52, Cy Schubert wrote: > In message , Mark Millard > write > s: >> From: Charlie Li wrote on >> Date: Wed, 12 Apr 2023 20:11:16 UTC : >> >>>

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

In message , Mark Millard write s: > From: Charlie Li wrote on > Date: Wed, 12 Apr 2023 20:11:16 UTC : > > > Charlie Li wrote: > > > Mateusz Guzik wrote: > > >> can you please test poudriere with > > >> https://github.com/openzfs/zfs/pull/14739/files > > >> > > > After applying, on the

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

From: Charlie Li wrote on Date: Wed, 12 Apr 2023 20:11:16 UTC : > Charlie Li wrote: > > Mateusz Guzik wrote: > >> can you please test poudriere with > >> https://github.com/openzfs/zfs/pull/14739/files > >> > > After applying, on the md(4)-backed pool regardless of block_cloning, > > the cy@

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75 [separate aarch64 panic for zpool import]

On Sat, Apr 8, 2023 at 5:24 AM Mateusz Guzik wrote: > > On 4/8/23, Kyle Evans wrote: > > On Fri, Apr 7, 2023 at 4:54 PM Mateusz Guzik wrote: > >> > >> On 4/7/23, Mark Millard wrote: > >> > On Apr 7, 2023, at 14:26, Mateusz Guzik wrote: > >> > > >> >> On 4/7/23, Mateusz Guzik wrote: > >> >>>

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75 [separate aarch64 panic for zpool import]

On 4/8/23, Kyle Evans wrote: > On Fri, Apr 7, 2023 at 4:54 PM Mateusz Guzik wrote: >> >> On 4/7/23, Mark Millard wrote: >> > On Apr 7, 2023, at 14:26, Mateusz Guzik wrote: >> > >> >> On 4/7/23, Mateusz Guzik wrote: >> >>> can you try with this: >> >>> >> >>> diff --git >> >>>

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75 [separate aarch64 panic for zpool import]

On Apr 7, 2023, at 16:29, Kyle Evans wrote: > On Fri, Apr 7, 2023 at 4:54 PM Mateusz Guzik wrote: >> >> On 4/7/23, Mark Millard wrote: >>> On Apr 7, 2023, at 14:26, Mateusz Guzik wrote: >>> On 4/7/23, Mateusz Guzik wrote: > can you try with this: > > diff --git >

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75 [separate aarch64 panic for zpool import]

On Fri, Apr 7, 2023 at 4:54 PM Mateusz Guzik wrote: > > On 4/7/23, Mark Millard wrote: > > On Apr 7, 2023, at 14:26, Mateusz Guzik wrote: > > > >> On 4/7/23, Mateusz Guzik wrote: > >>> can you try with this: > >>> > >>> diff --git > >>>

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75 [separate aarch64 panic for zpool import]

On 4/7/23, Mark Millard wrote: > On Apr 7, 2023, at 14:26, Mateusz Guzik wrote: > >> On 4/7/23, Mateusz Guzik wrote: >>> can you try with this: >>> >>> diff --git >>> a/sys/contrib/openzfs/include/os/linux/kernel/linux/simd_aarch64.h >>>

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75 [separate aarch64 panic for zpool import]

On Apr 7, 2023, at 14:26, Mateusz Guzik wrote: > On 4/7/23, Mateusz Guzik wrote: >> can you try with this: >> >> diff --git >> a/sys/contrib/openzfs/include/os/linux/kernel/linux/simd_aarch64.h >> b/sys/contrib/openzfs/include/os/linux/kernel/linux/simd_aarch64.h >> index

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75 [separate aarch64 panic for zpool import]

On 4/7/23, Mateusz Guzik wrote: > can you try with this: > > diff --git > a/sys/contrib/openzfs/include/os/linux/kernel/linux/simd_aarch64.h > b/sys/contrib/openzfs/include/os/linux/kernel/linux/simd_aarch64.h > index 16276b08c759..e1bca9ef140a 100644 > ---

Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75 [separate aarch64 panic for zpool import]

can you try with this: diff --git a/sys/contrib/openzfs/include/os/linux/kernel/linux/simd_aarch64.h b/sys/contrib/openzfs/include/os/linux/kernel/linux/simd_aarch64.h index 16276b08c759..e1bca9ef140a 100644 --- a/sys/contrib/openzfs/include/os/linux/kernel/linux/simd_aarch64.h +++

RE: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75 [separate aarch64 panic for zpool import]

Turns out that as of this commit aarch64 (Cortex-A72 and Cortex-A57 examples reported) gets the following even when no zfs media is present (UFS boot): # zpool import x0: f0fa9168 (ucom_cons_softc + efbf1bb8) x1: ff90 ($d.1 + afa318) x2: ff900400 ($d.1 + afa718)