Re: Possible issue with linux xattr support?

2023-08-30 Thread Felix Palmen
* Dmitry Chagin [20230830 11:57]: > On Tue, Aug 29, 2023 at 08:58:13PM +0200, Felix Palmen wrote: > > Thanks again for quickly fixing this! Can this still make 14.0-RELEASE? > > > I think yes, thanks for testing, I revised the error handling and made > it more precise, c

Re: Possible issue with linux xattr support?

2023-08-30 Thread Dmitry Chagin
On Wed, Aug 30, 2023 at 12:33:23PM +0200, Felix Palmen wrote: > * Felix Palmen [20230830 12:01]: > > Unfortunately, install from GNU coreutils is now unable to install > > anything again. I tried both as 'nobody' and as 'root', it doesn't make > > a difference: &

Re: Possible issue with linux xattr support?

2023-08-30 Thread Felix Palmen
* Felix Palmen [20230830 12:58]: > * Dmitry Chagin [20230830 13:48]: > > I don't changed setxattr syscalls due to EPERM is a valid error from it, > > however here's the essential difference between Linux and FreeBSD. > > FreeBSD does not permits manipulatingg attribu

Re: Possible issue with linux xattr support?

2023-08-30 Thread Dmitry Chagin
On Wed, Aug 30, 2023 at 11:20:39AM +0200, Felix Palmen wrote: > * Dmitry Chagin [20230830 11:57]: > > On Tue, Aug 29, 2023 at 08:58:13PM +0200, Felix Palmen wrote: > > > Thanks again for quickly fixing this! Can this still make 14.0-RELEASE? > > > > > I think y

Re: Possible issue with linux xattr support?

2023-08-30 Thread Dmitry Chagin
On Wed, Aug 30, 2023 at 12:58:45PM +0200, Felix Palmen wrote: > * Dmitry Chagin [20230830 13:48]: > > On Wed, Aug 30, 2023 at 12:01:13PM +0200, Felix Palmen wrote: > > > Unfortunately, install from GNU coreutils is now unable to install > > > anything again. I tried bo

Re: Possible issue with linux xattr support?

2023-08-30 Thread Dmitry Chagin
On Wed, Aug 30, 2023 at 12:01:13PM +0200, Felix Palmen wrote: > * Dmitry Chagin [20230830 12:22]: > > On Wed, Aug 30, 2023 at 11:20:39AM +0200, Felix Palmen wrote: > > > * Unprivileged user will get ENOTSUP when trying to access the system > > > namespace (regardl

Re: Possible issue with linux xattr support?

2023-08-30 Thread Felix Palmen
* Felix Palmen [20230830 12:01]: > * Dmitry Chagin [20230830 12:22]: > > On Wed, Aug 30, 2023 at 11:20:39AM +0200, Felix Palmen wrote: > > > * Unprivileged user will get ENOTSUP when trying to access the system > > > namespace (regardless of the new jail sett

Re: Possible issue with linux xattr support?

2023-08-30 Thread Dmitry Chagin
On Tue, Aug 29, 2023 at 08:58:13PM +0200, Felix Palmen wrote: > * Dmitry Chagin [20230829 21:12]: > > On Tue, Aug 29, 2023 at 07:02:22PM +0200, Felix Palmen wrote: > > > So, using user.* works, using system.* doesn't, and maybe a bit > > > surprising(?), dumping all attributes which by default

Re: Possible issue with linux xattr support?

2023-08-30 Thread Felix Palmen
* Dmitry Chagin [20230830 12:22]: > On Wed, Aug 30, 2023 at 11:20:39AM +0200, Felix Palmen wrote: > > * Unprivileged user will get ENOTSUP when trying to access the system > > namespace (regardless of the new jail setting), so GNU tools like e.g. > > coreutils inst

Re: Possible issue with linux xattr support?

2023-08-30 Thread Felix Palmen
* Felix Palmen [20230830 12:01]: > Unfortunately, install from GNU coreutils is now unable to install > anything again. I tried both as 'nobody' and as 'root', it doesn't make > a difference: > [...] > I assume the fsetxattr call needs some adjustment of error codes as well >

Re: Possible issue with linux xattr support?

2023-08-30 Thread Felix Palmen
* Dmitry Chagin [20230830 13:48]: > On Wed, Aug 30, 2023 at 12:01:13PM +0200, Felix Palmen wrote: > > Unfortunately, install from GNU coreutils is now unable to install > > anything again. I tried both as 'nobody' and as 'root', it doesn't make > > a difference: &

Re: net/mpd5 on stable/14 - COMPAT_FREEBSD12 required?

2023-08-30 Thread Herbert J. Skuhra
On Wed, 30 Aug 2023 15:29:28 +0200, "Herbert J. Skuhra" wrote: > > Hi, > > after updating from stable/13 to (main and later to) stable/14 > net/mpd5 only connects to my ISP (VDSL with VLAN) if I enable "options > COMPAT_FREEBSD12" in my kernel. Without I get only: > > Aug 30 15:08:06 gw

Re: ZFS Page Derefrence

2023-08-30 Thread Mark Johnston
On Tue, Aug 29, 2023 at 07:08:35PM -0700, Cy Schubert wrote: > Hi > > Just got the following panic on an and64 machine running poudriere building > i386 packages. > > panic: vm_page_dequeue_deferred: page 0xfe000b222808 has unexpected > queue state^M > [...] > > uname reports, > >

net/mpd5 on stable/14 - COMPAT_FREEBSD12 required?

2023-08-30 Thread Herbert J. Skuhra
Hi, after updating from stable/13 to (main and later to) stable/14 net/mpd5 only connects to my ISP (VDSL with VLAN) if I enable "options COMPAT_FREEBSD12" in my kernel. Without I get only: Aug 30 15:08:06 gw mpd[59876]: [L1] PPPoE connection timeout after 9 seconds Aug 30 15:08:06 gw

Another ZFS Panic -- buffer modified while frozen

2023-08-30 Thread Cy Schubert
A different panic on a different amd64 machine also running poudriere but building amd64 packages. Exmh was just started, displaying back to my laptop at the time of panic. panic: buffer modified while frozen! cpuid = 1 time = 1693417762 KDB: stack backtrace: db_trace_self_wrapper() at

Re: ZFS Page Derefrence

2023-08-30 Thread Cy Schubert
In message , Mark Johnston writes: > On Tue, Aug 29, 2023 at 07:08:35PM -0700, Cy Schubert wrote: > > Hi > > > > Just got the following panic on an and64 machine running poudriere building > > > i386 packages. > > > > panic: vm_page_dequeue_deferred: page 0xfe000b222808 has unexpected > >

Re: 100% CPU time for sysctl command, not killable

2023-08-30 Thread Alexander Leidinger
Am 2023-08-20 21:23, schrieb Alexander Leidinger: Am 2023-08-20 18:55, schrieb Mina Galić: procstat(1) kstack could be helpful here. Original Message On 20 Aug 2023, 17:29, Alexander Leidinger alexan...@leidinger.net> wrote: Hi, sysctl kern.maxvnodes=1048576000 results in

Re: Possible issue with linux xattr support?

2023-08-30 Thread Shawn Webb
On Wed, Aug 30, 2023 at 06:55:14AM +0200, Alexander Leidinger wrote: > Am 2023-08-29 21:02, schrieb Shawn Webb: > > > Back in 2019, I had a similar issue: I needed access to be able to > > read/write to the system extended attribute namespace from within a > > jailed context. I wrote a rather

sscanf change prevents build of CURRENT

2023-08-30 Thread John F Carr
I had a problem yesterday and today rebuilding a -CURRENT system from source: --- magic.mgc --- ./mkmagic magic magic, 4979: Warning: Current entry does not yet have a description for adding a MIME type mkmagic: could not find any valid magic files! The cause was an sscanf call

Re: Possible regression in main causing poor performance

2023-08-30 Thread Glen Barber
On Mon, Aug 28, 2023 at 06:06:09PM -0700, Mark Millard wrote: > Has any more been learned about this? Is it still an issue? > I rebooted the machine before the ALPHA3 builds with no other changes, and the overall times for 14.x builds went back to normal. I do not like to experiment with

Re: sscanf change prevents build of CURRENT

2023-08-30 Thread Dag-Erling Smørgrav
"John F Carr" writes: > I had a problem yesterday and today rebuilding a -CURRENT system from > source: [...] The cause was an sscanf call unexpectedly failing to > parse the input. This caused the mkmagic program (internal tool used > to build magic number table for file) to fail. This was

Re: Possible issue with linux xattr support?

2023-08-30 Thread Dmitry Chagin
On Tue, Aug 29, 2023 at 02:07:11PM -0500, Kyle Evans wrote: > On 8/29/23 14:02, Shawn Webb wrote: > > On Tue, Aug 29, 2023 at 05:45:51PM +0300, Dmitry Chagin wrote: > > > On Tue, Aug 29, 2023 at 12:59:11PM +0200, Felix Palmen wrote: > > > > * Dmitry Chagin [20230828 18:57]: > > > > > On Mon, Aug

Re: Possible regression in main causing poor performance

2023-08-30 Thread Cy Schubert
In message <20230830184426.gm1...@freebsd.org>, Glen Barber writes: > > > On Mon, Aug 28, 2023 at 06:06:09PM -0700, Mark Millard wrote: > > Has any more been learned about this? Is it still an issue? > >=20 > > I rebooted the machine before the ALPHA3 builds with no other changes, > and the

Re: user problems when upgrading to v15

2023-08-30 Thread Graham Perrin
On 31/08/2023 03:31, brian whalen wrote: Understood. I guess I was expecting the update process of etcupdate -p && make installworld && etcupdate -B to not whack existing users or delete an existing root user's password. I accepted the remote and then recreated users and reset passwords and

Re: user problems when upgrading to v15

2023-08-30 Thread Graham Perrin
On 31/08/2023 03:00, brian whalen wrote: … I ran etcupdate resolve accepting the remote option and saw 2 issues. The root user's password was deleted. The non root user no longer existed. Logically, remote does not include things such as your root user's password.

Re: user problems when upgrading to v15

2023-08-30 Thread brian whalen
Understood. I guess I was expecting the update process of etcupdate -p && make installworld && etcupdate -B to not whack existing users or delete an existing root user's password. I accepted the remote and then recreated users and reset passwords and am retrying this. BW On 8/30/2023 7:21

pkg problems with v15

2023-08-30 Thread brian whalen
root@f15:~ # pkg update pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended Updating FreeBSD repository catalogue... pkg: http://pkgmir.geo.freebsd.org/FreeBSD:15:amd64/quarterly/meta.txz: Not Found repository FreeBSD has no meta file, using default

Re: user problems when upgrading to v15

2023-08-30 Thread brian whalen
I have seen this twice. Once when going from 13.2 to current 14.0 alpha1 and then to 15, and a 2nd time when going from 13.2 to 15. I have a user that is a member of the wheel group. After I upgraded and ran the post reboot commands in single user mode I was alerted to merge conflicts. I ran

Re: pkg problems with v15

2023-08-30 Thread Graham Perrin
On 31/08/2023 02:59, brian whalen wrote: … pkg: http://pkgmir.geo.freebsd.org/FreeBSD:15:amd64/quarterly/meta.txz: Not Found … For 15.0-CURRENT you should use latest; don't expect quarterly. Also, it's probably too soon for latest. 1. 2.