Re: Speed improvements in ZFS

Am 2023-08-16 18:48, schrieb Alexander Leidinger: Am 2023-08-15 23:29, schrieb Mateusz Guzik: On 8/15/23, Alexander Leidinger wrote: Am 2023-08-15 14:41, schrieb Mateusz Guzik: With this in mind can you provide: sysctl kern.maxvnodes vfs.wantfreevnodes vfs.freevnodes vfs.vnodes_created vfs.n

Re: Status for zfs upgrade?

Hi, This blog might be interesting to you. https://vermaden.wordpress.com/2022/03/25/zfs-compatibility/ BTW: stable/14 is delayed one week: https://www.freebsd.org/releases/14.0R/schedule/ Regards, Ronald. Van: Tomoaki AOKI Datum: vrijdag, 18 augustus 2023 00:00 Aan: freebsd-current@freebsd.

Boot failures with 14.0-ALPHA1

I'll update to ALPHA2. In the meantime, briefly: – no visible progress beyond the four lines of EFI framebuffer information. In each case, I worked around by removing a USB flash drive that's used for L2ARC. The most recent incident was preceded

Re: Status for zfs upgrade?

Hi. Thanks for the pointer! Although the data in the page are a bit outdated, but the methods to determine features described there looks helpful. (For example, the problematic block_cloning feature is not listed yet.) And yes, I've noticed the Alpha2 commit, but ATM release schedule page was not

Re: Speed improvements in ZFS

On 8/18/23, Alexander Leidinger wrote: > Am 2023-08-16 18:48, schrieb Alexander Leidinger: >> Am 2023-08-15 23:29, schrieb Mateusz Guzik: >>> On 8/15/23, Alexander Leidinger wrote: Am 2023-08-15 14:41, schrieb Mateusz Guzik: > With this in mind can you provide: sysctl kern.maxvnodes

Re: ZFS deadlock in 14

Dag-Erling Smørgrav writes: > A kernel built from c47116e909 plus these two patches has so far built > 2,285 packages without a hitch, whereas normally it would have > deadlocked after well before reaching 500 packages. I'll do another run > without the patches tomorrow just to be sure. Plot twi

make-memstick.sh creates in 14.0-CURRENT run-away processes

I was used to use in 13.0-CURRENT the script "make-memstick.sh" to create memstick immages to install the system on smaller devices where the OS can't build from the sources, and it always worked fine for many years. Now I'm ready to do so with my fresh compiled system (sources from git August, 5

Re: ZFS deadlock in 14

[I had sent to the wrong list. Just fixing that here.] On Aug 18, 2023, at 09:26, Mark Millard wrote: > Dag-Erling_Smørgrav wrote on > Date: Fri, 18 Aug 2023 14:16:12 UTC : > >> Dag-Erling Smørgrav writes: >>> A kernel built from c47116e909 plus these two patches has so far built >>> 2,285 pa

Re: make-memstick.sh creates in 14.0-CURRENT run-away processes

I filed this PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273211 about the issue. El día viernes, agosto 18, 2023 a las 06:17:42p. m. +0200, Matthias Apitz escribió: > > I was used to use in 13.0-CURRENT the script "make-memstick.sh" to > create memstick immages to install the system

Re: ZFS deadlock in 14

Dag-Erling Smørgrav writes: > Plot twist: c47116e909 _without_ the patches also appears to be working > fine. The last kernel I know for sure deadlocks is b36f469a15, so I'm > going to test cd25b0f740 and 28d2e3b5de. c47116e909 with cd25b0f740 and 28d2e3b5de reverted deadlocks, see attached ddb.

Re: ZFS deadlock in 14

I believe the below quoted messages were reports of deadlocks based on after the following 2 MFV being in place in their environments: Thu, 10 Aug 2023 . . . • git: cd25b0f740f8 - main - zfs: cherry-pick fix from openzfs Martin Matuska • git: 28d2e3b5dedf - main - zfs: cherry-pick fix fr

Possible regression in main causing poor performance

ets laying around from last week (everything is a pristine environment, etc.), this week's builds are taking forever: r...@releng1.nyi:/releng/scripts-snapshot/scripts # ./thermite.sh -c ./builds-14.conf ; echo ^G 20230818-00:15:44 INFO: Creating /releng/scripts-snapshot/logs 20

New FreeBSD snapshots available: main (ALPHA2) (20230819 77013f29d048)

ailable on the Hashicorp Atlas site for the VMWare Desktop and VirtualBox providers, and can be installed by running: % vagrant init freebsd/FreeBSD-14.0-ALPHA2 % vagrant up == ISO CHECKSUMS == o 14.0-ALPHA2 amd64 GENERIC: SHA512 (FreeBSD-14.0-ALPHA2-amd64-20230818-77013f29d048-264841-bo

Re: Possible regression in main causing poor performance

last week (everything is a pristine environment, etc.), this week's > builds are taking forever: My confusion may extend to this "no changes" status vs. the uname output identifying the kernel is from mid July. > r...@releng1.nyi:/releng/scripts-snapshot/scripts # ./thermi

Re: Possible regression in main causing poor performance

x27;s > > builds are taking forever: > > My confusion may extend to this "no changes" status vs. the uname > output identifying the kernel is from mid July. > It is admittedly a month versus two weeks difference here. My fault. > > r...@releng1.nyi:/releng

Re: Possible regression in main causing poor performance

etc.), this week's >> builds are taking forever: > > My confusion may extend to this "no changes" status vs. the uname > output identifying the kernel is from mid July. > >> r...@releng1.nyi:/releng/scripts-snapshot/scripts # ./thermite.sh -c >> ./build