106
have you ever successfully broken the zfs to the point where it's not recoverable?
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 01 Sep 2026
106 points (97.3% liked)
linuxmemes
32686 readers
36 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves / tolerates / hates> systemd, and wants to interject for a moment. You can stop now.
5. ๐ฌ๐ง Language/ัะทัะบ/Sprache
- This is primarily an English-speaking community. ๐ฌ๐ง๐ฆ๐บ๐บ๐ธ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. ย
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 3 years ago
MODERATORS
my achievement here is that this is a proper raidz setup with multiple disks and ecc ram
oof
Raidz1 or z2? One of the reasons I went with z2 is because of the "raid5 is dead" thing, argument basically being, drives are so large that if 1 fails, you are statistically almost guaranteed to encounter a read error during the rebuild when you no longer have any redundancy, so double redundancy is a necessity nowadays.
I have a raidz5 array of 8tb drives, one died, replaced it with no issues
Raidz5 doesn't exist, I assume you mean raid5? And you wouldn't know, URE is sometimes silent, and because without parity during a rebuild you would be recalculating the parity bit and assumig every read on the remaining drives is successful. Except the URE rate for drives hasn't gone down to match the increasing size of drives - so for a full 1x read of a large drive, you're statistically at risk to get at least 1 URE.
In short, there is no integrity checking when rebuilding a single redundancy array after a drive failure, so just because a rebuild succeeds, doesn't mean nothing was lost or corrupted. With double redundancy, you will still have single redundancy during a rebuild, so you would be able to detect URE and retry reads or raise an error to the user.
Some articles may make it overblown - you won't lose your whole array, but any files stored in the block that had the URE during rebuild would be lost. And you might not know that it happened.
You can read about it here: https://www.servnetuk.com/insights/ure-is-raid-5-dead
I've seen a calculation somewhere for drive speed, size and scrub frequency where optimal number of extra drives was calculated. On fast storage and with weekly scrubs one extra drive should be mostly fine.
My philosophy is any raid is not really a data contingency solution - it just saves some time when the drive fails.
This is raidz1. Three 4TB NVME drives. I've built this machine as the primary server for services like immich as a fun project that enables me to say that my photo service runs faster than all the commercial stuff and is on ARM64. The downside is that the SoC is not supported by upstream very well so vendor patches had to be applied and there was some instability between that and my shitty electricity supply.