The pool is about 20 usable TB.

Thats exactly what I wanted to say, yes :D.

High capacity storage pools for enterprises.
Space is at a premium. Saving space should/could equal to better pricing/availability.

well, it depends. if they were dropped just because they are smr and were writing slowly, I think they are fine. but otherwise...

what array system do you use? some raid software, or zfs?

Not necessarily.

The trouble with spinning platters this big is that if a drive fails, it will take a long time to rebuild the array after shoving a new one in there. Sysadmins will be nervous about another failure taking out the whole array until that process is complete, and that can take days. There was some debate a while back on if the industry even wanted spinning platters >20TB. Some are willing to give up density if it means less worry.

I guess Seagate decided to go ahead, anyway, but the industry may be reluctant to buy this.

This hard drive is so big, that astronomers thought it was a planet.

Can't wait to see this bad boy on serverpartdeals in a couple years if I'm still alive

A ZFS Scrub validates all the data in a pool and corrects any errors.

Hello!

I wanna fuck this HDD. To have that much storage on one drive when I currently have ~30TB shared between 20 drives makes me very erect.

Windows Server storage solutions. I took them out of the array and they still weren't recognized in Disk Management so I assume they're shot. It was just weird having 2 fail the same way.

I would assume with arrays they will use a different way to calculate parity or have higher redundancy to compensate the risk.

I get it. But the moment we invoke RAID, or ZFS, we are outside what standard consumers will ever interact with, and therefore into business use cases. Remember, even simple homelab use cases involving docker are well past what the bulk of the world understands.

What is the usecase for drives that large?

I 'only' have 12Tb drives and yet my zfs-pool already needs ~two weeks to scrub it all. With something like this it would literally not be done before the next scheduled scrub.

I'm not in the know of having your own personal data centers so I have no idea. ... But how often is this necessary? Does accessing your own data on your hard drive require a scrub? I just have a 2tb on my home pc. Is the equivalent of a scrub like a disk clean up?

Does it really matter that much if the first copy takes a while though? Only doing it once and you don't even have to do it all in 1 go. Just let it run over the weekend would do though.

And I’ve only ever had WD hard drives and sandisk flash drives die on me

Maybe it's confirmation bias but almost all memory that failed on me has been sandisk-flash storage. Zhe only exception being a corsair ssd which failed after 3 yrs as the main laptop drive + another 3 as a server boot and log-drive.

twenty!?

You usually scrub you pool about once a month, but there are no hard rules on that. The main problem with scrubbing is, that it puts a heavy load on the pool, slowing it down.

Accessing the data does not need a scrub, it is only a routine maintenance task.
A scrub is not like a disk cleanup. With a disk cleanup you remove unneeded files and caches, maybe de-fragment as well. A scrub on the other hand validates that the data you stored on the pool is still the same as before. This is primarily to protect from things like bit rot.

There are many ways a drive can degrade. Sectors can become unreadable, random bits can flip, a write can be interrupted by a power outage, etc. Normal file systems like NTFS or ext4 can only handle this in limited ways. Mostly by deleting the corrupted data.

ZFS on the other hand is built using redundant storage. Storing the data spread over multiple drives in a special way allowing it to recover most corruption and even survive the complete failure of a disk. This comes at the cost of losing some capacity however.