26
submitted 22 hours ago* (last edited 12 hours ago) by CorrectAlias@piefed.blahaj.zone to c/selfhosted@lemmy.world

I currently have a secondary pool (with raidz2) that I was originally going to use for my important documents, such as storage for Paperless-ngx, as raidz offers corruption detection and repair. The pool is encrypted.

However, I'm concerned about rebuild times (it's a pool of 4 22TB drives). Is btrfs a better choice for this use case, or should I just go with raidz like I originally planned?

Edit: I should have mentioned that I already have 4-3-2 backups configured - I'm primarily interested in the "self-healing" aspect of ZFS so that I don't have to recover from backups unless necessary, and to resolve corruption on the fly without me having to notice that a file is corrupt.

you are viewing a single comment's thread
view the rest of the comments
[-] tychosmoose@piefed.social 3 points 21 hours ago

For your situation I would be more likely to go with a single drive with btrfs and dup for metadata redundancy. Regular snapshots and scrubs.

Use a second drive in the same system with btrfs to store snapshots at wider scheduled intervals. These will be bigger since no CoW on the separate file system. Scheduled scrub here too.

Use a third drive with ext4 as a backup target using a separate backup mechanism.

Use the fourth drive as a spare, or in a separate location as a target to send the backups if you don't already have an off-site solution.

[-] CorrectAlias@piefed.blahaj.zone 1 points 12 hours ago

Interesting idea.

this post was submitted on 25 May 2026
26 points (93.3% liked)

Selfhosted

59472 readers
1414 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS