Re: Seemingly random nvme (nda) write error on new drive (retries exhausted)

2023-06-08 Thread Rebecca Cran
On 6/8/23 00:24, Warner Losh wrote: PCIe 3 or PCIe 4? PCIe 4. nda0 at nvme0 bus 0 scbus0 target 0 lun 1 nda0: nda0: Serial Number S55KNC0TC00168 nda0: nvme version 1.3 x8 (max x8) lanes PCIe Gen4 (max Gen4) link nda0: 6104710MB (12502446768 512 byte sectors) -- Rebecca Cran

Re: Seemingly random nvme (nda) write error on new drive (retries exhausted)

2023-06-08 Thread Tomek CEDRO
what filesystem? is TRIM enabled on that drive? have you tried disabling trim? i had similar ssd related problem on samsung's ssd long time ago that was related to trim. maybe drive firmware can be updated too? :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Re: Seemingly random nvme (nda) write error on new drive (retries exhausted)

2023-06-08 Thread Rebecca Cran
It's ZFS, using the default options when creating it via the FreeBSD installer so I presume TRIM is enabled. Without a reliable way to reproduce the error I'm not sure disabling TRIM will help at the moment. I don't think there's any newer firmware for it. -- Rebecca Cran On 6/8/23 04:25,

Re: Seemingly random nvme (nda) write error on new drive (retries exhausted)

2023-06-08 Thread Warner Losh
On Thu, Jun 8, 2023, 4:35 AM Rebecca Cran wrote: > It's ZFS, using the default options when creating it via the FreeBSD > installer so I presume TRIM is enabled. Without a reliable way to > reproduce the error I'm not sure disabling TRIM will help at the moment. > > I don't think there's any newe

Re: Seemingly random nvme (nda) write error on new drive (retries exhausted)

2023-06-08 Thread Rebecca Cran
On 6/8/23 05:48, Warner Losh wrote: On Thu, Jun 8, 2023, 4:35 AM Rebecca Cran wrote: It's ZFS, using the default options when creating it via the FreeBSD installer so I presume TRIM is enabled. Without a reliable way to reproduce the error I'm not sure disabling TRIM will help at

CURRRENT snapshot won't boot due missing ZFS feature

2023-06-08 Thread Michael Gmelin
Hi, I didn't dig into this yet. After installing the current 14-snapshot (June 1st) in a bhyve-vm, I get this on boot: ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 (booting stops at this point) Seems like the boot loader is missing this recently added feature. Best Michael -- M

Re: CURRRENT snapshot won't boot due missing ZFS feature

2023-06-08 Thread Glen Barber
On Thu, Jun 08, 2023 at 06:11:15PM +0200, Michael Gmelin wrote: > Hi, > > I didn't dig into this yet. > > After installing the current 14-snapshot (June 1st) in a bhyve-vm, I > get this on boot: > > ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 > > (booting stops at this point) > >

Re: CURRRENT snapshot won't boot due missing ZFS feature

2023-06-08 Thread Yuri
Michael Gmelin wrote: > Hi, > > I didn't dig into this yet. > > After installing the current 14-snapshot (June 1st) in a bhyve-vm, I > get this on boot: > > ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 > > (booting stops at this point) > > Seems like the boot loader is missing thi

Re: CURRRENT snapshot won't boot due missing ZFS feature

2023-06-08 Thread Yuri
Yuri wrote: > Michael Gmelin wrote: >> Hi, >> >> I didn't dig into this yet. >> >> After installing the current 14-snapshot (June 1st) in a bhyve-vm, I >> get this on boot: >> >> ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 >> >> (booting stops at this point) >> >> Seems like the boot

Re: CURRRENT snapshot won't boot due missing ZFS feature

2023-06-08 Thread Michael Gmelin
On Thu, 8 Jun 2023 16:20:12 + Glen Barber wrote: > On Thu, Jun 08, 2023 at 06:11:15PM +0200, Michael Gmelin wrote: > > Hi, > > > > I didn't dig into this yet. > > > > After installing the current 14-snapshot (June 1st) in a bhyve-vm, I > > get this on boot: > > > > ZFS: unsupported fe

OpenSSL 3.0 in the base system update

2023-06-08 Thread Ed Maste
As previously mentioned[1] FreeBSD 14.0 will include OpenSSL 3.0. We expect to merge the update to main in the near future (within the next week or two) and are ready for wider testing. Supported by the FreeBSD Foundation, Pierre Pronchery has been working on the update in the src tree, with assi

Re: CURRRENT snapshot won't boot due missing ZFS feature

2023-06-08 Thread Michael Gmelin
On Thu, 8 Jun 2023 19:06:23 +0200 Michael Gmelin wrote: > On Thu, 8 Jun 2023 16:20:12 + > Glen Barber wrote: > > > On Thu, Jun 08, 2023 at 06:11:15PM +0200, Michael Gmelin wrote: > > > Hi, > > > > > > I didn't dig into this yet. > > > > > > After installing the current 14-snapshot (J

Re: CURRRENT snapshot won't boot due missing ZFS feature

2023-06-08 Thread Warner Losh
On Thu, Jun 8, 2023, 11:18 AM Michael Gmelin wrote: > > > On Thu, 8 Jun 2023 19:06:23 +0200 > Michael Gmelin wrote: > > > On Thu, 8 Jun 2023 16:20:12 + > > Glen Barber wrote: > > > > > On Thu, Jun 08, 2023 at 06:11:15PM +0200, Michael Gmelin wrote: > > > > Hi, > > > > > > > > I didn't dig i

panic(s) in ZFS on CURRENT

2023-06-08 Thread Gleb Smirnoff
Hi, I got several panics on my desktop running eb2b00da564 which is after the latest OpenZFS merge. #1 (couple cores with this backtrace) --- trap 0x9, rip = 0x803ab94b, rsp = 0xfe022e45ed30, rbp = 0xfe022e45ed50 --- buf_hash_insert() at buf_hash_insert+0xab/frame 0xfe022e

Re: panic(s) in ZFS on CURRENT

2023-06-08 Thread Gleb Smirnoff
On Thu, Jun 08, 2023 at 07:56:07PM -0700, Gleb Smirnoff wrote: T> I'm switching to INVARIANTS kernel right now and will see if that panics earlier. This is what I got with INVARIANTS: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed (225142071296 <= 225142063104) cpuid = 17 time = 1686

CPU hog on -current (pfSense 23.05)

2023-06-08 Thread Juraj Lutter
Hi, since cca 7 days I’ve started to observe a CPU hog of one CPU core on APU2 box running pfSense 23.05 (if that matters). mjg@ suggested to run a dtrace oneliner that showed: ~~ kernel`pmap_copy 33 kernel`amd64_syscall