Re: FreeBSD NFSv4.1/4.2 server is broken when Linux mounts use "nconnects"

On Mon, Mar 29, 2021 at 3:52 PM Rick Macklem wrote: > Hi, > > The FreeBSD NFS server is broken when handling multiple > connections for NFSv4.1/4.2. > It incorrectly binds the back channel to a new connection > when is sees an RPC with Sequence in it (almost all RPCs) > and might send a callback

Re: ZFS (in virtual machine): $HOME being a dataset causes xauth to timeout- access delays?

On Thu, Apr 01, 2021 at 07:18:56PM -1000, parv/freebsd wrote: > On Thu, Apr 1, 2021 at 3:38 PM parv/freebsd wrote: > > I am wondering if $SRC_BASE, $MAKEOBJDIRPREFIX, & $WRKDIRPREFIX being > ZFS datasets now would increase compile time. I will found that out in > few weeks (in case of buildworld

ZFS (in virtual machine): $HOME being a dataset causes xauth to timeout- access delays?

Hi there, I have FreeBSD 12-STABLE in VirtualBox 5.2.44 on Windows 10. All the "disks" are file-backed virtual disks. I noticed that after making $HOME a ZFS dataset, there were delays ... - generally in start of Xorg; - exhibited by xauth (after using "startx") error messages about timeout

Re: ZFS (in virtual machine): $HOME being a dataset causes xauth to timeout- access delays?

On Thu, Apr 1, 2021 at 3:38 PM parv/freebsd wrote: I am wondering if $SRC_BASE, $MAKEOBJDIRPREFIX, & $WRKDIRPREFIX being ZFS datasets now would increase compile time. I will found that out in few weeks (in case of buildworld & kernel) as earlier I had both $SRC_BASE & $MAKEOBJDIRPREFIX as plain

ZFS (in virtual machine): $HOME being a dataset causes xauth to timeout- access delays?

Hi there, I have FreeBSD 12-STABLE in VirtualBox 5.2.44 on Windows 10. All the "disks" are file-backed virtual disks. I noticed that after making $HOME a ZFS dataset, there were delays ... - generally in start of Xorg; - exhibited by xauth (after using "startx") error messages about timeout

ACPI poweroff is not working on 13.0

Sorry, subject is too loud, but... My MB is ASUS M5A97R2.0. On FreeBSD v10, 11 and 12 ACPI poweroff (shutdown -p, halt -p, short click on power button) works as expected. After upgrade to 13.0 it does not power the system off anymore. The process comes to "re0: link state changed to DOWN" as

Re: Vinum deprecation for FreeBSD 14 - are there any remaining Vinum users?

On Thu, Apr 01, 2021 at 11:20:44AM +0300, Lev Serebryakov wrote: | On 01.04.2021 2:39, Doug Ambrisko wrote: | | > | > I can only state that I use it only occasionally, and that when I do. I | > | > have had no problems with it. I'm glad that it's there when I need it. | > | | > | Thanks for the

Re: Vinum deprecation for FreeBSD 14 - are there any remaining Vinum users?

On 01.04.2021 2:39, Doug Ambrisko wrote: | > I can only state that I use it only occasionally, and that when I do. I | > have had no problems with it. I'm glad that it's there when I need it. | | Thanks for the reply. Can you comment on your use cases - in | particular, did you use mirror,

Re: Vinum deprecation for FreeBSD 14 - are there any remaining Vinum users?

On Fri, Mar 26, 2021 at 10:22:53AM -0400, Ed Maste wrote: | On Thu, 25 Mar 2021 at 15:09, Chris wrote: | > | > I can only state that I use it only occasionally, and that when I do. I | > have had no problems with it. I'm glad that it's there when I need it. | | Thanks for the reply. Can you

FreeBSD 13.0-RC4 with filesystem quotas

Hello, I create a bug report here about "mount" command not showing quotas enabled after a reboot. More information here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254682 Can someone running 13.0-RC4 with quotas enabled to

Re: Update to the 13.0-RELEASE schedule

We don't even start before .1 is out. Am 31.03.21 um 19:24 schrieb Rainer Duffner: > >> Am 31.03.2021 um 17:58 schrieb Glen Barber : >> >> A small set of updates that we consider blocking the 13.0 release have >> been brought to our attention. As such, the 13.0-RELEASE schedule has >> been

Re: Update to the 13.0-RELEASE schedule

> Am 31.03.2021 um 17:58 schrieb Glen Barber : > > A small set of updates that we consider blocking the 13.0 release have > been brought to our attention. As such, the 13.0-RELEASE schedule has > been updated to include a fifth release candidate (RC5). > > The updated schedule is available on

Re: Update to the 13.0-RELEASE schedule

On Wed, Mar 31, 2021 at 03:58:51PM +, Glen Barber wrote: > A small set of updates that we consider blocking the 13.0 release have > been brought to our attention. As such, the 13.0-RELEASE schedule has > been updated to include a fifth release candidate (RC5). > > The updated schedule is

Re: FreeBSD-13.0-RC1-amd64-disc1.iso unbootable on memstick

> > Hi. > > > > Are you shure you're using *.memstick.img? > > I am shure I am NOT using memstick, as the subject says > I am using: > FreeBSD-13.0-RC1-amd64-disc1.iso > > > > *.iso are for optical drives. > > Ah, not since 12.0, these are now "hybrid" type images that > are designed to

Update to the 13.0-RELEASE schedule

A small set of updates that we consider blocking the 13.0 release have been brought to our attention. As such, the 13.0-RELEASE schedule has been updated to include a fifth release candidate (RC5). The updated schedule is available on the FreeBSD Project website:

Re: possibly silly question regarding freebsd-update

Hi, On Tue, Mar 30, 2021 at 12:52:59PM -0500, Doug McIntyre wrote: On Tue, Mar 30, 2021 at 05:54:03PM +0100, tech-lists wrote: it just threw me that the thing-that-was-updated didn't update its version information when queried. Absent sources, how can I tell it was updated (apart from

Re: FreeBSD 13.0-RC4 and Nginx process "stuck" during restart

On Wed, Mar 31, 2021 at 3:55 AM Christos Chatzaras wrote: > > With the patch I can't reproduce the issue. Can you please MFC it to > 13.0-STABLE and 13.0 ? > Thanks for doing the testing! I've committed the MFC to stable/13. I'll request re@ approval to pull it up to 13.0. Jonathan

Re: qlnxe driver not in 13.0 arm64

On 3/30/21 8:31 PM, John-Mark Gurney wrote: Daniel Morante via freebsd-stable wrote this message on Sun, Mar 28, 2021 at 03:23 -0400: I installed 13.0-RC3 ARM64 from the DVD ISO image (FreeBSD-13.0-BETA4-arm64-aarch64-dvd1.iso

Re: FreeBSD 13.0-RC4 and Nginx process "stuck" during restart

> On 31 Mar 2021, at 02:31, Jonathan T. Looney wrote: > > On Tue, Mar 30, 2021 at 12:01 PM Christos Chatzaras > wrote: > > Did you notice it with nginx too or something else? I also run monit, bind, > dovecot, postfix, mysql, php-fpm and pure-ftpd and didn't

Re: qlnxe driver not in 13.0 arm64

I tried to move the lines, but maybe I did something wrong since it failed to build. make[3]: stopped in /usr/src/sys/modules *** [modules-all] Error code 2 make[2]: stopped in /usr/obj/usr/src/arm64.aarch64/sys/THUNDERX2 15 errors The full output is here:

powerpc64le is missing in: https://www.freebsd.org/platforms/

When I looked at https://www.freebsd.org/platforms/ I noticed that "64-bit little-endian PowerPC" powerpc64le is not listed. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-stable@freebsd.org mailing list

Re: qlnxe driver not in 13.0 arm64

To test it with a custom kernel, would I only need to add these lines (https://cgit.freebsd.org/src/tree/sys/conf/files.amd64#n279-306)? |dev/qlnx/qlnxe/ecore_cxt.c optional qlnxe pci \ compile-with "${LINUXKPI_C}" dev/qlnx/qlnxe/ecore_dbg_fw_funcs.c optional qlnxe pci \ compile-with

Re: possibly silly question regarding freebsd-update

uname -aU: FreeBSD t450s.local.lan 12.2-RELEASE-p4 FreeBSD 12.2-RELEASE-p4 GENERIC amd64 1202000 freebsd-version: 12.2-RELEASE-p5 cat /etc/os-release NAME=FreeBSD VERSION=12.2-RELEASE-p5 VERSION_ID=12.2 ID=freebsd ANSI_COLOR="0;31" PRETTY_NAME="FreeBSD 12.2-RELEASE-p5"

Re: FreeBSD 13.0-RC4 and Nginx process "stuck" during restart

> On 31 Mar 2021, at 02:31, Jonathan T. Looney wrote: > > On Tue, Mar 30, 2021 at 12:01 PM Christos Chatzaras > wrote: > > Did you notice it with nginx too or something else? I also run monit, bind, > dovecot, postfix, mysql, php-fpm and pure-ftpd and didn't

Re: FreeBSD 13.0-RC4 and Nginx process "stuck" during restart

On Tue, Mar 30, 2021 at 12:01 PM Christos Chatzaras wrote: > > Did you notice it with nginx too or something else? I also run monit, > bind, dovecot, postfix, mysql, php-fpm and pure-ftpd and didn't notice any > restart of these services to "stuck". > Yes, we noticed it in Nginx; however, we

Re: qlnxe driver not in 13.0 arm64

Daniel Morante via freebsd-stable wrote this message on Sun, Mar 28, 2021 at 03:23 -0400: > I installed 13.0-RC3 ARM64 from the DVD ISO image > (FreeBSD-13.0-BETA4-arm64-aarch64-dvd1.iso > ).

Re: possibly silly question regarding freebsd-update

On 31/03/2021 12:35 am, tech-lists wrote: > Hi, > > Recently there was > https://lists.freebsd.org/pipermail/freebsd-security/2021-March/010380.html > about openssl. Upgraded to 12.2-p5 with freebsd-update and rebooted. > > What I'm unsure about is the openssl version. > Up-to-date 12.1-p5

Re: possibly silly question regarding freebsd-update

On Tue, Mar 30, 2021 at 05:54:03PM +0100, tech-lists wrote: > it just threw me that the thing-that-was-updated didn't update its > version information when queried. Absent sources, how can I tell it > was updated (apart from freebsd-version -u) ? Comparing what the SA patch says it is doing at

Re: possibly silly question regarding freebsd-update

On Tue, Mar 30, 2021 at 12:07:41PM -0400, Karl Denninger wrote: Ok, that's fair; it DOES show -p5 for the user side. $ freebsd-version -ru 12.2-RELEASE-p4 12.2-RELEASE-p5 So that says my userland is -p5 while the kernel, which did not change (even though if you built from source it would

Re: possibly silly question regarding freebsd-update

On Tue, Mar 30, 2021 at 11:55:24AM -0400, Karl Denninger wrote: How do I *know*, without source to go look at, whether or not the fix is present on a binary system? Yep, you understand my point exactly. -- J. signature.asc Description: PGP signature

Re: possibly silly question regarding freebsd-update

On 3/30/2021 12:02, Gary Palmer wrote: On Tue, Mar 30, 2021 at 11:55:24AM -0400, Karl Denninger wrote: On 3/30/2021 11:22, Guido Falsi via freebsd-stable wrote: On 30/03/21 15:35, tech-lists wrote: Hi, Recently there was

Re: possibly silly question regarding freebsd-update

On Tue, Mar 30, 2021 at 11:55:24AM -0400, Karl Denninger wrote: > > On 3/30/2021 11:22, Guido Falsi via freebsd-stable wrote: > > On 30/03/21 15:35, tech-lists wrote: > > > Hi, > > > > > > Recently there was > > > https://lists.freebsd.org/pipermail/freebsd-security/2021-March/010380.html > > >

Re: FreeBSD 13.0-RC4 and Nginx process "stuck" during restart

> On 30 Mar 2021, at 18:40, Jonathan T. Looney wrote: > > Yes, it could be related. Because of the timing of when we first saw the > behavior, I assumed the trigger for the behavior (which remains unknown) only > existed in main. However, it is possible that this behavior is now being >

Re: possibly silly question regarding freebsd-update

On 3/30/2021 11:22, Guido Falsi via freebsd-stable wrote: On 30/03/21 15:35, tech-lists wrote: Hi, Recently there was https://lists.freebsd.org/pipermail/freebsd-security/2021-March/010380.html about openssl. Upgraded to 12.2-p5 with freebsd-update and rebooted. What I'm unsure about is

Re: possibly silly question regarding freebsd-update

On 30/03/21 17:38, tech-lists wrote: On Tue, Mar 30, 2021 at 05:22:30PM +0200, Guido Falsi via freebsd-stable wrote: No, as you can see in the commit in the official git [1] while for current and stable the new upstream version of openssl was imported for the release the fix was applied

Re: FreeBSD 13.0-RC4 and Nginx process "stuck" during restart

On Mon, Mar 29, 2021 at 3:57 PM Christos Chatzaras wrote: > Hello, > > > I upgrade from 12.2 to 13.0-RC4 and I notice a strange issue with Nginx. > > When I run "service nginx restart" in some (random) servers it > doesn't complete the restart and it "stucks" at "Waiting for PIDS: 20536." . > >

Re: possibly silly question regarding freebsd-update

On Tue, Mar 30, 2021 at 05:22:30PM +0200, Guido Falsi via freebsd-stable wrote: No, as you can see in the commit in the official git [1] while for current and stable the new upstream version of openssl was imported for the release the fix was applied without importing the new release and

Re: FreeBSD 13.0-RC4 and Nginx process "stuck" during restart

On Tue, Mar 30, 2021 at 04:48:25PM +0300, Christos Chatzaras wrote: > > > > On 30 Mar 2021, at 16:45, Mark Johnston wrote: > > > > On Mon, Mar 29, 2021 at 10:57:09PM +0300, Christos Chatzaras wrote: > >> Hello, > >> > >> > >> I upgrade from 12.2 to 13.0-RC4 and I notice a strange issue with

Re: possibly silly question regarding freebsd-update

Hi, On Tue, Mar 30, 2021 at 11:01:20AM -0400, Karl Denninger wrote: It is not updating; as I noted it appears this security patch was NOT backported and thus 12.2-RELEASE does not "see" it. ok, then I guess I need to post to -security? Because the notice suggests that it was. You cannot go

Re: possibly silly question regarding freebsd-update

On 30/03/21 15:35, tech-lists wrote: Hi, Recently there was https://lists.freebsd.org/pipermail/freebsd-security/2021-March/010380.html about openssl. Upgraded to 12.2-p5 with freebsd-update and rebooted. What I'm unsure about is the openssl version. Up-to-date 12.1-p5 instances report OpenSSL

Re: possibly silly question regarding freebsd-update

On 3/30/2021 10:40, tech-lists wrote: On Tue, Mar 30, 2021 at 09:14:56AM -0500, Doug McIntyre wrote: Like the patch referenced in the SA. https://security.FreeBSD.org/patches/SA-21:07/openssl-12.patch Again, it seems like confusion over what happens in RELEASE, STABLE and CURRENT.. Hi, I'm

Re: possibly silly question regarding freebsd-update

On Tue, Mar 30, 2021 at 09:14:56AM -0500, Doug McIntyre wrote: Like the patch referenced in the SA. https://security.FreeBSD.org/patches/SA-21:07/openssl-12.patch Again, it seems like confusion over what happens in RELEASE, STABLE and CURRENT.. Hi, I'm not sure what you mean by this. In

Re: possibly silly question regarding freebsd-update

On Tue, Mar 30, 2021 at 04:05:32PM +0200, Ruben via freebsd-stable wrote: Hi, Did you mean 12.1-p5 or 12.2-p5 ? I'm asking because you refer to both 12.1-p5 and 12.2-p5 (typo?). yes, I meant 12.2-p5, sorry -- J. signature.asc Description: PGP signature

Re: possibly silly question regarding freebsd-update

freebsd-update fetch and freebsd-update install?? Brian On 3/30/2021 7:18 AM, Karl Denninger wrote: On 3/30/2021 10:14, Doug McIntyre wrote: Like the patch referenced in the SA. https://security.FreeBSD.org/patches/SA-21:07/openssl-12.patch Again, it seems like confusion over what happens

Re: possibly silly question regarding freebsd-update

On 3/30/2021 10:14, Doug McIntyre wrote: Like the patch referenced in the SA. https://security.FreeBSD.org/patches/SA-21:07/openssl-12.patch Again, it seems like confusion over what happens in RELEASE, STABLE and CURRENT.. On Tue, Mar 30, 2021 at 04:05:32PM +0200, Ruben via

Re: possibly silly question regarding freebsd-update

Like the patch referenced in the SA. https://security.FreeBSD.org/patches/SA-21:07/openssl-12.patch Again, it seems like confusion over what happens in RELEASE, STABLE and CURRENT.. On Tue, Mar 30, 2021 at 04:05:32PM +0200, Ruben via freebsd-stable wrote: > Hi, > > Did you mean 12.1-p5 or

Re: possibly silly question regarding freebsd-update

Hi, Did you mean 12.1-p5 or 12.2-p5 ? I'm asking because you refer to both 12.1-p5 and 12.2-p5 (typo?). If you meant 12.2-p5: Perhaps the FreeBSD security team did not bump the version, but "only" backported the patches to version 1.1.1h ? Regards, Ruben On 3/30/21 3:35 PM, tech-lists

Re: FreeBSD 13.0-RC4 and Nginx process "stuck" during restart

> On 30 Mar 2021, at 16:45, Mark Johnston wrote: > > On Mon, Mar 29, 2021 at 10:57:09PM +0300, Christos Chatzaras wrote: >> Hello, >> >> >> I upgrade from 12.2 to 13.0-RC4 and I notice a strange issue with Nginx. >> >> When I run "service nginx restart" in some (random) servers it doesn't

Re: FreeBSD 13.0-RC4 and Nginx process "stuck" during restart

On Mon, Mar 29, 2021 at 10:57:09PM +0300, Christos Chatzaras wrote: > Hello, > > > I upgrade from 12.2 to 13.0-RC4 and I notice a strange issue with Nginx. > > When I run "service nginx restart" in some (random) servers it doesn't > complete the restart and it "stucks" at "Waiting for PIDS:

possibly silly question regarding freebsd-update

Hi, Recently there was https://lists.freebsd.org/pipermail/freebsd-security/2021-March/010380.html about openssl. Upgraded to 12.2-p5 with freebsd-update and rebooted. What I'm unsure about is the openssl version. Up-to-date 12.1-p5 instances report OpenSSL 1.1.1h-freebsd 22 Sep 2020

Re: FreeBSD NFSv4.1/4.2 server is broken when Linux mounts use "nconnects"

On 30/03/2021 8:52 am, Rick Macklem wrote: Hi, The FreeBSD NFS server is broken when handling multiple connections for NFSv4.1/4.2. Whats the version scope for this issue? If a regression in 12.x 13.x, adding to RELNOTES and ERRATA would be great It incorrectly binds the back channel to a

FreeBSD 13.0-RC4 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The fourth RC build of the 13.0-RELEASE release cycle is now available. Installation images are available for: o 13.0-RC4 amd64 GENERIC o 13.0-RC4 i386 GENERIC o 13.0-RC4 powerpc GENERIC o 13.0-RC4 powerpc64 GENERIC64 o 13.0-RC4 powerpc64le

Re: FreeBSD NFSv4.1/4.2 server is broken when Linux mounts use "nconnects"

On Mon, Mar 29, 2021 at 3:52 PM Rick Macklem wrote: > Hi, > > The FreeBSD NFS server is broken when handling multiple > connections for NFSv4.1/4.2. > It incorrectly binds the back channel to a new connection > when is sees an RPC with Sequence in it (almost all RPCs) > and might send a callback

FreeBSD NFSv4.1/4.2 server is broken when Linux mounts use "nconnects"

Hi, The FreeBSD NFS server is broken when handling multiple connections for NFSv4.1/4.2. It incorrectly binds the back channel to a new connection when is sees an RPC with Sequence in it (almost all RPCs) and might send a callback on the wrong connection. I have a fix, but it won't be in a

FreeBSD 13.0-RC4 and Nginx process "stuck" during restart

Hello, I upgrade from 12.2 to 13.0-RC4 and I notice a strange issue with Nginx. When I run "service nginx restart" in some (random) servers it doesn't complete the restart and it "stucks" at "Waiting for PIDS: 20536." . I can kill the 20536 process and then restart completes. procstat -kk

qlnxe driver not in 13.0 arm64

I installed 13.0-RC3 ARM64 from the DVD ISO image (FreeBSD-13.0-BETA4-arm64-aarch64-dvd1.iso ). There is no "if_qlnxe" kernel model present on the install media, or on the system after

Re: build failed for 12.2-p5

On Sat, Mar 27, 2021 at 02:52:09PM +0100, Miroslav Lachman wrote: The same error is there after make delete-old + delete-old-libs again. I am out of ideas. Hi, does it have a /etc/src.conf? if so, does it use ccache? The way i'd build 12.2-p5 from scratch would be like this: 1. rm -rf

Re: build failed for 12.2-p5

On 27/03/2021 14:23, Miroslav Lachman wrote: On 27/03/2021 13:57, Juraj Lutter wrote: On 27 Mar 2021, at 13:24, Miroslav Lachman <000.f...@quip.cz> wrote: [Creating objdir /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/kerberos5/lib/libroken...] make-roken > roken.h *** Signal 11 Stop.

Re: WITHOUT_KERNEL_SYMBOLS - *.ko now with debug_info

add Cc: current@ On Mon, 22 Mar 2021 02:17:11 +0100, "Herbert J. Skuhra" wrote: > > On Sun, Mar 21, 2021 at 11:11:08PM +0100, Herbert J. Skuhra wrote: > > Hi, > > > > since upgrading to stable/13 I was wondering why /boot/kernel is much > > larger. When using "WITHOUT_KERNEL_SYMBOLS=" in

Re: build failed for 12.2-p5

On 27/03/2021 13:57, Juraj Lutter wrote: On 27 Mar 2021, at 13:24, Miroslav Lachman <000.f...@quip.cz> wrote: [Creating objdir /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/kerberos5/lib/libroken...] make-roken > roken.h *** Signal 11 Stop. make[3]: stopped in /usr/src/kerberos5/lib/libroken

Re: build failed for 12.2-p5

> On 27 Mar 2021, at 13:24, Miroslav Lachman <000.f...@quip.cz> wrote: > [Creating objdir > /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/kerberos5/lib/libroken...] > make-roken > roken.h > *** Signal 11 > > Stop. > make[3]: stopped in /usr/src/kerberos5/lib/libroken > *** Error code 1 > ***

Re: build failed for 12.2-p5

On 27/03/2021 12:57, Dimitry Andric wrote: On 27 Mar 2021, at 12:39, Miroslav Lachman <000.f...@quip.cz> wrote: [...] # make -DNO_CLEAN buildkernel cc -O2 -pipe -fno-common -I/usr/src/crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/usr/src/kerberos5/include -g -MD -MF.depend.copyhostent.o

Re: build failed for 12.2-p5

On 27 Mar 2021, at 12:39, Miroslav Lachman <000.f...@quip.cz> wrote: > > I compiled 12.2-p4 from sources 2 days ago but any attempt to build update > for 12.2-p5 ends with error. > > Previous build was done on 11.4: > > # cd /usr/src/ > # git clone https://github.com/freebsd/freebsd.git -b

build failed for 12.2-p5

I compiled 12.2-p4 from sources 2 days ago but any attempt to build update for 12.2-p5 ends with error. Previous build was done on 11.4: # cd /usr/src/ # git clone https://github.com/freebsd/freebsd.git -b releng/12.2 ./ # make buildworld # make buildkernel 11.4 machine was upgraded to 12.2

Re: Vinum deprecation for FreeBSD 14 - are there any remaining Vinum users?

On 2021-03-26 07:22, Ed Maste wrote: On Thu, 25 Mar 2021 at 15:09, Chris wrote: I can only state that I use it only occasionally, and that when I do. I have had no problems with it. I'm glad that it's there when I need it. Thanks for the reply. Can you comment on your use cases - in

Re: Vinum deprecation for FreeBSD 14 - are there any remaining Vinum users?

On Thu, 25 Mar 2021 at 15:09, Chris wrote: > > I can only state that I use it only occasionally, and that when I do. I > have had no problems with it. I'm glad that it's there when I need it. Thanks for the reply. Can you comment on your use cases - in particular, did you use mirror, stripe, or

Re: Vinum deprecation for FreeBSD 14 - are there any remaining Vinum users?

On 2021-03-25 10:25, Ed Maste wrote: Vinum is a Logical Volume Manager that was introduced in FreeBSD 3.0, and for FreeBSD 5 was ported to geom(4) as gvinum. gvinum has had no specific development at least as far back as 2010 and it is not clear how well it works today. There are open PRs with

Vinum deprecation for FreeBSD 14 - are there any remaining Vinum users?

Vinum is a Logical Volume Manager that was introduced in FreeBSD 3.0, and for FreeBSD 5 was ported to geom(4) as gvinum. gvinum has had no specific development at least as far back as 2010 and it is not clear how well it works today. There are open PRs with reports of panics upon removing disks,

13.0-RELEASE schedule update

At least one issue has been brought to our attention that affects new installations, which as we currently have no precedent for re-rolling ISOs and/or VM images post-release, warrant adding RC4 to the 13.0 schedule. Please be advised that we are still only accepting critical changes only, with

Re: Filesystem operations slower in 13.0 than 12.2

On 2021-Mar-22, at 22:51, Kevin Oberman wrote: > On Mon, Mar 22, 2021 at 8:19 AM Adrian Chadd wrote: >> On Mon, 15 Mar 2021 at 14:58, Kevin Oberman wrote: >> >> > > >> > > It appears that the messages are associated with reading >> > > the disk(s), not directly with writing them, where the

Re: Filesystem operations slower in 13.0 than 12.2

On Mon, Mar 22, 2021 at 8:19 AM Adrian Chadd wrote: > On Mon, 15 Mar 2021 at 14:58, Kevin Oberman wrote: > > > > > > > It appears that the messages are associated with reading > > > the disk(s), not directly with writing them, where the > > > reads take more than "hz * 20" time units to

Re: Filesystem operations slower in 13.0 than 12.2

On Mon, 15 Mar 2021 at 14:58, Kevin Oberman wrote: > > > > It appears that the messages are associated with reading > > the disk(s), not directly with writing them, where the > > reads take more than "hz * 20" time units to complete. > > (I'm looking at main (14) code.) What might contribute > >

Re: Help with applying a differential

> Am 22.03.2021 um 17:59 schrieb Warner Losh : > > > > On Mon, Mar 22, 2021, 10:19 AM Rainer Duffner > wrote: > > > > Am 22.03.2021 um 16:34 schrieb Juraj Lutter > >: > > > > > > To which branch do you want to apply those patches? >

Re: Help with applying a differential

On Mon, Mar 22, 2021, 10:19 AM Rainer Duffner wrote: > > > > Am 22.03.2021 um 16:34 schrieb Juraj Lutter : > > > > > > To which branch do you want to apply those patches? > > > > Judging from the original patch date, I’d say that they have been > developed against 13.0 at some point. > > That

Re: Help with applying a differential

> Am 22.03.2021 um 16:34 schrieb Juraj Lutter : > > > To which branch do you want to apply those patches? > > Judging from the original patch date, I’d say that they have been developed > against 13.0 at some point. > That being said, you may want to try to apply them manually against 13.0

Re: FreeBSD 13.0-RC3 Now Available

On Mon, Mar 22, 2021 at 01:39:06PM +0100, Goran Mekić wrote: > Hello, > > I see the RC3 in the "Latest News" but not here: > https://www.freebsd.org/releases/13.0R/schedule/ > I hope I'm writing to the proper channels/list about this. > Fixed. Thank you for the report. Glen signature.asc

Help with applying a differential

Hi, I need help applying this differential https://reviews.freebsd.org/D24428 Me and a co-worker (who is one order of magnitude better at all things git than me) are unable to get this to apply. rduffner@suse5:~/freebsd-src/sys/dev/smartpqi> git apply --check ~/Downloads/D24428.diff

Re: FreeBSD 13.0-RC3 Now Available

Hello, I see the RC3 in the "Latest News" but not here: https://www.freebsd.org/releases/13.0R/schedule/ I hope I'm writing to the proper channels/list about this. Regards, meka signature.asc Description: PGP signature

Re: FreeBSD 13.0-RC3 Now Available

On Sun, 21 Mar 2021 at 03:08, Glen Barber wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > The third RC build of the 13.0-RELEASE release cycle is now available. > > === Upgrading === > > The freebsd-update(8) utility supports binary upgrades of amd64, i386, > and aarch64 systems

Re: WITHOUT_KERNEL_SYMBOLS - *.ko now with debug_info

On Sun, Mar 21, 2021 at 11:11:08PM +0100, Herbert J. Skuhra wrote: > Hi, > > since upgrading to stable/13 I was wondering why /boot/kernel is much > larger. When using "WITHOUT_KERNEL_SYMBOLS=" in /etc/src.conf the > kernel modules now contain debug_info. OK? (I manually run "objcopy >

WITHOUT_KERNEL_SYMBOLS - *.ko now with debug_info

Hi, since upgrading to stable/13 I was wondering why /boot/kernel is much larger. When using "WITHOUT_KERNEL_SYMBOLS=" in /etc/src.conf the kernel modules now contain debug_info. OK? (I manually run "objcopy --strip-debug".) FreeBSD 13.0-STABLE #60 stable/13-n245000-12349e667ced: $ cat

Re: FreeBSD 13.0-RC3 Now Available

Hi! > The third RC build of the 13.0-RELEASE release cycle is now available. Upgrading a 13.0-RC2 poudriere jail to RC3 seems to fail ? # poudriere jail -u -j 130 -t 13.0-RC3 [...] To install the downloaded upgrades, run "/usr/sbin/freebsd-update.fixed install". Installing updates...Scanning

Re: ThinkPad X1 Carbon Gen 4 unable to boot 13.0-RC1

On 3/20/21 10:26 AM, Kevin Oberman wrote: On Sat, Mar 20, 2021 at 8:35 AM Fred via freebsd-stable < freebsd-stable@freebsd.org> wrote: On 3/19/21 7:59 PM, Mathias Picker wrote: Fred Hall via freebsd-stable writes: I have a ThinkPad X1 Carbon Gen 4 (20FCS0NB00) which has happily run

Re: kldload zfs spins the system after upgrading from 12.2 to 13-BETA

On 20/03/2021 05:01, Yoshihiro Ota wrote: > On Tue, 9 Mar 2021 11:24:53 +0200 > Andriy Gapon wrote: > >> On 08/03/2021 05:24, Yoshihiro Ota wrote: >>> On Sun, 7 Mar 2021 00:09:33 +0200 >>> Andriy Gapon wrote: >>> On 06/03/2021 20:09, Yoshihiro Ota wrote: > Hi all, > > I'm

Re: ThinkPad X1 Carbon Gen 4 unable to boot 13.0-RC1

On Sat, Mar 20, 2021 at 8:35 AM Fred via freebsd-stable < freebsd-stable@freebsd.org> wrote: > On 3/19/21 7:59 PM, Mathias Picker wrote: > > > > Fred Hall via freebsd-stable writes: > > > >> I have a ThinkPad X1 Carbon Gen 4 (20FCS0NB00) which has happily run > >> FreeBSD 11 and 12, but which

FreeBSD 13.0-RC3 Now Available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The third RC build of the 13.0-RELEASE release cycle is now available. Installation images are available for: o 13.0-RC3 amd64 GENERIC o 13.0-RC3 i386 GENERIC o 13.0-RC3 powerpc GENERIC o 13.0-RC3 powerpc64 GENERIC64 o 13.0-RC3 powerpc64le

Re: Rasberry Pi 4 has no USB

Carl Johnson writes: > Emmanuel Vadot writes: > >> On Sun, 28 Feb 2021 09:26:23 -0800 >> Carl Johnson wrote: >> >>> I have an 8GB RPi 4B that I am trying out, but it has no USB response at >>> all. That means that I can't use a keyboard or mouse, but I can use a >>> serial console and

Re: ThinkPad X1 Carbon Gen 4 unable to boot 13.0-RC1

On 3/19/21 7:59 PM, Mathias Picker wrote: Fred Hall via freebsd-stable writes: I have a ThinkPad X1 Carbon Gen 4 (20FCS0NB00) which has happily run FreeBSD 11 and 12, but which can't boot 13.0-RC1 from memstick or via freebsd-update. In both cases the boot process locks up on the line

Request: Mount zfs encrypted datasets at boot? Re: FreeBSD 13.0-RC2 Now Available

Hi, > On 13 Mar 2021, at 1:11, Glen Barber wrote: > > The second RC build of the 13.0-RELEASE release cycle is now available. Might it be interesting to change the zfs mount -a / zfs unmount -a in /etc/rc.d/zfs to zfs mount -al / zfs unmount -au so that filesystems using the openzfs

Re: kldload zfs spins the system after upgrading from 12.2 to 13-BETA

On Tue, 9 Mar 2021 11:24:53 +0200 Andriy Gapon wrote: > On 08/03/2021 05:24, Yoshihiro Ota wrote: > > On Sun, 7 Mar 2021 00:09:33 +0200 > > Andriy Gapon wrote: > > > >> On 06/03/2021 20:09, Yoshihiro Ota wrote: > >>> Hi all, > >>> > >>> I'm upgrading fron 12.2-RELEASE to 13-BETA/RC one by one.

Re: ThinkPad X1 Carbon Gen 4 unable to boot 13.0-RC1

Fred Hall via freebsd-stable writes: I have a ThinkPad X1 Carbon Gen 4 (20FCS0NB00) which has happily run FreeBSD 11 and 12, but which can't boot 13.0-RC1 from memstick or via freebsd-update. In both cases the boot process locks up on the line "hwpstate_intel0: on cpu0" If running

Important Message sta...@freebsd.org

Dear ANZ customer Your ANZ Internet Banking access has been violated. We suspected someone other than you with IP 178.210.92*** trying to access your information's. Please verify your banking information with us to

ThinkPad X1 Carbon Gen 4 unable to boot 13.0-RC1

I have a ThinkPad X1 Carbon Gen 4 (20FCS0NB00) which has happily run FreeBSD 11 and 12, but which can't boot 13.0-RC1 from memstick or via freebsd-update. In both cases the boot process locks up on the line "hwpstate_intel0: on cpu0" If running freebsd-update, a work around is to add

Re: 13.0-RC2 / 14-CURRENT: Processes getting stuck in vlruwk state

To sum up what happened, Yamagi was kind enough to test several patches and ultimately the issue got solved here https://cgit.freebsd.org/src/commit/?id=e9272225e6bed840b00eef1c817b188c172338ee . The patch also got merged into releng/13.0 On 3/17/21, Yamagi wrote: > Hi, > me and some other users

13-RC2 Serial Console not accepting Input

I upgraded a system from 12.2 to 13-RC2 running on an PC Engines Alix APU1D4 system board. It boots and works fine, however despite console output displaying fine, it will not accept any keyboard input. I have the following in my /boot/loader.conf # Enable Serial Console console="comconsole"

Re: 13.0-RC2 / 14-CURRENT: Processes getting stuck in vlruwk state

Thanks, I'm going to have to ponder a little bit. In the meantime can you apply this: https://people.freebsd.org/~mjg/maxvnodes.diff Once you boot, tweak maxvnodes: sysctl kern.maxvnodes=1049226 Run poudriere. Once it finishes, inspect sysctl vfs.highest_numvnodes On 3/17/21, Yamagi wrote: >

Re: 13.0-RC2 / 14-CURRENT: Processes getting stuck in vlruwk state

This time poudriere came to an end: % sysctl vfs.highest_numvnodes vfs.highest_numvnodes: 500976 On Wed, 17 Mar 2021 18:55:43 +0100 Mateusz Guzik wrote: > Thanks, I'm going to have to ponder a little bit. > > In the meantime can you apply this: >

Re: 13.0-RC2 / 14-CURRENT: Processes getting stuck in vlruwk state

Can you reproduce the problem and run obtain "sysctl -a"? In general, there is a vnode limit which is probably too small. The reclamation mechanism is deficient in that it will eventually inject an arbitrary pause. On 3/17/21, Yamagi wrote: > Hi, > me and some other users in the ##bsdforen.de

Re: 13.0-RC2 / 14-CURRENT: Processes getting stuck in vlruwk state

Hi Mateusz, the sysctl output after about 10 minutes into the problem is attached. In case that its stripped by Mailman a copy can be found here: https://deponie.yamagi.org/temp/sysctl_vlruwk.txt.xz Regards, Yamagi On Wed, 17 Mar 2021 15:57:59 +0100 Mateusz Guzik wrote: > Can you reproduce the

Re: Updating to 13-stable and existing ZFS pools: any gotchas?

On 2021-03-17 9:59 am, tech-lists wrote: On Sun, Mar 14, 2021 at 09:59:21AM +0100, Stefan Bethke wrote: I'm planning to upgrade three production machines with existing ZFS pools to 13-stable. Is there anything I need to pay attention to wrt OpenZFS? Or should it be fully transparent, apart

<    1   2   3   4   5   6   7   8   9   10   >