seems related, maybe. truenas.com/community/threads/nfs-d…rt-server-side-copy-with-zfs.103309

Title: NFS does *not* support server-side copy with ZFS? :( | TrueNAS Community

presumably that is refering the native ZFS exports? I'd have thought that exports handled by the OS would be filesystem agnostic

nfs is not quite filesystem agnostic but i'm not sure of the details. if by native zfs exports you mean sharenfs, that's just a mechanism to automatically recursively list zfs datasets in an nfs exports file

(well at least sharenfs used to be that, not sure what it does on openzfs)

scoobybejesus: seems like it could account for the difference when copying locally, but would it account for the difference when receiving the snapshot? in other words would zfs introduce sparseness? (no idea)

but i would still think that such a large difference in filesize would be difficult to be accounted for just by sparseness when it's a multimedia file...

it is prod that is taking up more room than backup. writing the snapshot to the backup box takes up as much room as the file should take up. initial writing of the file by an NFS client (linux, otherwise ext4) is where the sparseness shows up.

it's weird that i could probably script something to cp every file in place and save over 33% of the disk space used up by that dataset. i'd like to think that wouldn't wreck havoc on the database watching those files.

scoobybejesus: how are you getting th snapshot to the backup box

yeah, by sparseness i mean reduced space thanks to the filesystem recognising the gaps

jmnbtslsQE, sorry by native exports I meant those handled by ZFS directly, rather than those handled by freebsd with nfsd etc

I am using syncoid

just realised i was assuming possibly wrongly this whole time that you were backing up using zfs send/recv

syncoid does use zfs send/recv under the hood, glueing in mbuffer and compression over the wire

Trying to install a fresh copy of FreeBSD 14 onto a ThinkPad X270 with an existing FreeBSD installation. NVMe disk isn't showing up in any of the guided disk setup menus, but is in /dev (and was what I had originally installed the current OS on). Any idea why this might be?

I vaguely recall something about some UEFI settings on ThinkPads...

(using the memstick.img)

how did you get 13 onto it, if that's what you're using?

therein lies my confusion. It was a long time ago, but I used the memory stick image also. I suspect it's something to do with the disk being MBR-formatted. I'm going to drop into a shell and wipe it/convert to GPT and try again.

14 implemented a new nvme driver I believe

used to be nvd - man.freebsd.org/cgi/man.cgi?query=nvd&sektion=4&format=html

Title: nvd(4)

is now nda - man.freebsd.org/cgi/man.cgi?query=nda&sektion=4&format=html

Title: nda(4)

yeah that did the trick - I can now select the disk

lkdload nvd?

*kldload

what did? reformatting the nvme disk as GPT?

sorry, reformatting as GPT

it might be a bug with the installer then

it should allow you to select it

ok that makes more sense. nda supposedly is fully backwards compatible with nvd

the fun times of when you think a change is simple.. and by the end of your journey.. you are no closer than you were before: bughuntingfreebsd.wordpress.com/2024/03/07/fixing-self-referencing

Title: Fixing self-referencing.. – FreeBSD Bug Hunting

is there a tool that automatically switches the current ports branch to the latest quarterly one every quarter

Does pkg allow me to find all the packages that depend on Qt-5.10.15, plz?

strange

If exoflux had stayed I would have suggested this one-liner: for p in $(pkg info); do pkg query '%dn' $p | grep -q '^qt5-' && echo $p; done

That's installed packages not all packages that one might install but...

i think i came up with a solution

0 0 2 */3 * root git -C /usr/ports switch $(date +%YQ%q)

in cron

Clever! (Though I am unfamiliar with git-switch and wonder how it differs from git-checkout. It's not important that I know this though.)

i just got git switch from the wiki

Title: Chapter 4. Installing Applications: Packages and Ports | FreeBSD Documentation Portal

it might need a git pull as well though

I have quickly scanned the man page for git-switch and it says "does not require a clean index and working tree" so that's one difference. git-switch is a new command, still marked experimental, and I just have not interacted with it before.

i cant recall ever using it

i just figured out that nixbsd (github.com/nixos-bsd/nixbsd) is a thing so i want to integrate it in my nixos config github.com/Kreyren/nixos-config so that i can just on demand switch kernels linux/bsd.. is there any painless way to check how well will the devices run on bsd? e.g. I am helping with development of linux kernel for OLIMEX Teres-I it would be cool if it could do *BSD as well :P

Title: GitHub - Kreyren/nixos-config: My WIP nixos configuration

I'd suggest starting with freebsd.org/releases/14.0R/hardware if you haven't looked at it already. Next in order would be searching dmesgd.nycbug.org/index.cgi , then booting FreeBSD on that if feasible. (For NetBSD and OpenBSD, I'm not sure, but something similar to the first URL on their respective websites may exist.)

Title: FreeBSD 14.0 Hardware Notes | The FreeBSD Project

soo apparently people in linux-sunxi tested it, it should work, but lacks some kernel things like governer support etc..

how different is it to submit patches to freebsd? I will try to contribute few once i finish working on robust linux 6.5+ support

V_PauAmma_V, thanks that's helpful i also found bsd-hardware.info which should work with linux-hardware.org probe to get more details on the exact modules?

freebsd.org/releases/14.0R/hardware also the website explicitly says A64-Olinuxino is supported which is the board that was used to develop OLIMEX Teres-I and uses the same hardware

Title: FreeBSD 14.0 Hardware Notes | The FreeBSD Project

I'll leave your question about submitting patches to a developer, but IIRC they'll take (some) pull requests on Github.

integrating nixos into the freebsd world sounds both awesome and difficult, given that nixos is fairly linux centric, though i suppose with enough effort, it's possible to factor out direct dependencies

i would be surprised if these packages actually worked given how many patches are laying around in our ports tree that upstreams don't want

scoobybejesus, it seems that the nixos-part is already handled by the nixbsd but it seems to need adjustments for packages and modules to work on linux and freebsd

i'm eager to see updates on this :)

tracked in Kreyren/nixos-config #4

Title: Implement nixbsd · Issue #4 · Kreyren/nixos-config · GitHub

4 – You can mount a filesystem multiple times "on top" of itself bugs.freebsd.org/bugzilla/show_bug.cgi?id=4

I first need to handle git.dotya.ml/KREYLIMEX/TERES/milestone/21 but that's near finished

Title: Maintanance - TERES - git.dotya.ml

Is there something like sunxi-oriented work for BSD btw? e.g. linux-sunxi.org/Olimex_Teres-A64 is for linux and patches are then handled sent to linux from megi's (sunxi dev) git repository

Title: Olimex Teres-A64 - linux-sunxi.org