this post was submitted on 11 Dec 2023
100 points (87.3% liked)

datahoarder

6763 readers
37 users here now

Who are we?

We are digital librarians. Among us are represented the various reasons to keep data -- legal requirements, competitive requirements, uncertainty of permanence of cloud services, distaste for transmitting your data externally (e.g. government or corporate espionage), cultural and familial archivists, internet collapse preppers, and people who do it themselves so they're sure it's done right. Everyone has their reasons for curating the data they have decided to keep (either forever or For A Damn Long Time). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.

We are one. We are legion. And we're trying really hard not to forget.

-- 5-4-3-2-1-bang from this thread

founded 4 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] TrickDacy@lemmy.world 14 points 11 months ago (4 children)
[–] beerclue@lemmy.world 29 points 11 months ago

It's a data maintenance feature that amends data in storage pools that are incorrect or incomplete. It works on BTRFS volumes or RAID 5/6 storage pools. It's scheduled to run monthly on my NAS. I guess it started now as I upgraded my drives from 4x4TB to 4x18TB.

[–] PixeIOrange@feddit.de 14 points 11 months ago

It scrubs your data

[–] athos77@kbin.social 12 points 11 months ago

I think it's more that they've increased the size of the drive from 10TB to 48TB.

[–] Unforeseen@sh.itjust.works 7 points 11 months ago

When initializing a new array, it's a (usually optional) process of zeroing out the newly added disks. Sometimes it's required as part of calculating parity across the array (redundancy data).