Please update the title to the full title of the article. This is super misleading and makes it sound like the founder doesn’t want this.

Backblaze of course, but we aren’t talking about the probability of seeing a failure, but of one of your disks failing, and more importantly, data loss. A binomial probability distribution is a simplified way to see the scenario.

Let’s pretend all disks have a failure rate of 2% in year one.

If you have 2 disks, your probability of each disk failing is 2%. The first disk in that array is 2%, and the second is 2%. If 2 disks fail in Z1, you lose data. This isn’t a 1% (half) chance, because the failure rate of one disk does not impact the other, however the risk is less than 2%.

So we use a binomial probability distribution to get more accurate, which would be .02 prob in year one with 2 trials, and 2 failures making a cumulative probability of .0004 for data loss.

If you have 6 disks, your probability of each disk failing is also 2%. The first disk in that array is 2%, the second is 2%, so on and so forth. With 6 disk Z2, three must fail to lose data, reducing your risk further (not to .08%, but lower than Z1).

So with a binomial probability distribution, this would be .02 prob with 6 trials, and 3 failures making a cumulative probability of .00015 for data loss.

Thats a significantly smaller risk. The other interesting part is the difference in probability of one disk failing in a 6 disk array than a 2 disk array is not 3x, but is actually barely any difference at all, because the 2% failure rate is independent. And this doesn’t even take into account large disks have a greater failure rate to start.

I’m not saying mirroring two larger disks is a bad idea, just that there are tradeoffs and the risk is much greater.

Hate to be that guy, but those maths aren’t mathing.

Less drives does not equal less chance of multiple failures. The statistical failure rate of one drive has no impact on another. In fact, analysis of Backblaze’s data showed that larger drives were more prone to failure (platter density vs platter count).

Agree, but before any one else takes the time:

https://github.com/search?q=repo%3Ajarnedemeulemeester%2Ffindroid+shuffle&type=code

Function is already in place, just TODO, and a 30 second code scan shows clean, standard code base. Anyone who’s worked on Android and familliar with the layout library could probably do this in a few hours not including set up time.

$20 is still no where close, though. Feature donation is def the way to go.

As someone who runs 3 large arrays with 8TB, 16TB, and 21TB drives respectively, know that:

• RAIDZ1 will cause tons of fear when a disk fails if you’re used to Z2. Don’t change.
• When a disk goes, the larger the disk, the slower the rebuild time, and the more taxing it is on the other disks. With Z1, if another fails during the rebiluild, you’re SOL.

Less disks is simpler, but more disks is safer. 6 disks is the perfect sized array IMO. If you don’t need more space, I’d buy a 2TB hot spare and call it a day. But if space is a concern, Z2 with 4 disks.

Edit: Those three arrays mirror each other in different locations, and the fear was still there when the Z1 had an issue. Mostly due to the headache, but still.

Does Caddy have an OWASP plugin like nginx?

/storage for me.

True, but a 3 year old TV with original firmware would have been pre-adpocalypse. My never-connected LG boots pretty quick when it was last on an HDMI port before turning off.

Maybe give https://nowsci.com/only-sensor a shot? I built the guides/schematics/models for ESPHome devices as a learning experience for myself.

@SkyNTP@lemmy.ml I felt the same way. Now I just keep making new things for it, currently on garage door opener, blinds opener, and may even automate turning on my DIY solder fume extractor.

Hrm, I don’t. Part of the fun is learning how things work, and I’ve heard to many complaints of incompatibilities and lack of updates with Yuno, though I haven’t tried it, so second hand.

It’s so easy to self host! Just watch 14 hours of a talking head!

Fan of FUTO, but can’t recommend this to most people thinking of starting. Needs to be less “scary”.

What formats are the same? Users are /u and @ while communities are /c and !. No overlap to check for. Mastodon is where the confusion comes in.

Ohhhh. My understanding is initial @ in Mastodon is only required for users, and would default to user over community, while leaving off the initial @ would do community. I have not validated that in the source, though.

I don’t follow… Lemmy and Mastodon both require port 443, so a single hostname of lemmy.ml can’t run both. Lemmy and Mastodon handle users the same way, just Mastodon doesn’t have !communities.

That’s not how Lemmy works. Lemmy uses Actor URLs of https://host.tld/u/user which is referenced via @user@host.tld, and communities are https://host.tld/c/community referenced as !community@host.tld. So there is no overlap.

@ex_06@slrpnk.net

!lemmy@lemmy.ml

The Sengled ZigBee RGB or white bulbs work well for me and have tunable white LEDs. They seem to have a good DC/AC conversion. But they do require ZigBee.

Yup. I use one of those micro PCs with 4 network ports as a router, and that’s it.

The ultimate social media scheduling tool, with a bunch of AI

Mmhmm

on a site

https://github.com/jetkvm/kvm/blob/main/LICENSE