01:29:25 <antranigv> it was indeed an issue with 2TB+, maybe the new data was in the 2TB+ area
01:29:39 <antranigv> user decided to add a small NVMe for boot.
01:29:46 <antranigv> tsoome_ thank you very much for your help.
01:30:02 <antranigv> I'm acting as a bridge between discord and IRC questions and knowledge bases :))
01:33:37 <johnjaye> i thought a bridge displayed something in brackets on each message. e.g. [Discord user #123] hello there
07:11:08 <grahamperrin> FYI there seems to be a public log of this channel. I'll not disclose the URL.
07:19:56 <ghodawalaaman> how to make sure if the gpu driver is loaded or not?
07:33:44 <grahamperrin> ghodawalaaman, what's the GPU?
07:34:11 <ghodawalaaman> grahamperrin: it's skylake (in-built GPU)
08:02:25 <grahamperrin> ghodawalaaman, kldstat | grep i915kms
08:12:20 <ghodawalaaman> grahamperrin: it returned nothing
08:13:11 <ghodawalaaman> here is the kldstat output: https://termbin.com/ud89
08:14:22 <grahamperrin> Which version of FreeBSD, exactly? Packages of ports from latest, or quarterly?
08:15:03 <ghodawalaaman> it's 14.2-RELEASE
08:15:11 <grahamperrin> freebsd-version -kru ; uname -aKU ; pkg -vv | grep -B 1 -e url -e priority
08:16:53 <ghodawalaaman> https://termbin.com/vwvg
08:21:26 <grahamperrin> OK, AMD64.
08:21:28 <grahamperrin> pkg query '%o %v %At:%Av' drm-61-kmod
08:24:57 <grahamperrin> I have no idea how new or old Skylake is, I guess it's Intel
08:25:23 <ghodawalaaman> that command returned nothing
08:25:27 <tsoome_> antranigv you are welcome.
08:25:27 <ghodawalaaman> yes it's intel
08:25:41 <grahamperrin> pciconf -lv | grep -B 3 -A 1 display
08:26:37 <ghodawalaaman> https://termbin.com/ap6xl
08:26:39 <ghodawalaaman> a
08:30:52 <grahamperrin> <https://bsd-hardware.info/?probe=adcbf8a526#pci:8086-1912-1028-07a3> worked with i915 with 14.0-RELEASE-p5, so
08:31:08 <grahamperrin> you should install two things:
08:31:22 <grahamperrin> a) drm-kmod
08:31:36 <grahamperrin> then
08:34:03 <ghodawalaaman> I have installed drm-kmod, it was pretty big package
08:34:27 <ghodawalaaman> I also added kld_list="i915kms" in /etc/rc.conf
08:34:43 <grahamperrin> pkg add https://pkg.freebsd.org/FreeBSD:14:amd64/kmods_quarterly_2/All/drm-61-kmod-6.1.92.1402000_3.pkg
08:36:04 <ghodawalaaman> the most recent version of drm-61-kmod-6.1.92 is already installed
08:36:17 <grahamperrin> pkg add -f https://pkg.freebsd.org/FreeBSD:14:amd64/kmods_quarterly_2/All/drm-61-kmod-6.1.92.1402000_3.pkg
08:37:10 <ghodawalaaman> done
08:37:57 <grahamperrin> Now restart the OS, hopefully you'll see a flicker when the module loads. With or without a flicker:
08:38:17 <grahamperrin> kldstat | grep i915kms
08:38:27 <ghodawalaaman> ohk, thanks
08:38:37 <grahamperrin> BBL, maybe. Bye.
11:34:08 <ghodawalaaman> Hello, I want to just add a message saying "make sure GPU driver is correctly installed" in sway/wayland section. how would I edit the handbook?
11:38:31 <ghodawalaaman> also this link on the handbook is broken (https://github.com/freebsd/freebsd-doc/blob/main/documentation/content/en/_index)
11:39:44 <ghodawalaaman> I have to make a Github account to contribute to the documentation.
11:50:28 <dch> ghodawalaaman: you don't have to do that, you can create a bugzilla account and send patches/issues there
12:02:56 <antranigv> Folks, I have a iSCSI server (NetApp), I am the iSCSI client (FreeBSD), the block device is formatted as EXT4. I can connect to iSCSI, I see the device, I can mount EXT4, but it's VERYYYYYYY SLOWWWW. Thoughts?
12:07:42 <ghodawalaaman> dch: sending patches this way is also new to me but I will try doing this way
12:08:11 <dch> antranigv: you're doing it via fuse I guess?
12:08:27 <dch> ghodawalaaman: no worries, feel free to ask here for help any time
12:08:29 <antranigv> dch mount -t ext2fs. I think that's *not* fuse.
12:08:36 <dch> aah yes
12:08:39 <antranigv> ghodawalaaman thank you for contributing.
12:09:53 <dch> antranigv: I would compare throughput of unmounted block device with dd .. vs mounted and look a bit at tcpdump in case there's any stupid MTU or similar things obviously not right
12:10:07 <dch> but I guess its probably just not a very optimised implementation on freebsd
12:10:58 <antranigv> dch I'll have a look with unmounted dd if=/dev/mydevice right now. If that's the case then I can copy the iscsi over dd, and then boot a linux vm for the ext parts
12:11:10 <antranigv> thanks for the tip uncle dch <3
12:11:14 <dch> ;-)
12:11:34 <dch> can you just pass the iscsi device through to a linux vm directly?
12:28:05 <jemius> why is data deep-copied when you move it from one data set to another on the same pool?
12:38:44 <antranigv> with dd I'm getting 10MB/s, but I have a 10Gbps link, and iperf shows 9.9Gbps and disk in dmesg shows 150MB/s for the speed.
12:38:54 <antranigv> faster than EXT4 mount, slower than what's needed.
12:39:37 <antranigv> jemius because datasets are indeed different filesystems. they start at inode 0, etc, basically a different filesystem indeed.
12:42:00 <jemius> makes sense
13:06:40 <ghodawalaaman> https:/github.com/freebsd/freebsd-doc/pull/443
13:06:51 <ghodawalaaman> could someone verify this pull request?
13:07:05 <ghodawalaaman> I have just made the pull request for adding a warning while installing sway
13:09:03 <dch> antranigv:  150MB/s is not far off a single NAS-level SATA disk throughput. whats the backing vdevs on the netap?
13:16:46 <jemius> so is it common pracitce on FreeBSD/ZFS to give each user his own dataset as home directory? I guess it's handy for example for limiting maximum homedir size
13:20:44 <dch> jemius: very common, not just for quotas. some users have multiple datasets, with different retention or replication (snapshot) policies, or different performance / tuning settings
13:29:45 <jemius> I see.
13:29:47 <jemius> Defragmentation is not a thing on ZFS, is it?
13:41:37 <ketas> zfs datasets are awesome
15:24:39 <futune> if i have zroot on mirror and physically remove one drive before powering up, will it boot normally?
15:25:01 <futune> (both drives have the bootcode)
15:25:13 <ivy> futune: yes, as long as your boot environment (EFI partitions, etc.) are redundant -- FreEBSD doesn't set that up automatically
15:25:19 <ivy> the pool will just import in a degraded state
15:26:28 <futune> hmm, that is true, and they are, but there is also a non zfs geom mirrored swap partition
15:27:03 <futune> will that assemble in a degraded state too? or halt the boot in some way if it fails?
15:28:05 <futune> and as for the zfs part, if i then power down afterwards, reconnect the drive, and power up, will it be easy to resilver it again?
15:28:48 <ivy> i would strongly recommend not putting zfs on a geom mirror, because geom doesn't understand checksums, which means ZFS cannot fix any data corruption in the mirror
15:28:59 <futune> no, no, zfs is not on a geom mirror
15:29:11 <futune> the swap partition is, because i dont want swap on zfs
15:29:12 <ivy> ah, i see what you mean
15:29:39 <ivy> yes, as far as i know, gmirror will still come up if one side is missing, although i've never actually tried that -- so i don't know how you recover that off hand
15:30:05 <ivy> (from what i remember though, you just use a gmirror command to overwrite one side of the mirror with the other)
15:30:30 <futune> that seems fine, as long as i can recover - its just swap, no permanent data
15:31:04 <ivy> right, mirrored swap is just about having the system not crash if a root disk dies, but it should still boot if a disk is missing
15:31:28 <ivy> i have done this extensively on Solaris but sadly not so much on FreeBSD
15:32:33 <futune> yeah exactly
15:33:27 <futune> i am mainly worried about the zfs resilver after putting the drive back
15:33:54 <ivy> that should be pretty straightforward, resilver does not interrupt service at all other than using a few iops
15:34:07 <futune> awesome, thank you ivy
15:34:50 <ivy> although, "a few iops" can actually be quite a hit to performance -- if that's a concern there are sysctls you can tune to adjust how fast the resilver runs
15:35:28 <futune> if it's just the root being slow it should be fine for me
15:36:35 <futune> this whole adventure is actually about replacing disks in a much larger array, but I don't have enough ports, and I don't want to temporarily degrade the critical data
15:38:31 <antranigv> dch I am okay with the iSCSI showing itself as 150MB/s, but I still get 10MB/s when actually doing dd :D
16:17:48 <dch> antranigv: maaybe check block size of dd vs whatever the network can support?
16:17:53 <dch> sounds like a mess anyway
16:19:58 <jemius> if you set copies > 1, does the file system then ensure that the redundant blocks are spread across the partition? I suppose it does, because having them next to each other would be very dumb
16:20:01 <antranigv> dch indeed. we're moving to the NetApp to the other supercomputer datacenter, so I need to take of my files. My FreeBSD and NetApp are 1KM afar, but the fiber has been giving us stable ~10Gbps.
16:39:14 <ivy> jemius: as far as i know, yes, but it's not as useful as you would think -- if you have two striped vdevs with copies=2, and one breaks, you can no longer import the pool at all
16:39:39 <ivy> or in other words, copies is not a way to just mirror certain filesystems
16:40:35 <jemius> ivy, what does "two striped vdevs" mean?
16:43:08 <dch> antranigv: I expect its the latency then. can you try the perf at the local DC for comparison?
16:43:35 <dch> jemius: nobody relies on copies>1 in practice. best to use mirrors or raidz combos, drives tend to fail in unexpected wats
16:44:15 <jemius> I had bit errors on certain sectors on a dying drive once.
16:44:22 <jemius> Anyways, why provide a feature that is not useful
16:44:40 <dch> jemius: a vdev is the lowest level of of zfs building blocks - it can be a physical block device like a disk partition
16:45:13 <dch> you can stripe 2 vdevs together, which yields a faster vdev but with less redundancy
16:45:33 <dch> you can mirror 2 vdevs, which results in redundancy but slower writes, and faster reads
16:45:35 <dch> etc etc
16:47:32 <jemius> You're simply talking about how you can organize your pool. A RAID of mirrors and so on
16:48:56 <ivy> jemius: the feature is useful, just only in very specific circumstances -- it's intended for the situation where you have, say, a laptop with a single disk, and you want to protect against some data being corrupted by bad blocks
16:49:36 <ivy> "two striped vdevs" mean a zfs pool configured as a stripe across two disks (akin to a raid0) -- some people think they can use copies=2 in this situation to provide redundancy, but you cannot
16:50:38 <jemius> Ah. No no, I'm not doing that. I have a 2-mirror
17:21:19 <asarch> I have four MBR partitions, in the first one a 36G-sized FreeBSD partition (created with Fedora's fdisk), then I created the BSD partition scheme in that partition with "gpart create -s bsd" but when I try to add the slices with "gpart -t freebsd -s 10G" I get "gpart: invalid argument", why?
17:32:10 <mzar> asarch: what is the exact command that fails ?
17:36:25 <asarch> Well, it is: "gpart -t freebsd -s 10G" but it seems because I did not add the MBR bootcode to the partition with "gpart bootcode -b /boot/mbr"
17:36:34 <asarch> ...first
17:37:43 <mzar> how would gpart know where to add this slice ?
17:38:10 <mzar> moreover there's no type "freebsd"
17:38:53 <mzar> asarch: take a look at this nice gpart primer by W. Block http://www.wonkity.com/~wblock/docs/html/disksetup.html
17:38:55 <asarch> I mean, freebsd-ufs
17:39:41 <mzar> "gpart -t freebsd -s 10G" - the syntax is wrong, please take a look at gpart(8)
18:04:49 <asarch> Bingo!
18:04:54 <asarch> Thank you!
18:04:56 <dch> asarch: I would not normally use BSD partition type these days, just `-s gpt`
18:05:02 <asarch> Thank you very much! :-)
18:05:19 <asarch> I know, but actually is an old PC
18:05:19 <dch> theres nothing wrong with it per se, just gpt is basically standard on all OS now
18:05:26 <dch> make sense
18:05:28 <asarch> With no UEFI support at all
18:06:26 <dch> asarch: UEFI and GPT partition types are IIRC orthogonal, but its if its a very old box then that makes sense
18:17:20 <asarch> A very old HP box
18:17:28 <asarch> It is still alive
18:18:01 <mzar> yes, using GPT if you have no MS Windows there will be best, both FreeBSD and Linux will boot fine
18:27:40 <mzar> but if the disk has already MBR laout and place for one primary partition for FreeBSD, they follow old MBR/BSD partiotioning scheme
18:27:56 <mzar> s/partition/slice