01:01:09 ant-x: whats wrong with twm? 01:09:01 rtprio, it behaves wrong with pop-up menus of e.g. FireFox. When I press the sandwich button, a pop-up menu is shown, but it disappears as soon as I shift the mouse cursor, unless I keep holding the LMB down. 01:09:26 ^ This does not happen on Windows and I am sure is not meant to happen anywhere. 02:39:47 hello. i have an old laptop with intel ivybridge and HD4000 graphics. it was working well up until i updated to freebsd 15. now, it doesn't load i915kms on boot; i have to load it manually using kldload 02:42:00 i have kld_list="i915kms" in /etc/rc.conf, i also tried full path, kld_list="/boot/modules/i915kms.ko" (file does exist) and in both cases, i see a warning during boot that says: /etc/rc WARNING: can't load i915kms: No such file or directory 02:43:00 but then logging in and running sudo kldload i915kms does load it. any thoughts on why rc can't find the file? zfs filesystem if it matters... 02:44:22 i've been using the laptop since freebsd 11 and it was working fine until freebsd 14.3 and this issue only crept up after updating to freebsd 15...there weren't any obvious errors/failures during update to freebsd 15, followed the usual process as documented in handbook 02:46:27 using drm-kmod package 02:49:21 but you say `# kldload i915kms` works just fine 02:50:04 from cli, yes, it does 02:50:16 but not when rc tries to load it during boot 02:50:49 rc says file not found...even if i give it full path 02:51:05 you shouldn't have to give it a full path 02:51:24 right, it doesn't find it with or without 02:51:25 how did you upgrade to 15? freebsd-update? 02:51:28 yes 02:52:09 after booting, try running `service kld start` 02:52:42 we can try and diagnose that 02:53:00 ok 02:54:07 will disconnect to reboot, brb 02:56:47 ok, running 'service kld start' in cli loads it fine 02:58:06 and at boot there's no related errors? 02:58:30 during boot got that same error that it couldn't find file 02:58:48 i ran service kld start after boot in cli and that loaded it 02:59:04 should i run service kld enable or something so it runs during boot? 02:59:20 i need to step out to walk the dog, will be back in 20 min or so... 03:06:12 CorvetteZR1: it should always run 03:06:34 i don't know, sorry, maybe someone else knows 03:23:46 yea, this is weird...ok, i'll keep digging. thank you! 07:10:00 howdy 07:34:46 EHLO 07:38:32 anybody know if there is some issue with freebsd samba when using it to backup proxmox containers? 07:38:58 i keep getting error 70 bad address from proxmox and am not sure if that's fbsd samba or something 07:39:04 no issue AFAIK 07:39:24 i don't see these issues using nfs 07:39:34 NFS is better choice 07:39:37 i'm actually copying all my backups to another dataset that i'm exporting with nfs 07:39:53 just because of this weird bad address thing with samba 07:39:56 add certs for auth and you will be lucky 07:39:59 it's so random 07:40:48 it's to a local nas so i'm not too concerned about certs so much as i'm at a loss with this bad address thing from samba heh 07:41:28 INFO: zstd: error 70 : Write error : cannot write block : Bad address 07:41:50 i'm not sure if that is telling me it's a bad network address or bad block address 07:42:38 like maybe the zfs backend on the fbsd side is messing with how it's supposed to write to zfs? 07:43:47 NFS is perfect choice for FreeBSD, it's completely fine to share ZFS over NFS 07:44:37 i'm sure .. but i'd still like to sort out why the error is happenign with smb 07:44:41 *happening 07:45:15 are you piping samba through zstd ? 07:46:03 no. proxmox is piping tar to zstd to backup to smb 07:46:32 OK, so proxmox have problems with samba 07:46:58 yes. but i'm not sure which side is having the issue here. i'm guessing it's the proxmox side. i don't see these sorts of issues elsewhere 07:47:18 try NFS then, use nfsv4 and delegate the whole share to the client 07:47:32 but again. i don't know if it's telling me the bad address is a network hangup (which i'm not seeing at all) or if it's because when it tries to write to the fbsd samba share it's not writing correctly 07:47:42 yeah i already did that 07:47:54 Macer: you have to troubleshoot it 07:48:02 i'm moving the backups to a new dataset that i'm exporting with nfs.. but again... i'd like to sort out where the issue is with smb :) 07:48:22 because i've seen this on more than one proxmox server connecting to more than one fbsd server 07:48:24 sniff on the inrerfaces, take a deeper look what is going on filesystems etc 07:48:34 or better, workaround it by changing to NFS 07:48:38 yeah. i've been trying to find it.. it's very random 07:48:57 that's what i'm doing for now. moving it to nfs 07:49:04 just to make sure the backups work 07:49:08 good choice 07:49:36 but i'd still... like to find out what is going on with samba and determine if it is a proxmox problem, fbsd samba problem, freebsd zfs problem, or something else 07:50:12 i've been quadruple checking settings all over and monitoring logs on both sides to sort out where / why it's happening and so far the only thing i can see is the bad address error from proxmox 07:50:20 i don't see nic hangups etc 07:50:30 maybe i'll monitor the fbsd debug log 07:50:33 go ahead, troubleshoot it, increase debugging in samba and dive into the problem 07:51:03 but if you want reliable solution, use NFS 07:51:07 i'm wondering if maybe mount.cifs on the proxmox side is too aggressive on minor hangups lol 07:52:12 you can tune samba server, you can make mount.cifs less agressive 07:53:50 /192.168.1.13/proxmox on /mnt/pve/devil type cifs (rw,relatime,vers=3.1.1,cache=strict,upcall_target=app,username=backup,domain=DOMAIN.ORG,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.13,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,reparse=nfs,nativesocket,symlink=native,rsize=4194304,wsize=4194304,bsize=1048576,retrans=1,echo_interval=60,actimeo=1,closetimeo=1) 07:54:18 wow proxmox does a lot just to mount cifs 07:55:06 i'm looking at reparse=nfs and retrans=1 07:56:25 i'm wondering if zfs is losing the block during the backup from another write process 08:07:39 Macer: what is happening, you're backing up from proxmox to freebsd 08:07:40 ? 08:37:05 Hi 08:37:37 since my upgrade to FreeBSD 15.0, my host regularly breaks with jail: nginx: getpwnam: Too many open files in system 08:37:50 i was thinking that bastille is the problem or a jail, but the whole system is affected 08:37:55 a reboot solve it 08:38:02 i just notice something strange 08:38:10 https://0x0.st/P-aj.txt 08:38:21 on Linux, syncthing only eats 63 FDs 08:39:25 i'm out of what i understand, so i asked chatgpt which tells me that freebsd kernel design is different and uses kqueue instead of inotify. kqueue needs one FD per watched file 08:39:31 is that true ? 08:41:17 i will wait for it to break again to verify the number of FDs 08:41:39 my question is : setting higher kern.maxfilesperproc is a workaround or a fix ? 08:52:28 rtprio: yes. from proxmox using smb to fbsd using samba 08:53:38 INFO: zstd: error 70 : Write error : cannot write block : Bad address 08:53:44 and this happens randomly 08:54:45 *fbsd using samba and zfs 09:02:45 eoli3n: inotify is 15.0, it is one of the new features https://man.freebsd.org/cgi/man.cgi?inotify(2) 09:05:06 mzar: hm, let's check if the dev knows it 09:05:30 https://github.com/syncthing/syncthing/issues/10464 09:05:30 eoli3n: Too many open files in system <- kern.maxfiles can be set only at boottime 09:05:32 nice 09:06:00 ok, so it's a proper fix before syncthing move to inotify ? 09:06:05 to increase it, i mean 09:06:49 I don't know, I am not using syncthing, but kern.maxfiles can be set from loader.conf, it's lodader tunable 09:08:05 https://github.com/syncthing/syncthing/issues/9183 09:11:44 eoli3n: you can try to patch the code, beging with allowing to build this part on FreeBSD https://github.com/fsnotify/fsnotify/blob/main/backend_inotify_test.go 09:12:08 i will let this to anybody more competent than me :) 09:12:16 but thanks for the flag 09:12:31 oh.. it's test, not right file 09:13:01 https://github.com/fsnotify/fsnotify/blob/main/backend_inotify.go 09:13:07 this one 09:13:30 eoli3n: you can learn by fixint it 09:13:56 yes i could, but i miss time for now 09:15:41 mzar: how do you propose 'fixing' the module that is specifically Linux only? 09:16:32 to fix* 09:17:03 considering fsnotify has backend_kqueue that is specifically Free/NetBSD + Mac OS only 09:56:06 Remilia: I'd begin by adding FreeBSD to the build 10:03:02 when making BE how do i include my pkg repository ( built by poudriere ) as well /usr/ports tree? would bectl create -r work? it is that /usr is not incuded in BE due to canmount=off for /usr 10:48:31 mzar: I'm sorry, what? 11:15:57 Remilia: mzars suggestion was to use inotify on FreeBSD instead of kqueue, not that that inotify backend is somehow broken 11:23:29 nimaje: I thought inotify is Linux only? 11:23:41 or is it like, via the emulator 11:32:57 read the man page mzar linked above, FreeBSD 15 has inotify and with it you can monitor a directory without needing an fd for every object in the directory (no idea why kqueue didn't get some handle for that use case or maybe it did and I just missed it) 11:33:55 oh 11:39:53 if the suggestion was instead to make it build on FreeBSD using devel/libinotify then it would have been useless, as devel/libinotify is just a wrapper around kqueue to have a inotify API to make porting easier, but it would have the same problem of needing many fds to monitor directories 13:17:17 dch: is oracle free tier now better with subscription? and are there more up-to-date guide for setting up freebsd image 15:30:47 angry_vincent: I recommend people to subscribe & upgrade to credit card, but then stay below the $$ monthly usage limit 15:31:08 setting up freebsd should be super easy, just choose the 15.0-RELEASE UFS or ZFS image from the web ui 15:31:17 if you're using command line I have tools to help 15:38:15 I think Installer is broken in 15.0-RELEASE 15:38:34 i just dd'ed the freebsd image over the oracle one from linux and restarted 15:57:38 checkpoint: what's wrong with it? 16:03:03 Remilia: recently I was trying to install 15.0 on Horizon N5 mini-PC, it could not connnect to network - neither wifi nor ethernet could connect and/or obtain IP from local DHCP server. 16:04:14 Remilia: same time 14.3-RELEASE worked like a charm on same mini-PC. 16:05:08 curiouser and curiouser 17:45:24 Has anyone noticed significant degradation in system responsiveness under heavy disk IO under 15-RELEASE? I'm noticing this in two wildly different systems: an Oracle Cloud arm64 instance using zfs, and a VM on Linux KVM using UFS. When disks start to saturate, ssh responsiveness suffers greatly. 17:46:26 This is utterly subjective, but more than on 14. 17:49:40 (KVM vm is amd64) 17:57:53 amigan: do you have ZFS? 17:57:58 oh 17:58:16 amigan: check `top -SH` and see if you have arc_prune at 100% 17:58:50 it's what completely devastates my server under tons of MediaWiki request 17:58:56 s 19:55:24 Remilia: nope on the ZFS VM. Most CPU is idle tasks, which makes no sense why it's such a dog