shur3d1d ago

#Backup question to the community

Using modern filesystems like #btrfs, isn't there a easy to handle solution to make snapshots and back them up with good #ux?

In my case, running #NAS on #TrueNAS, I guess I can leverage:
- Create #zvol
- Ise #btrbk, targeted to this zvol

Is there another solution? #WebUI? #GUI? #Docker?

Show threadMulti Purr Puss Jul 10, 2025

🧵 2/n ..strike the encrypted container requirement!

I can just set up a #LUKS #ZFS #ZVOL, on the NAS, and mount it via ssh - this is fine.

I just need something that can RESTORE a #Linux #Backup via LAN.

BTW: this rather "special" requirement ONLY exists, because #Valve #Steam #gaming #Flatpack CAN'T properly use other partitions as an "external library"! (i've tried, and failed) ..it's that sandboxing/namespacing nuisance, i guess!

Show threadFelix Palmen  Aug 23, 2024

@vermaden I knew 😉 and if I ever had the need to run #UFS on bare metal, I'd probably consider them.

But with a #zvol backing the virtual disk, I prefer just snapshotting that for safety and do the dance upgrading in place.

Show threadTomAokiMay 3, 2024

@zirias @parvXtl
Ah, thanks! I've completely overlooked the use case.
But it would require supports to accepting/handling trim from guests on host/hypervisor side.

#bhyve #zvol #hypervisor

Show threadFelix Palmen 📯May 3, 2024
@TomAoki @parvXtl It also makes sense on virtual disks, no matter how they are backed. #bhyve can shrink a sparse #zvol when the guest issues trim commands 😉
Felix Palmen 📯Mar 16, 2024

Short story, if you have massive stalls with heavy I/O load on #ZFS in #FreeBSD 13.3, try the #patches from here:
https://bugs.freebsd.org/275594

Longer story: My ZFS pool (on spinning disks) behaved "suboptimal" ever since upgrading to FreeBSD 13 (so, #OpenZFS). Heavy I/O started to stall the whole system for seconds, I had to adapt my poudriere settings (less parallelism) to somehow work around it. With the 13.3 kernel, this escalated to a point where the system was just completely unusable and nothing helped any more 😞.

Then I found the PR linked above and tried with the patches from there, and guess what, the behavior is completely fixed, just like it was on FreeBSD 12. I can put a load of 40 and more (on a quad-core with HT) with poudriere, at the same time do a build of world or even another "testport", and the machine stays responsive while serving homes via #NFS from the same pool, even a bhyve VM with a Windows server backed by a #zvol on this same pool still works fine 🥳

275594 – High CPU usage by arc_prune; analysis and fix

Show threadTomAokiFeb 17, 2024

@endrift
Not sure it can help or not, issues like this is discussed here.

https://forums.freebsd.org/threads/how-to-use-gpart-on-devices-created-on-zfs-with-volmode-dev.86789/

#FreeBSD #ZFS #ZVOL

ZFS - How to use "gpart" on devices created on ZFS with "volmode=dev"?

Most likely I'm missing something obvious, I thought this should be straight forward: # zfs create -V256G -o volmode=dev zroot/ubuntu # gpart create -s gpt /dev/zvol/zroot/ubuntu # gpart: arg0 'zvol/zroot/ubuntu': Invalid argument Then I used sysutils/gdisk, successfully created the...

The FreeBSD Forums
Show threadjzdmJul 26, 2023
Ah, die Ursache scheint #ZFS zu sein, das < 63 Zeichen für die Länge des Namens eines #Zvol empfiehlt… Ich dachte, das Z in ZFS steht dafür, dass es das letzte benötigte Dateisystem ist, aber dann scheitert es an 63 Zeichen 🙄
cJul 22, 2023

HAOS with a TrueNAS VM

https://fediverse.blog/~/c/HAOS%20with%20a%20TrueNAS%20VM/

HAOS with a TrueNAS VM