r/zfs • • 19h ago

Would you use a TUI?

Thumbnail
gallery
30 Upvotes

As a big fan of TUIs, I was a little bummed that there aren't any maintained TUIs for ZFS. I started building one (that is not public rn, but would be GPL-3+ written in Go. The general idea is that anything that can be done through the command line should be able to be completed through the TUI, along with additional functionality.

Features:

  • Unprivileged RO mode, with an opt-in RW mode

  • Full management of datasets, snapshots, volumes, i properties and permissions management for datasets, etc etc

  • ARC view and management, along with I/O view/management

  • The ability to save "Plans" and return to them later. e.g: you want to mock up a new dataset, but want to return to it later. You can save it as a "Plan" to return to later. Anyone can create plans, including unprivileged users, so this opens the door for say an admin to review and approve after submission

  • Any write action shows a confirmation page with the exact ZFS command run

Planned:

  • Pool management, including re-silvering, attaching and detaching disks, etc

  • Send/receive support

  • FreeBSD support

  • Support for other filesystems (BTRFS, XFS, EXT4, etc)

Yes, the project is being written with AI support.

Edit: https://github.com/nuclear-gumbo/fstui


r/zfs • • 4h ago

Yay! Somehow Microsoft decided that the best time to try again to force me to Win11 was 1am last night when my RAIDz3 was expanding to add a few more drives.

Thumbnail
reddit.com
0 Upvotes

r/zfs • • 1d ago

Is OpenZFS using the OSS Scanner by anthropic to help find bugs?

0 Upvotes

Anthropic has a project to help open source project find and fix bugs (not GlassWing) and OpenZFS is clearly the kind of important, infrastructure open-source project being targeted for help.

Does anybody know if OpenZFS is taking advantage of this?


r/zfs • • 1d ago

Async near real time mirror PR

0 Upvotes

Something I vibe coded and testing out due to not being able to afford more ssds 🤣

Let me know if you’re interested, think I’m mad etc

Thick skin engaged, go!

https://github.com/openzfs/zfs/discussions/19890


r/zfs • • 2d ago

To sudo or not to sudo?

5 Upvotes

Unix permissions are not my strong suit. So when it comes to creating pools and datasets, I am totally lost. When should we create a pool as sudo vs without? When should we create datasets with sudo and without?


r/zfs • • 7d ago

zfs bookmark missing -r :( now I fvcked up

12 Upvotes

I am using OpenZFS 2.3 and have been taking multiple snapshots of my root-on-ZFS pools and sending them to external drives for backup.

As the host SSD was running low on storage, I read the documentation about bookmarks for the first time and created some for older snapshots of said pools, so I could destroy the oldest snapshots and continue performing incremental send streams.

As mentioned, it was my first time using bookmarks, and when I started reading the documentation, I was thinking about the importance of having some -r option, like with snapshots, but forgot about it while reading. Anyway, I created the bookmarks, destroyed the old snapshots, and had space again (I had like 5 GB left on a 4 TB drive, with no quotas/reservations etc. — only the default slop space was left). I created a new snapshot and wanted to incrementally send the latest snapshot to the backup drives, only to receive some funny error: Error: multiple snapshots cannot be sent from a bookmark.

Then it hit me. Fvvvvvvvck.

zfs list -t snapshot,bookmark shows: I only have a bookmark of the pool — not its children.

So I went back to the ZFS documentation and noticed that bookmark -r was only recently added to the master branch. Welp, that's maybe why my brain shut off when I didn't see it in the v2.3 documentation.

Consulted some LLMs to see if I could fix the situation, but it seems there is no realistic option. I guess I'll have to break the chain and send a new backup to the drives, losing the incremental history :(

On the one hand, I'm kinda frustrated because I've spent my entire weekend since Friday doing nothing but ZFS-related stuff, with no other use of the machine. On the other hand, I'm really glad I've learned this lesson now, while it's non-critical.

tl;dr:

  1. zfs bookmark -r is only available in future releases (not up until v2.4)

  2. Never use zfs send -i/-I from a bookmark (even if theoretically possible), but rather from a snapshot, circumventing the lack ofzfs bookmark -r and the lack ofzfs send -Rfor bookmarks (Error: multiple snapshots cannot be sent from a bookmark)

If anybody knows a way to fix my issue using the existing snapshots on the external drive and the pool#bookmark (no child bookmarks for the pool's datasets) on my internal drive, I'd be glad to hear it.

But first: for the next 24 hours, I'm taking a break from managing ZFS 🐼


r/zfs • • 7d ago

ZFS on Fedora 45?

11 Upvotes

I tried to upgrade to Fedora 45, but there's no "45" folder at the ZFS on Linux download site.

Any news on this front? I'll admit that seeing links like this when I search for ZFS Fedora 45 is concerning.


r/zfs • • 7d ago

Long boot, zfs-impoort-cache.service, 1min 33sec, caused by ongoing scrub?

5 Upvotes

[SOLVED]

Had a long bootup today on LMDE7, basically Debian from a base perspective, rebooted to the same results.

ran systemd-analyze plot > plot.svg which fingered zfs-impoort-cache.service as the culprit.

https://postimg.cc/2V3FmL5t

was concerned about my pools for a moment but digging around I found that apparently a scheduled scrub started last night and I interrupted it with a shutdown.

Its a 3 rust disk z1 pool and will take a while to complete.

Is this expected behavior that will go away once the scrub is complete? I do not know that I have ever interrupted a scrub, but it appears to just start back where it left off at

dad@RatRod:~$ zpool status
  pool: lagoon
 state: ONLINE
  scan: scrub in progress since Sun Nov  8 00:24:01 2026
	1.86T / 1.97T scanned at 1.69G/s, 410G / 1.97T issued at 374M/s
	0B repaired, 20.35% done, 01:13:16 to go
config:

	NAME                        STATE     READ WRITE CKSUM
	lagoon                      ONLINE       0     0     0
	  raidz1-0                  ONLINE       0     0     0
	    wwn-0x5000cca260d7dbfb  ONLINE       0     0     0
	    wwn-0x5000cca260dba420  ONLINE       0     0     0
	    wwn-0x5000cca261c92058  ONLINE       0     0     0

errors: No known data errors

  pool: suwannee
 state: ONLINE
  scan: scrub repaired 0B in 00:03:04 with 0 errors on Sun Nov  8 15:58:48 2026
config:

	NAME                         STATE     READ WRITE CKSUM
	suwannee                     ONLINE       0     0     0
	  nvme-eui.0025384931406ac8  ONLINE       0     0     0

errors: No known data errors

Edit once the scrub was complete bootup went back to normal. https://postimg.cc/DW0fCGPQ


r/zfs • • 8d ago

Is there a study on NVMe SSD wear (write amplification) comparing ext4, Btrfs, and ZFS with LUKS2?

Thumbnail reddit.com
18 Upvotes

r/zfs • • 10d ago

OpenZFS on Windows 2.4.4rc8 AnyRaid

16 Upvotes

https://github.com/openzfsonwindows/openzfs/releases

  • Debug build of the new AnyRAID feature for those who would like to try. (Oh heh blast, I didnt tag it, so it says 2.4.1, but it is 2.4.4 :). ) Anyraid works on tiles so you can combine any disk sizes and you can remove disks.

  • I see Anyraid as the most universal raid type. It can replace mirror and raid-Z in future, now in OpenZFS master and in OpenZFS on Windows 2.4.4 pre release for first tests

Only for tests, not backward compatible with older OpenZFS
currently only mirror, not yet

  • raidz-Parity (anyraidz)

  • Rebalancing of Tiles on newly added disks

  • Vdev-Contraction


r/zfs • • 12d ago

ZFS AnyRaid VDEVs have just been approved and shipped

Thumbnail
github.com
57 Upvotes

r/zfs • • 11d ago

Remove files

0 Upvotes

I had a trueness server with ZFS. I want to remove my files from the ZFS is there some way to just get in the directory and get the files out or how should I go about getting them?


r/zfs • • 12d ago

sync=disabled is a free write barrier

22 Upvotes

fsync promises two things, durability and ordering, and I only need ordering.
ext4 gives both or neither: every fsync commits the journal and flushes the disk cache.
ZFS with sync=disabled gives ordering alone: transaction groups land in order, and a crash loses the last tens of seconds, not a database.
My two HDDs are 2.7% busy instead of 13%, and a write takes 2 ms instead of 16.

https://blog.dfb.sh/blog/zfs-fsync/


r/zfs • • 14d ago

zark: bare-metal backup and recovery for Ubuntu on encrypted ZFS, built on raw sends, per-drive bookmarks and read-back (I'm the author)

14 Upvotes

Disclosure: I'm the author of zark, free software (Apache 2.0). I'd like feedback from people who know ZFS better than a distro installer does.

What it does: it backs up an Ubuntu system on encrypted ZFS to an external drive, still encrypted, and rebuilds it on a new disk from a live USB, booting with Secure Boot on the stock Ubuntu boot chain. Supported: Ubuntu 24.04 and 26.04 LTS, installed with the installer's encrypted ZFS layout, Secure Boot on.

Design points that matter to this sub:

  • Raw sends. A raw zfs send carries the encrypted blocks as they are, so the backup drive holds ciphertext and never needs the keys. I first planned to give the drive its own encryption; the raw send is simpler and more efficient.

  • Own replication instead of syncoid. Each run takes one backup point of every dataset and sends from the newest snapshot the drive holds. When the source has already pruned that snapshot, a bookmark kept for that drive still marks where the drive stands. A drive can stay unplugged for months and sanoid's pruning no longer cuts it loose.

  • No destruction without a question. Nothing on a drive is destroyed without asking first, and the question comes before the transfer starts.

  • Read back before unplugging. Every backup is checked on the drive before zark says it is safe to disconnect it.

  • An honest verdict. BACKUP COMPLETED only when every expected dataset reached the new point. Otherwise BACKUP INCOMPLETE, exit code 1, the drive's last backup date is not recorded, and a table shows what happened to each dataset.

  • zark prune reclaims space in the source or on a drive under zark's own rules, so nobody has to reach for a % range by hand.

Why I wrote my own replication: in September I ran a zfs destroy with a % range on my home dataset to free space in an almost full pool. It also took the monthly snapshots in between, which one of my drives still shared with the laptop. Thirteen days later sanoid pruned the last common snapshot. After that, /home could not be sent incrementally to that drive. syncoid refused it, and zark 1.0.12 printed a warning, then BACKUP COMPLETED, and recorded the date. Every dataset on the drive was current except /home, a month old. Nothing was lost, but a backup tool exists to be believed, so I rebuilt it as 2.0.

Self-test: zark selftest checks that your machine's ZFS, kernel and tools behave the way zark relies on. Each release publishes the results from my test machine (certificates/ in the repo). zark selftest status tells you whether those results cover your kernel and OpenZFS version, and zark selftest report prints a link to share yours. I would like to collect results from other OpenZFS and kernel combinations: https://github.com/juanmitaboada/zark/issues/2

The question I'd like answered: what would you expect a verification step after a raw send to prove that I'm not checking? And if you use USB-SATA bridges for backup drives, I'm collecting which bridge chips behave and which do not: https://github.com/juanmitaboada/zark/issues/3

Numbers from my own use: a daily backup of my laptop takes about two minutes. On the test laptop, a full recovery from a live USB reached RECOVERY COMPLETE in 3m10s and in 3m25s; with more data, add the time it takes to copy it. I ran dozens, maybe hundreds, of backups and recoveries while building 2.0 and none failed.

zark partitions disks and destroys pools when you ask it to, so read what it touches first: https://github.com/juanmitaboada/zark#what-zark-touches

Full story, with photos: https://www.juanmitaboada.com/my-laptop-lost-its-disk-three-times-so-i-wrote-zark/
Code and docs: https://github.com/juanmitaboada/zark
Explainer video: https://youtu.be/RW7M9PC5les


r/zfs • • 14d ago

ZFS confusion

5 Upvotes

I've got a GhostBSD system that is using ZFS. I have some Linux installs that do not. I wanted to add ZFS support to them and did so on Devuan and it behaved and didn't import any pools on its own. I installed ZFS on Void Linux though and it automatically imported all of the pools that it could find and then automounted my GhostBSD datasets which caused all kind of havoc with overlapping mountpoints on the various datasets.

I still want Linux to able to mount a dataset but I don't want it to happen automatically. I still need GhostBSD to be able to boot though. I'd ultimately like to just create a separate shared pool between Ghostbsd and Linux. How do I do that without other pools being automounted?


r/zfs • • 15d ago

You will use SMR and be happy! (if you are allowed to own a computer)

Post image
123 Upvotes

Fresh off the "OpenZFS User and Developer Summit 2026" presses - scary WD guy says industry is moving entirely towards host managed SMR HAMR drives and CMR is going away. "Host managed" is going to be implied when talking about SMR and "drive managed" is not going to be a thing. No CMR areas either - heads can't support both.

There's already work underway to make ZFS support this, but at least from what I understood, you're going to need some sort of additional non-SMR vdev (special) to store bootstrapping things on.

All of you who wanted 100M AI generated pictures of cat-octopus hybrids in the clouds - this is your fault!

Two back to back presentations about this. Overall, very interesting.

https://youtu.be/s1L1VxASNfw?t=23503


r/zfs • • 16d ago

changing pool/keystore-ZVOL property's (copies=n) on live/online System: Any risks?

7 Upvotes

Running root on ZFS 5000 with ZFS aes-256-gcm + luks keystore via standard Ubuntu24.04.1 LTS first release (2024) installer, on a laptop with 32GB non-ECC. All Pools/Datasets are set to copies=1.

Running 2x external HDD luks container + ZFS pool inside for Backup, BUT so far I use "regular" file transfers into the decrypted/mounted container for backups - I do not use snapshot with 'zfs send' so far.

I get more concerned for bit flip and SHTF scenarios these days and was thinking "whats the best I can do with non-ECC?"

I found academic E2ZFS approaches but no practical software to try, or settings that allows redundancy in RAM by openZFS.

openZFS docu shows theres a 'copies' feature for the pool/dataset: So I was thinking while it does not fix my need for redundancy in RAM, its atleast a minor tweak.

My Q: Can I safely change the property

'zfs set copies=3 rpool/keystore'

'zfs set copies=3 bpool'

on the online System? (These datasets are not encrypted, the limit of copies=2 does not apply)

Ive read the copies wont be written right away, so I kinda need to trigger somehow to do it: for bpool (kernel, initramfs) I see no issue: But for the keystore?

Im not confident to actually continue. Consulting some LLM did not inspire confidence either. Would appreciate your input! Ty


r/zfs • • 17d ago

ZFS errors. Is cause HBA, cable, SAS drives?

6 Upvotes

Doing ZFS pool I got this error:

status: One or more devices has experienced an unrecoverable error.  An
        attempt was made to correct the error.  Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
        using 'zpool clear' or replace the device with 'zpool replace'.
   see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-9P

And when I investigated, I saw:

# for d in /dev/sd[a-h]; do
  echo "===== $d ====="
  smartctl -x "$d" 2>/dev/null | grep -Ei \
  'Non-medium error|grown defect|Loss of DWORD|Phy reset problem|SMART Health'
done
===== /dev/sda =====
SMART Health Status: OK
Elements in grown defect list: 0
Non-medium error count:    16223
    Loss of DWORD synchronization count = 73
    Phy reset problem count = 0
    Loss of DWORD synchronization count = 11
    Phy reset problem count = 0
===== /dev/sdb =====
SMART Health Status: OK
Elements in grown defect list: 0
Non-medium error count:    15717
    Loss of DWORD synchronization count = 11
    Phy reset problem count = 0
    Loss of DWORD synchronization count = 13
    Phy reset problem count = 0
===== /dev/sdc =====
SMART Health Status: OK
Elements in grown defect list: 55
Non-medium error count:      461
    reason: loss of dword synchronization
    Loss of DWORD synchronization count = 137
    Phy reset problem count = 0
    Loss of DWORD synchronization count = 0
    Phy reset problem count = 0
===== /dev/sdd =====
SMART Health Status: OK
Elements in grown defect list: 9
Non-medium error count:      300
    attached reason: loss of dword synchronization
    Loss of DWORD synchronization count = 0
    Phy reset problem count = 0
    Loss of DWORD synchronization count = 0
    Phy reset problem count = 0
===== /dev/sde =====
SMART Health Status: OK
Elements in grown defect list: 0
Non-medium error count:   104155
    Loss of DWORD synchronization count = 14
    Phy reset problem count = 0
    Loss of DWORD synchronization count = 0
    Phy reset problem count = 0
===== /dev/sdf =====
SMART Health Status: OK
Elements in grown defect list: 0
Non-medium error count:      513
    attached reason: loss of dword synchronization
    Loss of DWORD synchronization count = 2
    Phy reset problem count = 0
    Loss of DWORD synchronization count = 0
    Phy reset problem count = 0
===== /dev/sdg =====
SMART Health Status: OK
Elements in grown defect list: 0
Non-medium error count:    16161
    Loss of DWORD synchronization count = 9
    Phy reset problem count = 0
    Loss of DWORD synchronization count = 6
    Phy reset problem count = 0
===== /dev/sdh =====
SMART Health Status: OK
Elements in grown defect list: 7
Non-medium error count:      879
    Loss of DWORD synchronization count = 0
    Phy reset problem count = 0
    Loss of DWORD synchronization count = 0
    Phy reset problem count = 0

Are errors across all 8 disks likely due to HBA or connector. The HBA is LSI and connecting to drives via 2 SAS breakout cables which do look flimsy.

The other thing is, I thought the drives I bought were new from a reputable online store, but on investigation, I saw it was a reseller operating on the store and the drives are around 10 years old with 6 years of operational time. However, as these are non-medium errors, I wonder if less likely to be drives than the HBA/cables.

Could it even be PSU as that is old.

Anyone had similar errors before and found a way to fix?


r/zfs • • 17d ago

Are 8GB of ram enough for ZFS?

20 Upvotes

I did a quick research in the sub history before posting, but surprisingly I didn't find a related post.

My laptop has 8gb ram ddr4 and 240gb of ssd nmve. I read that ZFS is memory intensive, but it can be usable if I adjust some values like arc cache and turn off deduplication.

What's your take on this?

PS bit rot prevention is important for me, so, with such lowered stats can I actually prevent data loss? Of course I would keep 2 copies for each important file and do some check and scrum every now and then.

I'm using Debian right now, but I can change distro if it accomodates zfs better.


r/zfs • • 17d ago

Webcraft Integration in napp-it 4ai ZFS web-gui and napp-it cs-team add on

1 Upvotes

Announcement: Webcraft Integration in napp-it 4ai ZFS web-gui and napp-it cs-team add on
(OpenSource rebuilds of Creative Suite, Office Suite, Solid CAD and others)

https://hardforum.com/threads/openzfs-nas-bsd-illumos-linux-osx-solaris-windows-storage-spaces-with-napp-it-web-gui.1573272/page-222#post-1046399261

 


r/zfs • • 18d ago

After 12 years I finally got my data back from a pool that wouldn't open - led to a small read-only POC tool

105 Upvotes

this is mostly a "don't give up on your old drives" post, maybe it helps someone who has a dead pool sitting in a drawer like I did.

oct 2014, my home NAS (gentoo, zfs 0.6.3, mirror on LUKS) had a kernel panic and afterwards rpool/home just wouldn't open anymore: can't open objset for rpool/home. I tried everything people suggested in openzfs #2831 back then, -F, -X, -T, patched txgs, looping over every txg for weeks... best I got was "cannot iterate filesystems". a recovery company gave up too, so the drives went into the drawer.

this year I tried again with current openzfs master (a zdb crash on exactly that pool had just been fixed). zdb could finally open the pool and showed what was wrong: everything was fine except one single block, the objset block of home. both copies overwritten, on both disks. one block, 360 GB unreachable, and every older txg pointed to the same broken block, so no rewind could ever have worked.

but the data underneath was still there. so I scanned the raw disk for the dataset's dnode tree, checked every piece against the checksums zfs stores anyway, and found a complete state from ~16 hours before the crash. a few days ago my photos from 2014 opened again, byte for byte. pretty emotional tbh.

I put what I hacked together into a small read-only tool, more a proof of concept than a product: https://github.com/simonbuehler/zfs-salvage

it runs from an ubuntu live usb with a little web UI, works for single disks, mirrors and stripes, and can also go back to older states for deleted files or destroyed datasets. no raidz yet, no zstd, no native encryption.

two things I wish someone had told me back then:

  • never open the disks writable, not even for a "readonly" import. my old attempts kept writing new uberblocks. cryptsetup open --readonly / blockdev --setro, or just work on images

  • try zdb from current master first, even if it can't import it can tell you which block is actually broken

if you're stuck with a pool like that, or have a raidz one that won't import, feel free to try it or just ask


r/zfs • • 19d ago

[Announce] zfsbootmenu-installer 1.1.0: Root-on-ZFS AND Secure Boot installation of ANY(*) Debian- and Ubuntu-derived distro! Just give it the distro's Live .iso file!

Thumbnail
github.com
16 Upvotes

r/zfs • • 22d ago

Can I create a Storage Pool at my RAID's ODs?

Thumbnail reddit.com
3 Upvotes

r/zfs • • 23d ago Heartwarming

Windows on ZFS using OpenZFS on Windows.

50 Upvotes

Short video showing the progress of OpenZFS on Windows

https://youtu.be/yPWdl38wfE4

🧙‍♂️ Going on an adventure: booting Windows from a ZFS root 💾

Windows 10 booting to a desktop with its C: drive on a ZFS pool, on OpenZFS on Windows. It's a proof of concept (very much held together with duct tape 🩹), so it's not ready for public use. This is the story of the crashes along the way and how it finally came up.