00:12:02 where we go: shrinking a zroot zpool by sending it to smaller drives. https://dan.langille.org/2025/11/22/test-run-moving-to-a-smaller-zpool-zroot-using-zfs-snapshot-and-send-recv/ 00:19:08 FreeBSe 14.3 00:19:10 heh 00:22:27 JetpackJackson: looking at ports I found prusaslicer 00:22:37 based off of sli3r 00:22:50 same shit orcaslicer is based off 00:24:05 Yeah I guess I can use that as a base for my port 00:31:22 Hmm they have instructions for how to build in docker 00:35:44 i got it to build past boost 00:35:58 With docker? Or the scripts 00:38:47 cmake build 00:42:00 Oh duh how'd I miss that 00:42:11 Thanks 00:44:03 i fixed the boost issue by removing system from the list 00:44:07 i install tbb 00:44:11 but still fails to find it 00:44:22 Hmm 00:45:01 just have to play with where cmake finds things 00:45:10 linux expects evertything isn /usr/ 00:45:19 we expect everythig in /usr/local 00:54:04 Had to fix my VM cause it ran out of room 00:54:15 So Happy that zfs can resize 00:55:09 I kinda wanna get mindustry to build too 01:16:37 zip: I love ed and still use it a lot. I use rlwrap enable vi-mode line editing. I only resort to vi for extensive source code editing as a last resort. 01:17:08 Then again, my shell (and libedit itself) is set to use vi mode. 01:18:59 I wrote/updated a large part of the vi-mode functionality in tmux because I use it so much. tmux+rlwrap makes ed a lot more usable. 01:19:28 it's a powerful and elegant program 01:42:12 topcat001: you using a custom plugin or do you use the vim-tmux-navigator one? 01:54:48 no, my tmux setup is fairly simple. I `set -g mode-keys vi` basically. The vi keys are most handy in copy-mode and : cmd line editing. 01:55:44 one could argue that I cheat by running ed inside tmux and rlwrap :) 03:41:46 I am excited about version 15 and that's so strange to me, normally I'm not excited about system updates lol 03:48:14 15.0-release will be the holiday gift to the FreeBSD community 04:55:14 ya im excited 04:55:34 big moves in freebsd world. pkg base and oci support 12:51:22 kerneldove_: what is pkg base 12:54:54 instead of managing the base system via freebsd-update and other tools, there is a pkg repo for stuff in the base system and you can decide more fine grained what parts of base you want 12:54:56 splitting the OS itself up into individual pieces that can be independently versioned and upgraded 13:20:17 Oooh 13:20:26 That sounds cool 13:21:58 kerneldove_: that sounds like something my native boot proposal'd be able to help out with 16:47:00 87.2T 68.9T 18.3T - - 3% 79% 16:47:05 starting to get dangerous heh 16:47:11 is the 80% thing still a thing? 16:47:52 Upgraded to 90% or so 16:48:09 oh really? 16:48:24 is that when i'll start seeing massive performance loss? 16:48:50 https://github.com/openzfs/zfs/discussions/13511 16:50:47 You should still have an upgrade (or data deletion) path planned by now 16:54:55 yeah. i'm already working it out in my head. i mean it's a personal pool so it isn't THAT serious ... but i was going to make use of raidz expansion and add 4 8TB drives as another vdev and grow it from there 16:55:10 (as raidz2 on a separate vdev) 16:56:12 i'm just going to wait on RELEASE before i try doing that just to make sure fbsd 15 is settled 16:56:29 i'll be a little limited once i upgrade the pool 17:05:43 You could also just build a new server with new disks and have the current one as a new kickass backup server 17:09:32 This 17:10:11 This "move zroot from larger devices to smaller devices" is now ready for production: https://dan.langille.org/2025/11/23/test-run-moving-to-a-satadom-based-zpool-zroot-using-zfs-snapshot-and-send-recv/ 17:26:43 isn't this easier to just change openzfs to allow that mode 17:27:08 to avoid people doing stupid hacks 17:28:30 ketas: what do you mean by "that mode"? 17:29:22 shrink zpool while replacing devices 17:30:19 ketas: It does support it, see what I did here: https://dan.langille.org/2025/11/22/moving-a-zpool-to-smaller-drives-with-uefi-zfs-freebsd/ 17:31:34 that leaves that questionable map 17:31:39 ketas: two problems I have with that approach: 1 - it mangles the gpart settings for the old drives, meaning you can't just boot from them again. 2 - there is a slight, and I mean trivial, cost associated with a table to redirect from the old stuff to the new stuff. 17:32:38 ketas: I did several runs with both approaches. The send | recv approach sat best with me. 17:33:00 how come there's no "table" when you put larger device there 17:33:32 also why any outside of zfs thing matters 17:33:37 any gpt etc 17:34:02 ok, how does zfs replace disk anyway? 17:34:18 it only copies data, i understand 17:34:34 ketas: moving to larger devices usually involves `zfs replace` - shrinking is different, you add another mirror, in effect you start striping. Then you remove the original mirror, zfs evacuates all the date to the new drives. 17:35:07 ketas: My specific use case is the zroot pool, which involves partitions. 17:36:36 so if i have 100m data on 1g pool and want to replace 1g device with 500m one, and i can't then why? 17:36:57 does it write it to the +800m mark or what 17:37:00 ketas: who says you can't? 17:37:03 on new device 17:37:26 ketas: In my tests, I went from 240G to 30G 17:37:40 and from 240G to 128G 17:38:13 the table in question assumes that it has some immovable data there 17:38:19 or i don't know eh 17:40:13 ketas: I can't help you there, I just know the zfs folks seem to know what they're doing. 18:08:43 "the table" ? 18:09:52 rtprio: https://openzfs.github.io/openzfs-docs/man/master/8/zpool-remove.8.html mentions a mapping table. 18:10:32 See "Removal of vdev 0 copied 452K in 0h0m" at https://dan.langille.org/2025/11/22/moving-a-zpool-to-smaller-drives-with-uefi-zfs-freebsd/ 19:37:08 dvl: I can see it worked, but I just cant comprehend that zfs can allow removing a vdev from a stripe... Or am I misunderstanding something? 20:11:31 I am planing to learn FreeBSD.. B$$ companies are using it.. Have to find out that whats include in it which Linux doesnt have .. Freebsd and Linux kerenel is Same ? 20:13:27 no 20:18:21 hmm.. so Linus Torvalds kernel work is only for Linux.. well some one game a very good example.. Freebsd is a Complete Car and Linux is only an Engine.. which need body parts for making it a complete car.. and specially freedom from License point of view.. thats intereseting.. 20:22:13 Tingo: you can find a lot of info online on the differences 20:24:16 yes.. Reading it .. and its interesting to know more about Freebsd.. well, Thanks!! 20:27:40 You can think of the Linux kernel development as an autocracy while FreeBSD development is more democratic :P 20:31:34 kenrap: it gets old having to explain the differences when it can all be done with a few google searches 20:33:49 cpet: yeah. I thought I would throw in some "fresher perspectives" rather than "Linux is just a kernel and single component while FreeBSD is a complete and cohesive OS" 20:34:21 kenrap: pretty much what it is 21:27:09 i am working with a dataset storage/postgres which contains a database.. that is running in a FreeBSD jail.. when I make changes to the zfs dataset, say zfs set primarycache=metdata storage/postgres do the options on the server "trickle" down to the freebsd jail? 21:27:51 i have been looking over the internet and it talks about how the dataset will take the options.. but i am not seeing anything if i have to worry about the FreeBSD jail aspect, my gut is telling me no. 21:33:11 voy4g3r2: normally it will take on the option of the main dataset so if you have /var and you create /var/slaps and you dont add any options it will copy over the ones form /var now if you set options to /var/slap they wont revert back to /var 21:33:16 is that makes any sense :P 21:36:30 that is the inherit option 21:36:33 correct? 21:36:51 i think it does, if my statements are correct :) 21:37:09 * voy4g3r2 is on the verge of moving the WAL options to its dedicated pool and hard drive.. 21:39:21 voy4g3r2: yeap 21:42:26 okay cool.. so my changes to that dataset and not pool are working.. it is saying local when i am making modifications 21:51:09 voy4g3r2: are you making changes to that zfs or its parent? 22:04:13 damn default webfonts dont have Time new roman 22:06:09 rtprio: to the dataset itself 22:06:35 another example is making sure the blocksizes are 8k :) 22:17:55 https://www.reddit.com/r/freebsd/comments/1iven5k/reflinks_in_freebsd/ oooh so now cp will reflink by default if pool supports block cloning 23:52:11 im running into an issue here. I am using 32 bit netmask addresses for vnet jails and am pretty sure I have all of my static routes set up. On the host side I can ping and traceroute to the jail. However, on the jail side I seemingly cant traceroute, but I can ping the host. the jail also cant traceroute its loopback address, which is very strange. any ideas? 23:52:34 I should note, I have this same setup on another box and it works perfectly as expected. 23:53:49 are you able to paste the setup somewhere.. so we could take a gander? 23:53:55 like a pastebin type thing 23:55:32 yeah sure, what specifically do you think you'd wanna look at? I can post a few things 23:55:40 do you have pf enabled by any chance? anything in the logs? 23:55:41 the whole thing 23:56:30 i've been meaning to implement a proper pf ruleset for a server + jails for a few years but have not made the time yet but its on my radar so this sounds very relevent :) 23:56:32 nope, no firewalls should be enabled. this is a fresh freebsd install im working on. gathing stuff 23:57:31 allow.raw_sockets=1 ?