00:02:24 thorongil, It sounds like your array is failing beyond the redundancy available and has therefore degraded to failed. Your OS was running and so continues to run. 00:02:56 It's not like you have many options but upon reboot you might need to be resigned to finding that you have lost the array if you can't get disks back online. 00:03:44 Meanwhile... I have a Seagate here that glitches out every so often, requires a power cycle, then is okay for a day, week, month, then it glitches again. So maybe... 00:06:31 Also just a reminder that if you do get the array back online but zroot/ROOT/default is corrupted remember that Boot Environments at boot are available. 00:06:37 I successfully recovered a problem on one of my very recently by booting back to an older BE at boot time. 00:19:26 Anyone on 13.1 without virtualbox-ose-kmod installed able to pastebin `pkg install -n emulators/virtualbox-ose-kmod` output? 00:25:32 got my usb microphone 00:25:42 pcm3: (rec) 00:25:44 :P 00:27:07 thanks jmnbtslsQE & rwp. i am definitely resigned to losing the current drive contents---fortunately, they are super easy to recreate. (it's a one-drive pool, fwiw) 00:30:15 How do i use my usb microphone ? shows up in /dev/sndstat 00:30:36 hw.snd.default_unit=1 < -- speakers with pcm1 00:32:00 if/when i go through the reinstall process, is there any reason to choose BIOS vs EFI? 00:32:47 Everything made in the last decade or more supports UEFI, and it'll be the best-tested configuration. 00:34:51 i guess i figured if there wasn't a compelling use-case for UEFI over BIOS that many people would still be using the BIOS option and so it would remain pretty well-tested even so 00:35:44 skered, pkg install -n emulators/virtualbox-ose-kmod on my system. Anticlimatic. https://bsd.to/5t5O/raw 00:35:45 Title: 5t5O 00:40:03 thorongil: Legacy boot is still the most common for VMs. 00:40:07 rwp: Any chance mpfr and/or sccache-overlay installed? 00:40:13 thorongil, The one thing I hint is GPT partition types FTW for sure. 00:40:44 Mm. GPT labels are great. But you can use GPT with either Legacy or UEFI. 00:41:38 skered, pkg info output https://bsd.to/9RvC/raw 00:41:39 Title: 9RvC 00:42:01 hmm. do GPT labels really do much for me if all my disks are given over to ZFS pools? 00:42:30 rwp: If you run `pkg autoremove -n` does that try to remove anything? 00:42:51 (I swear I'm not trying to be contrarian, just trying to understand) 00:43:17 skered, pkg autoremove -n, yes just two things https://bsd.to/qVGH/raw 00:43:18 Title: qVGH 00:43:41 rwp: Ok thanks 00:44:28 skered, Perhaps "pkg info -d emulators/virtualbox-ose-kmod" is what you are looking for? 00:46:11 rwp: It should be nothing. 00:47:51 thorongil: Yes, you want your ZFS to live inside partitions, and GPT is a great way to label those. 00:53:18 I think its working, i had to chagne the settings in audacity and its reocrding. wonder why it dosen't work in chromium 01:04:35 mason: I don't want to allocate the entire disk to zfs? or are you suggesting that i create a single GPT partition that comprises the whole disk and point ZFS at it? if so, what does GPT buy me in that case? 01:06:19 in freebsd you want the pool to be inside a partition of time freebsd-zfs, but it can be the only partition if you want 01:06:26 of type 01:06:49 thorongil: A single partition would be better. More controllable if you have to add a new disk into the mix in future, for instance. 01:07:04 thorongil: Example, your single-disk pool becomes a mirror, but your second disk is bigger. 01:07:33 Or let's say you need to migrate to another similarly-sized-but-not-quite-the-same disk. 01:08:07 I had this as a surprise today for instance. I'm migrating my mirror to SSDs, and lo and behold, the 1TB SSDs are 20G bigger than my 1TB spinning rust. 01:08:18 But since I use partitions, this didn't matter. 01:08:56 I guess it's personal preference, but partitions are nicely hygienic. 01:09:24 works dosen't work, hmm 01:26:58 Works in chromium 02:03:27 mason: interesting, thanks! can you say a bit more (or point me to something I can read) about how a partition makes the zfs pool more controllable and/or how using partitions made it easier to transition your mirrored pool to different drives? 02:04:56 Why don't i have a root parition in fstab ? 02:05:21 using zroot i think the defualts from the installer 02:07:05 zfs filesystems aren't mounted via fstab 02:08:37 thorongil: one element is that a mirror needs the providers to have the exact same size and sometimes physical drives have slightly different sizes 02:09:17 i also think that using the entire disk can interfere with freebsd's recognition of the disk, but i don't know the details about that. i do remember having some issues orannoyances when i tried it 02:09:50 i think there are platforms where using the entire disk is recommended instead of a partition, but on freebsd it is the inverse 02:10:38 you will also not be able to use labels or do anything else with gpt if you use an entire disk for zfs instead of a partition 02:11:58 thorongil: Just saw that. https://wiki.freebsd.org/RootOnZFS 02:11:59 Title: RootOnZFS - FreeBSD Wiki 02:12:43 i'm still confused. if the partition takes up the whole disk, i don't see how that saves me from the requirement that both disks (partitions) be the same size in a mirror. 02:13:05 i do see the need for that requirement, just not how partitions alleviates the pain of it 02:14:30 if the new disk in the mirror is larger, than the original, then the new one will need to be on a partition of specified size (size of the original) 02:15:28 if the original is a specified size in GB, then sometimes there will be a few MB or KB at the end left, which i guess helps in the case that the size of a new disk is slightly different 02:16:01 for me, the real benefit is being able to use labels properly 02:16:51 i thought, in that case, zfs makes available space equal to the minimum of the two drives and that, if the smaller drive is replaced, it magically increase the available size to equal the minimum of the new array 02:16:53 for example it means i can replace an old drive with a new drive that has the same label 02:17:31 well, i was referging to the case where you had a mirror later on 02:18:12 so you have N drives in your mirror (possibly N=1), then add N+1 th drive that is slightly larger...that larger drive will surely need a partition to match the size of the current mirror volumes 02:18:25 in my experience, that is not the case 02:18:39 zfs just doesn't use the space that exceeds the size of the smallest drive 02:19:00 but if the smallest drive dies and gets replaced with a larger drive, the *new* smallest drive now determines the usable space 02:19:07 this seems like an argument to NOT use partitions tbh 02:25:48 thorongil: you are correct, i just tested it. i think the issue would arise when the new mirror disk is smaller than the existing ones, not larger 02:26:14 not during replacement, but when adding a device to the mirror 02:26:40 what do you do in that case, then? can you resize the zpool to accommodate the new, smaller mirror drive? i haven't heard of that feature. 02:27:03 as far as i know, it cannot be resized like that 02:28:00 if the physical disks are specified to be the same size, then surely the difference is very small, possibly in bytes, so if your mirror disks partition leaves a few MB or KB at the end, it is safe to add the new smaller disk 02:29:18 in the case where the new mirror disk is smaller than the existing ones, would zfs even allow you to add it to the pool? i would have assumed not. 02:29:32 right, you cannot add it 02:30:35 so the idea is that your original mirror partitions are slightly smaller than entire disk ; and so the new mirror disk is not too small 02:31:20 ah, okay. so you plan ahead and create 990G partitions on your 1T drives, so that you can later replace with other drives that claim to be 1T but might be a little less. 02:31:31 that makes sense! 02:32:01 i specify their sizes in GB, and often there are several KB left over 02:32:36 but i'm just an ordinary user with a relatively insignificnat infrastructure 02:33:13 most of my drives are physical 3TB drives, and looking at them, i do see that several have a few KB left over, but several do not 02:33:46 for me it really is about being able to abstracting from the physical identity of the drive using labels 02:34:02 gotcha, thanks 02:34:09 this has been an interesting discussion 02:35:13 i haven't heard of the behvavior you mentioned about the mirror zpool size changing to match the smallest drive when the old smallest is replaced, it sounds suspicious but i agree it would be a good way to be flexible and be able to increase the size of your pool 02:36:42 i have heard of that behavior in the context of RAIDZ. i sort of assumed it held for mirrors, as well, but i don't know for sure. 02:36:54 actually, i've tested that behavior on RAIDZ pools myself 02:37:33 i see 02:38:29 that sounds even more suspicious, but i only know enough about zfs to keep my systems running, along with whatever i have learned in times of crisis 02:42:17 i was not able to reproduce that behavior for raidz in a test with memory disks 02:45:09 interesting 02:45:59 however, i'm on 12.3, so maybe it's different on the zfs that's been used since 13 02:46:42 the feature i'm thinking of predates the inclusion of ZFS in FreeBSD 02:47:00 OK 03:02:49 anyone using gnome and have the extenstion app installed? if so how did you do it? 03:52:51 No updates needed to update system to 13.1-RELEASE-p2 03:52:57 -p2 ? 04:15:04 jb1277976: what 'extension app' ? 04:22:38 rtprio: Like dash to dock and stuff for gnome 07:34:52 my workstation just stopped reaching the kde desktop 07:35:49 sddm login is ok then i get the kde gears but then just a black screen with mouse cursor 07:36:17 windows boots ok 07:37:13 fedora recently broke their nvidia 390 drivers so that doesn't boot to kde atm 07:38:26 freebsd 13.1 on an oldish hp z400 xeon workstatiion 07:51:57 doesn't seem to be crashing just either hanging or extremely slow 08:18:04 something had wriiten some crap in ~/.config possible kmail that I started accidentally yesterday 08:23:02 still extremely slow 08:24:09 maybe, create another user and log in with it 08:24:38 such way you can isolate whether something to do plasma/usr configs 08:28:09 I tried renaming .config to .config.bak 08:28:36 ok, also possible. 08:29:10 sddm is such a finicky thing 08:30:07 sddm seems OK it looks like Xorg or plasma has become glacially slow 09:07:53 after getting back to desktop 'baloo_file' was killing perfromance 09:10:27 .oO( Of course! ) 09:12:55 OK restored my .config and turned off baloo seem to be back to normal 09:16:54 The issue as I understand is that baloo is used to index files; it uses kqueue|kevent, on FreeBSD, for notification of changes; which results in all the files of interest being kept open; that causes slow down. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230726 & https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256269 09:16:57 Title: 230726 – sysutils/kf5-baloo: OS performance suffers – sometimes, as if frozen – when reaching the virtual memory vnode limit 09:20:18 One could create a baloo configuration file to index only certain files (how or what format? I do not know). See https://twitter.com/probonopd/status/1583724940867825666 & https://github.com/helloSystem/hello/issues/33 09:20:19 Title: probono on Twitter: "Is anyone using @kdecommunity's baloo full text indexing on #FreeBSD? Does this need to be configured in special ways in order not to open too many files? https://t.co/fPW8dTaPSC" / Twitter 09:20:40 I never use it so I'll leave it off 09:21:38 Works 16:00:08 Guys it's mixer1 mixer2 dsp1 dsp2 all represent pcm1 pcm2 ? 16:02:02 jb1277976: I don't understand your question 16:03:16 You can get a list of audio devices with "cat /dev/sndstat" and get more info out of it after "hw.snd.verbose=1" 16:03:36 You can also use 2 for verbosity, but it might be too much 16:14:38 meka: Sorry. Does mixer0 and mixer1 represent pcm0 and pcm1 ? 16:18:17 they usually do, but I didn't read the code to claim it can not be different 16:23:25 Hi everyone, for some reason I've been getting this message while trying to install a package to a jail https://bsd.to/RjAt 16:23:27 Title: dpaste/RjAt (Plain Text) 16:23:47 If I understan correctly, my kernel is behind the package? 16:26:25 monkey_: what does `freebsd-version -ku` say? 16:26:38 probably 13.0 right? 16:27:16 On the host it prints 13.1-RELEASE-p2 twice 16:27:43 I was thinking that maybe I had 13.0, but that's not the case, and the jails is a fresh install 16:27:54 13.0 install? 16:28:05 the cvs-jail, that is 16:31:04 Originally it was a 13.0 install, but I upgrade my system to 13.1 a while ago 16:31:49 hmmm you sure the jail's upgraded too? 16:32:35 Right know I'm working on a new install 16:32:57 I just did a bsdinstall jail /path/to/jail 16:33:46 have a look at freebsd-upgrade'ing the jail then 16:34:03 something somewhere is b0rked ;) 16:37:13 Looks like there is a 13.1-RELEASE-p2 how do i see what is in the -p2? i googled it but nothing really came up. is it on the freebsd main website? 16:39:08 have a look at the security advisories/errata notices 16:45:17 xmj: I remember that I did the upgrade for the jail before, anyway it's working now 16:45:23 Thanks, appreciate your help 16:58:42 first upgrade attempt and i got an error https://termbin.com/ly8m don't know what it means 16:58:59 i just did a git -C /usr/ports/ pull so i think i have the latest 17:00:07 do i install those packages then try again? 17:11:12 probably a dumb question, but you are all called bsd, but you do have different kernels, right? you just kept the name. 17:33:13 monkey_, I know you said it is solved but for the future I think there was a missing -r in freebsd-version -kru which also then lists the running kernel too. For those who have not rebooted since the kernel upgrade. 17:33:49 In a perfect world all three of those emit the same version strings. If not, then it's a clue. 17:34:35 And freebsd-version is -j jail aware too. 17:39:07 rwp: the three lines have the same version 17:39:50 However I did reboot the computer 18:00:19 Sometimes, a -p only affects userland and not the kernel. Then, you can have different values. For instance, 12.3 is currently -p6/-p6/-p7. 18:09:48 V_PauAmma_V: so I don't need to do anything or worry right? 18:16:16 Look like amd64 is tier 1 18:58:08 lavaball: yes every *BSD is a different kernel. Many UNIX systems called their kernels unix too despite being often wildly different 18:58:09 jb1277976, based on your pastebin, I don't think you do. 19:01:09 vortexx, thanks for explaining. 19:04:08 lavaball: you're welcome 19:13:26 Hi guys, I need a little help... I'm using csh shell. The command history is saved at ~/.history. I want to prevent a user from deleting or modifying this file. I tried "chflags uappend", but FreeBSD cannot append history into this file, and ends up creating another .history_whatever file. 19:22:34 Just pre-ordered a VisionFive2. Hopefully freeBSD will run on it :) 19:25:28 While money can't buy happiness, it certainly 19:25:28 lets you choose your own form of misery. 19:25:35 fortune++ 19:32:47 devnull, Do you really need this feature? It is easy to defeat. But if so then maybe (I have not tried it) you could set up .history as a pipe with a reader that records the information elsewhere. Seems like trouble to me though. 19:41:11 does FreeBSD have, by default, the kind of stack protection that caused OpenSSL to downgrade the severity of the current bugs? https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows/ 19:41:12 Title: CVE-2022-3786 and CVE-2022-3602: X.509 Email Address Buffer Overflows - OpenSSL Blog 20:32:42 hey guys, maybe someone can assist me. I can't seem to get a jail to ping anything apart from it's host. vnet config 20:35:07 https://dpaste.org/ONZfG 20:35:35 seems that I can ping the host from the jail, and ping the jail from the host, but cannot ping the router from the jail 20:35:44 raw sockets enabled, etc etc 20:36:02 Hmm i'm getting an error when running virtualbox Unable to allocate and lock memory. The virtual machine will be paused. Please close applications to free up memory or close the VM. I ran https://dpaste.org/V6D8b im allocating 4096GB what could be wrong? i ran a vm with 4 gigs on current and it worked fine. currently on 13.1-RELEASE 20:46:14 devnull: csh probably writes a new file and then renames it to .history to avoid partially written files and if it does only keep a limited number of history avoid accidentally removing it as it has to override the whole file when removing stuff at the start 20:57:17 codersmoke: you need to make the bridge interface of the host the network interface of the jail for it to work without nat via firewall stuff 20:57:34 nimaje, It makes sense. This explains why "uappend" didn't work and the system just created the . history_whatever as it failed to rename. 20:57:55 interesting 21:12:16 nimaje thats it. Using bash shell, it worked. uappend worked in .bash_history. 21:24:09 hi all 21:47:55 @vortexx, can you explain that like i'm a 5 year old? 22:14:49 morning 22:48:07 .oO( Hmm EN-22:2[16] found their way to my email account but have not seen yet EN-22:24.zfs for 13.1; all: https://www.freebsd.org/security/notices/ ) 22:48:09 Title: FreeBSD Errata Notices | The FreeBSD Project 23:00:21 I have just upgraded my box to 13.1-RELEASE-p3, now I have no hardware acceleration on my Intel GPU! 23:00:32 hm, could EN-22:27 have been my problem with trying to update from 12.x -> 13.1? till the loader all was fine but after that it was just a blackscreen, I didn't have any idea how to debug that, so I ignored it after installing 13.1 was working fine (I only had 21 and 22 in my mail inbox, but in my feed reader I have all 7) 23:00:52 Opening xterm glides really slow over the monitor. It's horrible. 23:01:44 iio7: what was the prior version? 23:02:12 iio7: /var/run/dmesg.boot output as pastebin (bsd.to) 23:02:42 koobs, prior version was 13.1-RELEASE-p2 23:03:02 do you use drm-kmod for intel driver? 23:03:16 nimaje, That is what I am fearing if I would update from 13.0 (or, I would rather not reinstall from scratch) 23:03:40 Oh there is a p3 now? 23:03:47 Yes 23:03:48 Only checked last night 23:04:22 Thanks! Installing now 23:04:27 koobs, yes. 23:05:09 iio7: do you use ports or packages? if packages, quarterly or latest? 23:05:34 iio7: that /var/run/dmesg.boot and /var/log/message output (for the last boot) would be great (in the event the kernel mod is not loading correctly) 23:06:15 koobs, thanks for your time, one sec, I'll need to reboot. 23:07:21 And my desktop is running with p3 thanks for the headsup! 23:08:45 Ah and they fixed the dependency of KDE to samba 413 also 23:13:01 koobs, somehow kld_list="i915kms" was changed to kld_list="i914kms" in rc.conf, I have no idea how that happened. 23:14:55 iio7: changing it back fixes it? 23:15:11 koobs, yup. 23:15:14 win 23:15:28 On a completely different note, FreeBSD has so many tunables and settings available in both rc.conf, loader.conf and sysctl.conf, is that unique to FreeBSD? I don't see that many options on the various Linux distros config files. 23:17:01 There are GRUB options while loading kernel to start a system. System MIBs do exist on Linux too 23:17:49 MIBs? 23:18:08 Having not tried to set an option does not mean lack of it (or the complexity itsefl) 23:18:17 s/itsefl/itself/ 23:18:58 MIB: Management Information Base 23:20:45 iio7: linux has plenty too 23:21:00 iio7: rc.conf is 'rc' (post init) time, think about it as userland startup 23:21:01 parv: boot environments for the win, I could just rollback when that happend, ignore the update for a while longer and then decided to do a reinstall (with copying all systemconfigs to the other zpool in the machine and copying them back after the reinstall, I just forgot that I had some symlinks setup for poudriere, so that costed me some time) 23:21:12 iio7: sysctl.conf is run during rc 23:21:22 loader.conf has sysctl tunables that have to be set much earlier 23:25:27 koobs, basically, most of that is configured using systemctl for a distro with systemd. 23:31:20 Eh? GNU/Linux still uses sysctl.conf. 23:32:00 iio7: *nods*, same here, vast majority of tunables here are userland (runtime) tunable 23:32:41 Ah, reading scrollback. iio7: loader.conf is roughly equivalent to GRUB and the initramfs on GNU/Linux. sysctl.conf is analogous to sysctl.conf. rc.conf is a centralized way to specify services to be run, which varies wildly by Linux distribution. 23:33:35 Thanks guys for clarifying :) 23:33:39 pleasure 23:36:31 I have just logged into one of my Linux boxes, oh yes, sysctl.conf has a ton of kernel parameters, I didn't know that.