Asklemmy

43870 readers

1500 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
[email protected]: a community for finding communities

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago

MODERATORS

[email protected]

Is RAID still needed? (programming.dev)

submitted 7 months ago by [email protected] to c/[email protected]

67 comments fedilink hide all child comments

Me and my friend were discussing this the other day about how he said RAID is no longer needed. He said it was due to how big SSDs have gotten and that apparently you can replace sectors within them if a problem occurs which is why having an array is not needed.

I replied with the fact that arrays allow for redundancy that create a faster uptime if there are issues and drive needs to be replaced. And depending on what you are doing, that is more valuable than just doing the new thing. Especially because RAID allows redundancy that can replicate lost data if needed depending on the configuration.

What do you all think?

you are viewing a single comment's thread
view the rest of the comments

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

a dedicated battery to keep the I/O buffer alive in case of hardware failure

Unless I'm misunderstanding, that sounds like you're worried about the write hole, which RAIDZ doesn't have

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

It's mostly a matter of making sure any writes that are interrupted part way through (power failure, etc) are kept alive until the issue has been resolved. The raid controller caches everything until the write is complete.

It's not so much about disks being out of sync, but more about preventing data loss.

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

RAIDZ is copy-on-write, and will notice and correct parity discrepancies if interrupted partway through. Doesn't help if you don't get at least one copy of the data written, but I'd take RAIDZ and a UPS over a hardware raid any day

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

And at the scale I'm operating, I'll take hardware raid over raidz any day. I did some performance benchmarking when initially building these clusters, and beegfs really doesn't like raidz.

I use raidz at home, though.

[–] [email protected] 1 points 7 months ago

That's fair. My biggest concern with a hardware raid is the risk having trouble finding compatible hardware if/when a controller dies, but I expect that's not really an issue at larger scale; you probably buy hardware in bulk and have replacements on hand