Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.

On 08.01.2024 1:15, Larry Rosenman wrote: So, if this is a mirror, then ada0 blank and ada1 with good data, in theory you should be fine. However, perhaps ZFS is finding that there's an error from ada1 for real. Does all of ada1 read with a simple dd?   Yep, it is read with dd, I've checked it

Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.

On 01/08/2024 5:15 am, Lev Serebryakov wrote: On 08.01.2024 1:15, Larry Rosenman wrote: So, if this is a mirror, then ada0 blank and ada1 with good data, in theory you should be fine. However, perhaps ZFS is finding that there's an error from ada1 for real. Does all of ada1 read with a simple

Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.

On 08.01.2024 16:44, Larry Rosenman wrote: So, if this is a mirror, then ada0 blank and ada1 with good data, in theory you should be fine. However, perhaps ZFS is finding that there's an error from ada1 for real. Does all of ada1 read with a simple dd?   Yep, it is read with dd, I've checked it

Crash on adding L2ARC to raidz1 pool

Hello! System: FreeBSD 13.2-STABLE stable/13-n256849-05c55eed44e5 BLOB amd64 I'm still trying to add NVMe L2ARC to my 5xHDD RADIZ1 pool. Last attempt of adding 640GiB (10x RAM) GPT partition on NVMe (AData Legend 960) leads to instant crash. I have: vfs.zfs.compressed_arc_enabled=0 vfs

clang 17 and ports fallout

After today's MFC of clang17,  I am seeing some fallout from a few ports that build with clang16 on RELENG_13 but now fail.  Any ideas what might be going on ?   I have nothing in /etc/make.conf nor /etc/src.conf Specifically devel/ivykis databases/rrdtool --- iv_thread_posix.lo --- mv -f .de

Re: clang 17 and ports fallout

On 1/8/2024 3:40 PM, mike tancsa wrote: After today's MFC of clang17,  I am seeing some fallout from a few ports that build with clang16 on RELENG_13 but now fail.  Any ideas what might be going on ?   I have nothing in /etc/make.conf nor /etc/src.conf These build on RELENG_14, so perhaps som

kern.version and uname -v

Hi! For ages, "uname -v" output (sligtly polished sysctl kern.version) had the following format: $ uname -v FreeBSD 13.2-STABLE 36a037f15 KERNELIDENT Where KERNELIDENT is GENERIC for x86 distribution media. But now: # uname -v FreeBSD 14.0-RELEASE #0 releng/14.0-n265380-f9716eee8ab4: Fri Nov 1

Re: kern.version and uname -v

On Mon, Jan 8, 2024 at 1:58 PM Eugene Grosbein wrote: > Hi! > > For ages, "uname -v" output (sligtly polished sysctl kern.version) had the > following format: > $ uname -v > FreeBSD 13.2-STABLE 36a037f15 KERNELIDENT > This is the reproducible format: only include data that is identical from buil

Re: kern.version and uname -v

Hi, > On 8 Jan 2024, at 22:16, Warner Losh wrote: > > This is the old, non-reproducible format. We've had both formats for several > major releases, and this format, with various tweaks as we went from CVS -> > svn -> git. > > Maybe the problem here is that in the run up to 14.0 we didn't tur

Re: clang 17 and ports fallout

On 8 Jan 2024, at 21:57, mike tancsa wrote: > > On 1/8/2024 3:40 PM, mike tancsa wrote: >> After today's MFC of clang17, I am seeing some fallout from a few ports >> that build with clang16 on RELENG_13 but now fail. Any ideas what might be >> going on ? I have nothing in /etc/make.conf nor

Re: kern.version and uname -v

09.01.2024 4:16, Warner Losh wrote: > On Mon, Jan 8, 2024 at 1:58 PM Eugene Grosbein > wrote: > For ages, "uname -v" output (sligtly polished sysctl kern.version) had > the following format: > $ uname -v > FreeBSD 13.2-STABLE 36a037f15 KERNELIDENT > > This

Re: kern.version and uname -v

On Mon, Jan 8, 2024 at 7:17 PM Eugene Grosbein wrote: > 09.01.2024 4:16, Warner Losh wrote: > > > On Mon, Jan 8, 2024 at 1:58 PM Eugene Grosbein > wrote: > > For ages, "uname -v" output (sligtly polished sysctl kern.version) > had the following format: > > $ un