RE: Livelock on recent current

> On 09.09.20 06:18, Kevin Oberman wrote: > > I am seeing a problem since I moved to current on my laptop this week. > > It's odd as it is linked to the keyboard. As long as the keyboard is > > active, everything is fine, but if the keyboard is not used, after a > > few minutes, it locks up and get

Re: buildworld: "cp: /dev/null: Invalid argument"

On Thu, 10 Sep 2020 10:35:08 -0400 Michael Butler wrote: > Is anyone else seeing failures like this in building world and, in my > case, cron jobs as well? > > > Building /usr/obj/usr/src/amd64.amd64/stand/i386/zfsboot/zfsboot.ldr > --- all_subdir_sbin --- > Building /usr/obj/usr/src/amd64.amd6

Re: time sysctl kstat.zfs.misc.dbufs | wc (was: OpenZFS and L2ARC)

On Thu, Sep 10, 2020, at 11:50 PM, Brandon Bergren wrote: > On Thu, Sep 10, 2020, at 11:17 PM, Graham Perrin wrote: > > On 09/09/2020 07:46, Stefan Esser wrote: > > > … an annoyance that I had noticed before but now have > > > tracked down: > > > > > > $ time sysctl kstat.zfs.misc.dbufs | wc > >

Re: time sysctl kstat.zfs.misc.dbufs | wc (was: OpenZFS and L2ARC)

On Thu, Sep 10, 2020, at 11:17 PM, Graham Perrin wrote: > On 09/09/2020 07:46, Stefan Esser wrote: > > … an annoyance that I had noticed before but now have > > tracked down: > > > > $ time sysctl kstat.zfs.misc.dbufs | wc > >    55327 2047031 16333472 > > > > real    0m16,446s > > user    0m0,055s

time sysctl kstat.zfs.misc.dbufs | wc (was: OpenZFS and L2ARC)

On 09/09/2020 07:46, Stefan Esser wrote: … an annoyance that I had noticed before but now have tracked down: $ time sysctl kstat.zfs.misc.dbufs | wc    55327 2047031 16333472 real    0m16,446s user    0m0,055s sys    0m16,397s … Here, I get much scrolling but no output from time: root@mom

Re: tracking -current, using poudriere-devel and the switch to git

On Thu, 10 Sep 2020 at 07:02, tech-lists wrote: > > On Wed, Sep 09, 2020 at 04:34:20PM -0400, Ed Maste wrote: > > [...lots of stuff explaining...] > > thank you Oh, I see I left a word out of my first reply and it could be confusing - added text in brackets below: > At the moment, is svn behind

Re: buildworld: "cp: /dev/null: Invalid argument"

On 9/10/20 12:17 PM, Ryan Stone wrote: > I'm curious: does this give a similar issue? > > touch /tmp/foo > cp /tmp/foo /tmo/foo2 > > I'm wondering if the issue is that copy_file_range isn't handling > empty files, or if it's a devfs issue. An empty file doesn't generate the error .. imb@vm01:/ho

Re: New FreeBSD snapshots available: main

clay@bsd13:~ $ uname -a FreeBSD bsd13 13.0-CURRENT FreeBSD 13.0-CURRENT #0 1544934ffb2-c253004(main): Thu Sep 10 06:18:34 UTC 2020 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 Works great, no problems with snapshot, thanks much Glen & everybody.

Re: buildworld: "cp: /dev/null: Invalid argument"

It seems that SVN r365549 broke "cp /dev/null ..."     imb On 9/10/20 10:35 AM, Michael Butler wrote: > Is anyone else seeing failures like this in building world and, in my > case, cron jobs as well? > > > Building /usr/obj/usr/src/amd64.amd64/stand/i386/zfsboot/zfsboot.ldr > --- all_subdir_sbin

buildworld: "cp: /dev/null: Invalid argument"

Is anyone else seeing failures like this in building world and, in my case, cron jobs as well? Building /usr/obj/usr/src/amd64.amd64/stand/i386/zfsboot/zfsboot.ldr --- all_subdir_sbin --- Building /usr/obj/usr/src/amd64.amd64/sbin/bsdlabel/bsdlabel --- all_subdir_stand --- --- zfsboot.ldr --- cp:

Re: `zfs list` permission denied

On Thu, Sep 10, 2020 at 12:46:45PM -0400, Ryan Moeller wrote: > > On 9/10/20 12:33 PM, Shawn Webb wrote: > > I used to be able to run `zfs list` as an unprivileged user. Now I > > can't, even when my user is in the operator group. > > > > BEGIN LOG > > hbsd-current-01[shawn]:/home/shawn

Re: New FreeBSD snapshots available: main (20200903 c122cf32f2a)

On Thu, Sep 10, 2020 at 06:43:08PM +0200, Emmanuel Vadot wrote: > On Thu, 10 Sep 2020 16:36:44 + > Glen Barber wrote: > > > On Thu, Sep 10, 2020 at 06:25:51PM +0200, Emmanuel Vadot wrote: > > > On Thu, 3 Sep 2020 16:00:51 + > > > Glen Barber wrote: > > > > > > > On Thu, Sep 03, 2020 at

Re: `zfs list` permission denied

On 9/10/20 12:33 PM, Shawn Webb wrote: I used to be able to run `zfs list` as an unprivileged user. Now I can't, even when my user is in the operator group. BEGIN LOG hbsd-current-01[shawn]:/home/shawn $ zfs list Operation not permitted hbsd-current-01[shawn]:/home/shawn (1) $ id uid

Re: buildworld: "cp: /dev/null: Invalid argument"

No, it's devfs. I'll fix it. On Thu, Sep 10, 2020 at 10:18 AM Ryan Stone wrote: > I'm curious: does this give a similar issue? > > touch /tmp/foo > cp /tmp/foo /tmo/foo2 > > I'm wondering if the issue is that copy_file_range isn't handling > empty files, or if it's a devfs issue. > > > On Thu,

Re: New FreeBSD snapshots available: main (20200903 c122cf32f2a)

On Thu, 10 Sep 2020 16:36:44 + Glen Barber wrote: > On Thu, Sep 10, 2020 at 06:25:51PM +0200, Emmanuel Vadot wrote: > > On Thu, 3 Sep 2020 16:00:51 + > > Glen Barber wrote: > > > > > On Thu, Sep 03, 2020 at 05:33:54PM +0200, Emmanuel Vadot wrote: > > > > > > > > Hello, > > > > > > >

Re: New FreeBSD snapshots available: main (20200903 c122cf32f2a)

On Thu, Sep 10, 2020 at 06:25:51PM +0200, Emmanuel Vadot wrote: > On Thu, 3 Sep 2020 16:00:51 + > Glen Barber wrote: > > > On Thu, Sep 03, 2020 at 05:33:54PM +0200, Emmanuel Vadot wrote: > > > > > > Hello, > > > > > > On Thu, 3 Sep 2020 15:02:45 + > > > Glen Barber wrote: > > > > > >

`zfs list` permission denied

I used to be able to run `zfs list` as an unprivileged user. Now I can't, even when my user is in the operator group. BEGIN LOG hbsd-current-01[shawn]:/home/shawn $ zfs list Operation not permitted hbsd-current-01[shawn]:/home/shawn (1) $ id uid=1001(shawn) gid=1001(shawn) groups=1001(sh

Re: New FreeBSD snapshots available: main (20200903 c122cf32f2a)

On Thu, 3 Sep 2020 16:00:51 + Glen Barber wrote: > On Thu, Sep 03, 2020 at 05:33:54PM +0200, Emmanuel Vadot wrote: > > > > Hello, > > > > On Thu, 3 Sep 2020 15:02:45 + > > Glen Barber wrote: > > > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA256 > > > > > > New FreeBSD deve

Re: buildworld: "cp: /dev/null: Invalid argument"

I'm curious: does this give a similar issue? touch /tmp/foo cp /tmp/foo /tmo/foo2 I'm wondering if the issue is that copy_file_range isn't handling empty files, or if it's a devfs issue. On Thu, Sep 10, 2020 at 11:45 AM Michael Butler wrote: > > It seems that SVN r365549 broke "cp /dev/null ..

Re: tracking -current, using poudriere-devel and the switch to git

On Wed, Sep 09, 2020 at 04:34:20PM -0400, Ed Maste wrote: [...lots of stuff explaining...] thank you -- J. signature.asc Description: PGP signature

Re: svn commit: r365419 - in head/sys/dev: ath bwi iwm iwn mwl otus usb/wlan wtap

On 9 Sep 2020, at 22:41, Tomoaki AOKI wrote: This breaks at least iwm. (Other drivers not tested.) Messages below are repeatedly shown and no carrier detected. Manually reverting this commit fixes the issue. iwm0: failed to send antennas before calibration: 35 iwm_run_init_ucode: failed 35 iwm

Re: Freeze during early boot

> On 10. Sep 2020, at 03:57, Mason Loring Bliss wrote: > > Hi, all. I'd like to see FreeBSD running on a new class of box I've got > here. Not new hardware. These are Atom chips on Micro-ITX motherboards, and > are interesting in that they are low-power and have dual gigabit NICs. > They're UEF

Re: OpenZFS and L2ARC

Am 09.09.20 um 21:26 schrieb John Baldwin:> A simple fix might be to use CTLFLAG_SKIP so that you only invoke the expensive sysctls if you request them by name, but not if you request the 'kstat.zfs' tree. I have looked at /sys/contrib/openzfs/module/zfs/dbuf.c where I had assumed that the "kst