Anonymous
10/24/2025, 9:09:49 PM
No.106996868
>>106996532
No clue, I just use regular Windows + Storage Spaces.
For a while I used Windows Server and the more advances Storage Spaces it has ('Storage Spaces Direct' or 'S2D', it's separate to regular Storage Spaces and incompatible with it) to have the scrubbing function. But I read that the scrubbing function is kinda unreliable, it jumps the gun, sometimes it deletes the good copy and copies over the corrupted one. That risk + the fact that despite regular scrubbing it never found a single discrepancy for me in a few years, I decided bitrot was kind of a meme and decided to go back to regular Storage Spaces. The interface is simple and comfy but just werks. Powershell is there if I want to be more granular controls when creating a new Space.
What I like best about it (regular consumer version) is you can have different Spaces across the same disks.
E.g. I make a pool with 4 disks.
I make it a 'Mirror' (kinda like RAID1). But I begin running out of space.
I can of course add a new disk and expand the Space.
But I can, from the same pool i.e. on the same disks, make another Space, this time I make it a Parity (similar to RAID5). It'll make it on the same disks. Then I can move data from the Mirror Space to the Parity Space on the same disks. Once it's done I can delete the Mirror Space off the disks leaving the Parity Space as the only volume.
So I can migrate all my data to a new 'array' but without deleting the data and formatting the disks first. It's a slower but a safer way to do things. I mean of course I have a separate cold backup, but I always feel jittery about deleting the live array and creating a new one, because I'm down to my only backup and it isn't even cold any more because I'm copying its contents to the new array. One thing goes wrong with the backup and poof, everything gone. I don't have to do that when I shuffle the data to a new volume but within the same disks using Storage Space.
No clue, I just use regular Windows + Storage Spaces.
For a while I used Windows Server and the more advances Storage Spaces it has ('Storage Spaces Direct' or 'S2D', it's separate to regular Storage Spaces and incompatible with it) to have the scrubbing function. But I read that the scrubbing function is kinda unreliable, it jumps the gun, sometimes it deletes the good copy and copies over the corrupted one. That risk + the fact that despite regular scrubbing it never found a single discrepancy for me in a few years, I decided bitrot was kind of a meme and decided to go back to regular Storage Spaces. The interface is simple and comfy but just werks. Powershell is there if I want to be more granular controls when creating a new Space.
What I like best about it (regular consumer version) is you can have different Spaces across the same disks.
E.g. I make a pool with 4 disks.
I make it a 'Mirror' (kinda like RAID1). But I begin running out of space.
I can of course add a new disk and expand the Space.
But I can, from the same pool i.e. on the same disks, make another Space, this time I make it a Parity (similar to RAID5). It'll make it on the same disks. Then I can move data from the Mirror Space to the Parity Space on the same disks. Once it's done I can delete the Mirror Space off the disks leaving the Parity Space as the only volume.
So I can migrate all my data to a new 'array' but without deleting the data and formatting the disks first. It's a slower but a safer way to do things. I mean of course I have a separate cold backup, but I always feel jittery about deleting the live array and creating a new one, because I'm down to my only backup and it isn't even cold any more because I'm copying its contents to the new array. One thing goes wrong with the backup and poof, everything gone. I don't have to do that when I shuffle the data to a new volume but within the same disks using Storage Space.