Shakedown Social

Kevin Karhan :verified:<a href="https://udongein.xyz/users/lispi314" class="u-url mention" rel="nofollow noopener" target="_blank">@lispi314</a> <a href="https://hachyderm.io/@hlangeveld" class="u-url mention" rel="nofollow noopener" target="_blank">@hlangeveld</a> <a href="https://mastodon.social/@openzfs" class="u-url mention" rel="nofollow noopener" target="_blank">@openzfs</a> <a href="https://wetdry.world/@memoria" class="u-url mention" rel="nofollow noopener" target="_blank">@memoria</a> Yes, but still folks in the <a href="https://infosec.space/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a> community like <a href="https://mastodon.social/@allanjude" class="u-url mention" rel="nofollow noopener" target="_blank">@allanjude</a> will recommended people to stay off <a href="https://infosec.space/tags/SMR" class="mention hashtag" rel="nofollow noopener" target="_blank">#SMR</a> in general until it's improved...

Samuel ChaseFor those of you have been programming for more than a decade, what programming languages, ecosystems, technologies do you wish you had spent more time with?For me, it would be: <a href="https://fantastic.earth/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a>, <a href="https://fantastic.earth/tags/Perl" class="mention hashtag" rel="nofollow noopener" target="_blank">#Perl</a>, <a href="https://fantastic.earth/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a>, <a href="https://fantastic.earth/tags/TLA" class="mention hashtag" rel="nofollow noopener" target="_blank">#TLA</a>+, <a href="https://fantastic.earth/tags/ErlangOTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#ErlangOTP</a> .(I have spent some time with <a href="https://fantastic.earth/tags/commonlisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#commonlisp</a>, <a href="https://fantastic.earth/tags/clojure" class="mention hashtag" rel="nofollow noopener" target="_blank">#clojure</a>, <a href="https://fantastic.earth/tags/java" class="mention hashtag" rel="nofollow noopener" target="_blank">#java</a>, <a href="https://fantastic.earth/tags/rakulang" class="mention hashtag" rel="nofollow noopener" target="_blank">#rakulang</a> so these are not listed.)

Stefano MarinelliOnce again today, <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> and <a href="https://mastodon.bsd.cafe/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ZFS</a> saved a setup. Suddenly, a colleague realized that a database was acting up - probably some massive operation had deleted something. The machine takes snapshots every 15 minutes and keeps them for a few hours, then one a day and keeps those for days. To make a long story short, the July 4th dump still had the correct data. To get there, we just had to clone all the snapshots (going back day by day) and test them.Snapshots are one of the best inventions since sliced bread.<a href="https://mastodon.bsd.cafe/tags/RunBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#RunBSD</a> <a href="https://mastodon.bsd.cafe/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a>

Rob 💚My recent post about an <a href="https://social.lol/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a> bug generated some really interesting conversation. I've tried to summarise and respond to some of it. Phew!<a href="https://despairlabs.com/blog/posts/2025-07-13-an-openzfs-bug-and-the-humans-that-made-it-comments/" rel="nofollow noopener" translate="no" target="_blank">https://despairlabs.com/blog/posts/2025-07-13-an-openzfs-bug-and-the-humans-that-made-it-comments/</a>

Rob 💚A few weeks ago I fixed a bug in <a href="https://social.lol/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a> and I can't stop thinking about it.<a href="https://despairlabs.com/blog/posts/2025-07-10-an-openzfs-bug-and-the-humans-that-made-it/" rel="nofollow noopener" translate="no" target="_blank">https://despairlabs.com/blog/posts/2025-07-10-an-openzfs-bug-and-the-humans-that-made-it/</a>

Jim Salter<a href="https://bsd.network/@dvl" class="u-url mention" rel="nofollow noopener" target="_blank">@dvl</a> I found <a href="https://fosstodon.org/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a> bookmarks *fiendishly* difficult to wrap my head around for a long time, so here's my best attempt at a short and sweet explanation: A bookmark, unlike a snapshot, doesn't preserve all blocks active at a certain point in time: it merely notes the actual point in time. You can use a bookmark as a replication SOURCE, and as long as the TARGET has a snapshot taken at the exact time of the bookmark, that is sufficient basis for incremental replication.

Avid AndrewAt first glance, ZFS snapshots, bookmarks, and checkpoints may seem similar. Let's explore what these features are, how they differ, and example use cases for each: <a href="https://avidandrew.com/zfs-snapshots-bookmarks-checkpoints.html" rel="nofollow noopener" translate="no" target="_blank">https://avidandrew.com/zfs-snapshots-bookmarks-checkpoints.html</a><a href="https://universeodon.com/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://universeodon.com/tags/zfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#zfs</a> <a href="https://universeodon.com/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#foss</a> <a href="https://universeodon.com/tags/openzfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#openzfs</a> <a href="https://universeodon.com/tags/storage" class="mention hashtag" rel="nofollow noopener" target="_blank">#storage</a> <a href="https://universeodon.com/tags/freesoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#freesoftware</a> <a href="https://universeodon.com/tags/nas" class="mention hashtag" rel="nofollow noopener" target="_blank">#nas</a> <a href="https://universeodon.com/tags/TrueNas" class="mention hashtag" rel="nofollow noopener" target="_blank">#TrueNas</a> <a href="https://universeodon.com/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://universeodon.com/tags/freebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#freebsd</a> <a href="https://universeodon.com/tags/selfhost" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhost</a> <a href="https://universeodon.com/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosted</a> <a href="https://universeodon.com/tags/ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#ubuntu</a>

Graham Perrin<a href="https://mastodon.bsd.cafe/@paul" class="u-url mention" rel="nofollow noopener" target="_blank">@paul</a> <a href="https://telegrafverket.cc/@linus" class="u-url mention" rel="nofollow noopener" target="_blank">@linus</a> <a href="https://mastodon.bsd.cafe/@stefano" class="u-url mention" rel="nofollow noopener" target="_blank">@stefano</a> <a href="https://fosstodon.org/@whynothugo" class="u-url mention" rel="nofollow noopener" target="_blank">@whynothugo</a> I chose Ubuntu (for KDE Plasma) because the installer provides root-on-ZFS. With that base, I have not yet figured out which of these will be the simplest way forward: ― bemgr ― zectl ― ZFSBootMenu.<<a href="https://gist.github.com/grahamperrin/a65f5d819a6a8c54aff6079f63db33f6#user-content-management-of-zfs-boot-environments" rel="nofollow noopener" translate="no" target="_blank">https://gist.github.com/grahamperrin/a65f5d819a6a8c54aff6079f63db33f6#user-content-management-of-zfs-boot-environments</a>>I see verbose guides, the verbosity creates a sense of complication. I'd like the simplest possible guide to getting started, with any of the three options, where the boot environment layout/structure is predetermined by the installer for Ubuntu.TIA<a href="https://mastodon.bsd.cafe/tags/rootonzfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#rootonzfs</a> <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.bsd.cafe/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a> <a href="https://mastodon.bsd.cafe/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ZFS</a> <a href="https://mastodon.bsd.cafe/tags/bemgr" class="mention hashtag" rel="nofollow noopener" target="_blank">#bemgr</a> <a href="https://mastodon.bsd.cafe/tags/zectl" class="mention hashtag" rel="nofollow noopener" target="_blank">#zectl</a> <a href="https://mastodon.bsd.cafe/tags/ZFSBootMenu" class="mention hashtag" rel="nofollow noopener" target="_blank">#ZFSBootMenu</a>

Rob 💚Sometime the ask lands in the brain on just the right angle at just the right moment.<a href="https://github.com/openzfs/zfs/pull/17426" rel="nofollow noopener" translate="no" target="_blank">https://github.com/openzfs/zfs/pull/17426</a><a href="https://bsd.network/@dexter" class="u-url mention" rel="nofollow noopener" target="_blank">@dexter</a> <a href="https://social.lol/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a>

Stefano Marinellirsync -avhHPx --delete source/dir destdir/Me: Oh no! The correct source was source/ - not source/dir - and now all of destdir's contents (4.6 TB) have been deleted! Me, two seconds later: Oh well. `zfs rollback datapool/dataset@lastSnap`rsync -avhHPx --delete source/ destdir/Thank you, ZFS.<a href="https://mastodon.bsd.cafe/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ZFS</a> <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> <a href="https://mastodon.bsd.cafe/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a>

Rob 💚Last year at <a href="https://social.lol/tags/BSDCan" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSDCan</a> I excitedly told everyone how I was gonna make `fsync()` in <a href="https://social.lol/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a> successfully fail when necessary, instead of failing successfully.<a href="https://despairlabs.com/presentations/openzfs-fsync-zil/" rel="nofollow noopener" translate="no" target="_blank">https://despairlabs.com/presentations/openzfs-fsync-zil/</a>After a year of work, and rework, and getting all the pieces into place, an hour ago I finally posted the PR that should pull it all together and make it go 😅<a href="https://github.com/openzfs/zfs/pull/17398" rel="nofollow noopener" translate="no" target="_blank">https://github.com/openzfs/zfs/pull/17398</a>

FreeBSD FoundationTake your FreeBSD ZFS game to the next level! 🔧💾In our latest blog, Benedict Reuschling dives into automated ZFS snapshots with Sanoid — a powerful tool to schedule, manage, and prune snapshots effortlessly on FreeBSD. Learn how to set up snapshot policies to keep your data safe.📦 Bonus: Includes a ready-to-go Ansible playbook!👉 Read now: <a href="https://freebsdfoundation.org/blog/zfs-automatic-snapshots-with-sanoid-on-freebsd/" rel="nofollow noopener" translate="no" target="_blank">https://freebsdfoundation.org/blog/zfs-automatic-snapshots-with-sanoid-on-freebsd/</a> <a href="https://mastodon.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> <a href="https://mastodon.social/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ZFS</a> <a href="https://mastodon.social/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a> <a href="https://mastodon.social/tags/SysAdmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#SysAdmin</a> <a href="https://mastodon.social/tags/Sanoid" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sanoid</a> <a href="https://mastodon.social/tags/Snapshots" class="mention hashtag" rel="nofollow noopener" target="_blank">#Snapshots</a> <a href="https://mastodon.social/tags/DataRecovery" class="mention hashtag" rel="nofollow noopener" target="_blank">#DataRecovery</a> <a href="https://mastodon.social/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ansible</a>

TomAoki<a href="https://social.lol/@robn" class="u-url mention" rel="nofollow noopener" target="_blank">@robn</a> I don't have GitHub account, so replying here.Not sure it's trivial enough or not, but wouldn't it nice if this deletions are done in 3 steps, like below in single commit per step? Step1: Implement new SYSCTL macro to create alias of any sysctl/tunable node (i.e., SYSCTL_ALIAS). Step2: Use it for to-be-removed nodes. Step3: Actually remove now-actually-alias old nodes.This kind of renaming could happen in the future. So having clear way like Step1: Add new node as usual and make existing to-be-deleted ones alias of the new one. Step2: In next or later *.0-Release, search and delete aliases to avoid POLA violations within single stable branch.This way, the 2nd step would become trivial (look for SYSCTL_ALIAS).<a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> <a href="https://mastodon.bsd.cafe/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a> <a href="https://mastodon.bsd.cafe/tags/SYSCTL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SYSCTL</a>

Rob 💚Ok so, when <a href="https://social.lol/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> switched <a href="https://social.lol/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ZFS</a> to <a href="https://social.lol/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a> in 13.0, a lot of sysctl knobs got new names, and the old ones retained as aliases. I now want to get rid of them, but I don't know how deep they go in code, tools, documentation and oral histories.Since I'm here for code cleanup and not to ruin anyone's day, I could use an assist from old FreeBSD+ZFS boffins. Please review <a href="https://github.com/openzfs/zfs/pull/17375" rel="nofollow noopener" translate="no" target="_blank">https://github.com/openzfs/zfs/pull/17375</a> and let me know if there are any that would be bad to remove, and why. Thank you!

9to5Linux<a href="https://floss.social/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a> 2.3.2 is out now with support for <a href="https://floss.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> kernel 6.14 <a href="https://github.com/openzfs/zfs/releases/tag/zfs-2.3.2" rel="nofollow noopener" translate="no" target="_blank">https://github.com/openzfs/zfs/releases/tag/zfs-2.3.2</a><a href="https://floss.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://floss.social/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeSoftware</a>

Kevin Karhan :verified:<a href="https://chaos.social/@txt_file" class="u-url mention" rel="nofollow noopener" target="_blank">@txt_file</a> yeah, I think <a href="https://infosec.space/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a> should be more transparent about the requirements and limitations of <a href="https://infosec.space/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ZFS</a>.<ul><li>I think for average normies, <a href="https://infosec.space/tags/btrfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#btrfs</a> is a good, abeit <a href="https://infosec.space/tags/Backups" class="mention hashtag" rel="nofollow noopener" target="_blank">#Backups</a> are clearly essential ffs!</li></ul>

DoerkOpenZFS is great and it comes with awesome features. But for newbies or even users who don’t use all the features every day, it can be sometimes a little bit overwhelming. The FreeBSD foundation has generously created an OpenZFS cheat cheat covering all the basic stuff that is important in daily use. Great work and worth sharing!<a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> <a href="https://mastodon.bsd.cafe/tags/openzfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#openzfs</a> <a href="https://mastodon.bsd.cafe/tags/zfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#zfs</a> <a href="https://mastodon.bsd.cafe/tags/cheatsheet" class="mention hashtag" rel="nofollow noopener" target="_blank">#cheatsheet</a><a href="https://freebsdfoundation.org/blog/openzfs-cheat-sheet/" rel="nofollow noopener" translate="no" target="_blank">https://freebsdfoundation.org/blog/openzfs-cheat-sheet/</a>

Jan Lehnardt :couchdb:I absofuckinglutely love ZFS and every time I mess with it, I come back delighted. Today I doubled the sizes of my NAS backup pool to 8TB and my storage pool to 32TB. It took less than a minute 😎<a href="https://narrativ.es/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a>

Rob 💚Alas, I won’t be at <a href="https://social.lol/tags/BSDCan" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSDCan</a> this year.Travelling is a big financial and mental cost. I overspent last year on BSDCan and AsiaBSDCon and so missed the <a href="https://social.lol/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a> Dev Summit. So I’m saving both to make sure I can get there this year.It’s unclear if I will make it though. Managing an anxiety disorder is about finding the stable and predictable paths through the world. The USA seems uninterested in stable and predictable right now, and I don’t yet know if I can overcome it, or if I even want to.

Rob 💚Here's me rambling about libzfs and libzfs_core, the weird libraries that power the <a href="https://social.lol/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a> CLI tools and very little else. Along the way, we look at some of the other inadequate OpenZFS programming options that exist, the chats we've had about them the OpenZFS Production User Calls and the very first steps I'm taking to try and make sense of this whole mess.With thanks to <a href="https://mastodon.bsd.cafe/@bsdfund" class="u-url mention" rel="nofollow noopener" target="_blank">@bsdfund</a>. Turns out that if you buy me some snacks I'll write whatever you want! 🤑<a href="https://despairlabs.com/blog/posts/2025-03-12-we-should-improve-libzfs-somewhat/" rel="nofollow noopener" translate="no" target="_blank">https://despairlabs.com/blog/posts/2025-03-12-we-should-improve-libzfs-somewhat/</a>

Recent searches

Search options

Administered by:

Server stats:

#OpenZFS