this post was submitted on 16 Mar 2024
260 points (97.1% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

55056 readers
249 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others



Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 11 points 9 months ago (1 children)

All you need is to use ZFS or BTRFS locally to prevent master version bitrot and provide failover/redundancy, manually sync that to a separate "offline" HDD periodically, then setup a simple pi with tailscale + HDD at a family member or friends house, and rclone all your data to it (encrypted) as a cron job every night or week. This performs the function of a cloud provider (offsite backup); alternately, just manually sync the offline HDD once a month.

With this approach you're covered for accidental deletion, hard drive failures, bitrot, ransomware, and fire; possibly many natural disasters, depending how far away the offsite is.

Then you can just keep your most important data E2E encrypted in 1 or 2 cloud storage providers.

[–] [email protected] 2 points 9 months ago (1 children)

Note: zfs/btrfs cannot repair bitrot without redundancy, only detect it. But if redudancy, is repaired automatically (self-healing).

Raid 1/5/6 cannot repair, only detect bitrot, cannot decide which copy good.

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago) (1 children)

I have never seen an implementation of e.g. a mirror that gives up on disagreements of both disks. Repairing/redundnancy is what raid is there for.

Edit: maybe old hardware raid does not check?