03:55:49 <last1> is the compression in zfs similar to gzipping a file ?
03:59:36 <RhodiumToad> I believe each record is compressed separately
03:59:50 <RhodiumToad> (so the recordsize matters)
04:13:36 <rustyaxe> win 14
04:14:39 <last1> I think my compressratio is very poor because my files are smaller than 128k which is the default recordsize
04:14:51 <last1> any downsides to having a recordsize of say 8k ?
04:16:02 <RhodiumToad> small recordsizes reduce the compression opportunities (for files larger than the record size)
07:44:23 <ikkuranus-> I have an efi system running freebsd with a zfs mirror for /. One of the drives failed and I have resilvered it onto a new one.
07:44:47 <ikkuranus-> How do I restore the efi partition on the new drive
07:46:32 <parv> Create the same size partition of FAT16 or -32 (whatever that is); then copy the files
07:46:47 <ikkuranus-> the efi partition appears to be there but it's not mountable like it is on the other drive
07:49:23 <ikkuranus-> https://pastebin.com/ydBdxnSS
07:49:24 <VimDiesel> Title: => 40 234441568 ada0 GPT (112G) 40 409600 1 efi (2 - Pastebin.com
07:51:06 <ikkuranus-> ada0 is the replacement
08:00:31 <RhodiumToad> ikkuranus-: what did you do to create the partition?
08:02:00 <ikkuranus-> I don't remember. It was a while ago
08:04:19 <RhodiumToad> ikkuranus-: what do you get from  file -s /dev/ada0p1  and  file -s /dev/ada1p1
08:05:40 <ikkuranus-> . /dev/ada0p1: data
08:05:57 <ikkuranus-> ./dev/ada1p1: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID "BSD4.4  ", root entries 512, sectors 1600 (volumes <=32 MB), sectors/FAT 5, sectors/track 63, heads 1, serial number 0xbd4111ee, label: "EFISYS     ", FAT (12 bit), followed by FAT
08:08:09 <RhodiumToad> ok, so you never did a newfs_msdos on the new partition
08:08:29 <RhodiumToad> since it seems to be the exact same size, you could just dd the old one onto the new one
08:09:56 <RhodiumToad> that said, the old one looks like it might have been copied from an install image rather than properly created
08:10:22 <RhodiumToad> if you mount the old one, how large is it?
08:11:36 <ikkuranus-> 780K 387Kused
08:12:45 <RhodiumToad> that's rather small given that it's on a 200MB partition. definitely copied from an image
08:13:20 <RhodiumToad> the EFI spec requires a larger size (minimum 100MB I think), whereas install images are created as small as possible
08:13:40 <RhodiumToad> so the best thing would be to newfs_msdos the new one, and copy the files
08:14:26 <ikkuranus-> I assume I need to delete it first before running that
08:14:33 <RhodiumToad> no
08:14:52 <RhodiumToad> you already have the partition, you just don't have a filesystem in it
08:15:08 <RhodiumToad> just to check, though, what is your zpool configuration
08:15:29 <ikkuranus-> mirror
08:15:47 <RhodiumToad> and it shows two devices, ada0p3 and ada1p3 ? exactly those names?
08:15:56 <ikkuranus-> yup
08:16:05 <ixmpp> TIL android does now support ikev2 for ipsec
08:16:14 <ixmpp> that makes it much more attractive
08:16:20 <RhodiumToad> and swapinfo shows ada0p2 and ada1p2 ?
08:16:39 <ixmpp> wait, that was in -social, sorry
08:16:49 <ikkuranus-> yup
08:17:33 <RhodiumToad> ok, so  newfs_msdos /dev/ada0p1   should be safe
08:18:30 <ikkuranus-> ok it mounted now I can copy it over
08:19:04 <RhodiumToad> copy it as files, yes
08:19:26 <RhodiumToad> though probably you only have one or two files
08:20:41 <ikkuranus-> that's right
08:21:47 <ikkuranus-> thank you
08:35:51 <luna> https://www.bsdnow.tv/504 FreeBSD 13.2 release episode
08:35:53 <VimDiesel> Title: BSD Now 504: Release the BSD
09:19:15 <_0pr_> test test
09:19:32 <dch> _0pr_: syn ack
10:07:46 <debdrup> _0pr_: test successfully failed
10:07:57 <debdrup> with status code 0
10:15:55 <debdrup> https://cgit.freebsd.org/ports/log/?qt=grep&q=capsicum this seems worth keeping an eye on
11:09:43 <ghoti> So... I'm trying to pass through a pci device to a bhyve vm. Followed https://wiki.freebsd.org/bhyve/pci_passthru and the churchers/vm-bhyve man page, and from the host side I guess things look good, but my guest doesn't see a new pci device.
11:09:44 <VimDiesel> Title: bhyve/pci_passthru - FreeBSD Wiki
11:10:55 <ghoti> I see that `vm passthru` will tell be what devices are *ready* to be passed through, but is there a way to see what is currently being passed through in-the-moment?
11:11:42 <RhodiumToad> what exactly did you do?
11:11:50 <ghoti> The guest is a HAOS, a linux appliance.
11:13:02 <ghoti> I used `pciconf` to identify the peripheral's PCI location, then added that to 'pptdevs' in /etc/loader.conf, then added `passthru0="..."' to /vm/haos/haos.conf
11:13:43 <ghoti> The card is at 3/0/0, perhaps I should have used that instead of "...". :)
11:14:52 <ghoti> Oh, and there was a host reboot in there, so `pciconf` identified the card as "ppt0" instead of "xhci0".
11:15:07 <RhodiumToad> are you loading vmm in loader.conf or in rc.conf?
11:16:30 <ghoti> loader.conf.
11:17:00 <RhodiumToad> ok, and did you also specify to the relevant bhyve instance that it should claim the device?
11:17:02 <ghoti> I think when I did not, I didn't get a ppt0.
11:17:28 <ghoti> Er, that would be the vm configuration, would it not?
11:17:32 <RhodiumToad> yes
11:17:37 <ghoti> I'm using churchers/vm-bhyve
11:18:00 <RhodiumToad> ppt0 is visible in the host when you have pptdevs= and vmm loaded in loader.conf
11:18:28 <RhodiumToad> but you have to explicitly specify that bhyve should pass it through to a specific guest
11:18:49 <ghoti> > grep passthru /vm/haos/haos.conf
11:18:50 <ghoti> passthru0="3/0/0"
11:19:32 <ghoti> Is there some other place as well?
11:19:49 <RhodiumToad> I don't know vm-bhyve
11:20:04 <RhodiumToad> can you see what command-line options it used when starting the guest?
11:20:34 <ghoti> Ya, that would help. I'll try. It changes its text for ps.
11:33:07 <ghoti> I can't find a way to see the options that vm-bhyve generates, but all the instructions I've seen make sense and I've followed them. :(
11:33:46 <ghoti> vm-bhyve also has a "bhyve_options" config option, so perhaps I'll try the freebsd-wiki-way with that.
11:35:29 <RhodiumToad> have you specified that the guest memory is wired down?
11:36:01 <RhodiumToad> (passthrough requires that)
11:38:34 <ghoti> No luck with bhyve_options, the `lspci` output is the same. I have not specified that; if it's required, I would have expected vm-bhyve to "take care of it" for me if I specified a passthru device in the config. Is that mentions in the wiki?
11:39:26 <ghoti> It doesn't seem to be in the Requirements section of https://wiki.freebsd.org/bhyve/pci_passthru ..
11:39:28 <VimDiesel> Title: bhyve/pci_passthru - FreeBSD Wiki
11:45:31 <RhodiumToad> "The "-S" option must be passed to both bhyveload(8) and bhyve(8) to wire guest memory."
11:56:19 <ghoti> Does that mean that -S is required for passthru, even though it hasn't been mentioned earlier, or just that it's required for wiring guest memory, which also hasn't been mentioned earlier?
11:57:39 <RhodiumToad> you can't use passthrough without wired guest memory
11:58:24 <yuripv> "Guest memory must be wired using the -S option when a pass-through device is configured." from bhyve(8)
11:58:41 <RhodiumToad> if -S is not given, passthrough configuration will be ignored with a warning
11:58:48 <ghoti> as you said, I just haven't found documentation that says that. The "additional note" you quoted doesn't quite say that, though the wording is unclear.
11:59:29 <RhodiumToad> I would expect vm-bhyve to have some specific option for specifying wired memory
11:59:43 <ghoti> if -S is required, why would the wiki page not even mention its syntax?
12:00:12 <RhodiumToad> ... it does?
12:00:41 <ghoti> not that I saw.
12:01:01 <ghoti> Step 5 is all about "-s" which is a different option..
12:01:12 <RhodiumToad> it's just -S, there is no more to it than that
12:01:35 <ghoti> vm-bhyve has a "wired_memory" config option, but doesn't mention any connection to passthru.
12:02:07 <RhodiumToad> well, you need to enable that
12:02:15 <ghoti> Okie, I'll try it with -S added as a bhyve option. We'll see if it changes. :)
12:02:29 <RhodiumToad> no, use vm-bhyve's wired_memory option
12:06:31 <ghoti> Tried both, neither changed anything. Perhaps my get OS is at fault, I dunno.
12:06:40 <ghoti> guest
12:09:05 <ghoti> I'll try again using a freebsd guest for testing, where I'll know the diagnostic tools better.
12:20:00 <yuripv> ghoti: is "/etc/loader.conf" a typo?
15:57:00 <ghoti> yuripv: yes, that was a typo.
17:17:51 <ghoti> Hmm. I'm getting ld-elf.so.1: /usr/local/bin/gimp: Undefined symbol "g_string_free_and_steal" when I try to launch a freshly-installed gimp. I see that `g_string_free_and_steal()' was added to GLib 2.75.3 in February, but I'm running version 2.74. Upgrading to the latest, 2.76, lets gimp run.
17:17:56 <ghoti> Can packages not have version dependencies, or only ports? Or would it have to be done with a bespoke pre-install script?
17:22:55 <parv> Were no dependencies updated with update of gimp?
17:23:51 <parv> OTOH if something else was updated under gimp, that would also explain the error
19:04:54 <wikan> hi
19:05:15 <wikan> i came here to ask if qemu has kernel acceleration under freebsd?
19:05:37 <wikan> i wonder what is better qemu or virtual box or something else
19:55:29 <VVD> wikan, for amd64 use bhyve.
20:03:49 <last1> so if I get this right, in zfs a small recordsize is ideal for applications that need to modify small blocks within large files
20:03:56 <last1> aka vmdk files, or other large binaries
20:04:09 <last1> and 128k is sort of the default middle-ground
20:14:58 <rwp> last1, In all file systems the choice of block size is a compromise.  Smaller is more packed but more overhead and larger is more efficient with less overhead but more wasted unusable fragments.
20:15:46 <rwp> Historically block size used to be smaller but that caused impractically large amount of overhead and counter overflows.
20:16:12 <rwp> So block size has been steadily increased over the years as storage sizes has increased to what feels like huge sizes now compared to a decade ago.
20:16:51 <rwp> This results in more inefficient use for storing small bits of data.  But we now have support for this much larger total amount of storage to compensate.
20:18:27 <rwp> I don't know what would be the best block size for vmdk virtual machine back end storage files.  In the end there is no substitute for benchmarking.
20:19:01 <last1> well here's the thing about zfs recordsize, from what I read
20:19:11 <last1> if I set it to 1M and my file is 4k it will still occupy 4k
20:19:17 <VVD> At least use compression=lz4. :-o
20:19:37 <last1> so large recordsizes in zfs doesn't command wasted fragments
20:20:56 <last1> "Therefore, for simple file sharing you should typically set recordsize=1M—tiny files take care of themselves by being stored in tiny blocks, requiring no additional tuning. But your large files get the benefit of higher compression ratios, fewer I/O operations required to read or write the file, fewer indirect blocks, and less impact from on-disk fragmentation."
20:21:02 <last1> from: https://klarasystems.com/articles/tuning-recordsize-in-openzfs/
20:21:03 <VimDiesel> Title: Tuning recordsize in OpenZFS | Klara Inc
20:29:16 <ghoti> wikan: I use bhyve. It is excellent. I used to use VirtualBox. bhyve performs WAAY better than vbox.
20:48:10 <wikan> ghoti thanks
22:41:58 <Erhard> Would it be silly to think that I could use a GPU in a FreeBSD bare metal machine from within a linux bhyve VM running on that machine? (Knowing that I need the GPU full power for CUDA processing...)
22:42:39 <LxGHTNxNG> it is demonstrated, but experimentally
22:43:10 <Erhard> I see.
23:44:43 <concrete_houses> is freebsd performance near archlinux?  how does netbsd compare?  dragonfly?
23:50:11 <last1> performance at what ?
23:57:15 <LxGHTNxNG> concrete_houses: for all the BSDs the WiFi is slower than Linux but inroads are being made