3 ms·
> They don't use ZFS or mdadm; they've implemented their own raid system they call "synology hybrid raid" (SHR). It supports surprisingly smart heterogenous dri
by matheusmoreira 6y ago
> They don't use ZFS or mdadm; they've implemented their own raid system they call "synology hybrid raid" (SHR). It supports surprisingly smart heterogenous drive size utilization while still maintaining N-Drive redundancy
This is their best feature in my opinion. It allows users to just buy random drives from time to time and add them to the NAS when they need to expand storage capacity. Unraid also offers a similar feature albeit with a different implementation.
Current open source solutions just don't compare. Expanding storage with Linux device mapper involves failing and replacing each storage device:
https://raid.wiki.kernel.org/index.php/Growing https://raid.wiki.kernel.org/index.php/Growing
Even btrfs wastes 6 TB when given its 2+4+6+8 TB example:
https://carfax.org.uk/btrfs-usage/index.html https://carfax.org.uk/btrfs-usage/index.html
I wonder why existing systems can't support this easy expansion. It'd be a huge help for home users who'd like to slowly expand their storage capacity.
- zozbot234 6y ago> It supports surprisingly smart heterogenous drive size utilization while still maintaining N-Drive redundancy: with, for example, a 2TB+4TB+6TB+8TB drive combination You can do this yourself with ease by creating 2TB partitions on all drives and setting up RAID separately on each. Then you could use LVM to access them as unified storage, or keep them separate for extra flexibility when restoring.
- 013a 6y agoYou can also replicate Dropbox quite trivially by getting an FTP account, mounting it locally with curlftpfs, then use SVN or CVS on the mounted filesystem [1] [1] https://news.ycombinator.com/item?id=8863 https://news.ycombinator.com/item?id=8863
- fomine3 6y agoIt's theoretically possible but I'm afraid of operation failure for such complex array. So It's nice to have simple user interface like Synology.
- gravitas 6y ago> Expanding storage with Linux device mapper involves failing and replacing each storage device The same process is generally true of mainstream enterprise controllers such as Dell PowerEdge/PERC and HPe ProLiant/SmartArray; each existing drive is failed out (in turn) and the RAID rebuilt onto the new larger drive, then the controller array container is expanded once all drives are replaced.
- singron 6y agoWhat parameters are you using to make btrfs waste 6TB? With 2 copies (RAID1) and 2+4+6+8, that calculator shows it with 0 unusable space?
- matheusmoreira 6y agoI used RAID 6. That's 1 copy and 2 parity stripes.
- singron 6y agoAh that explains it. Don't use parity with btrfs (i.e. RAID5/6). If you really want that, that's a good reason not to use btrfs.
- matheusmoreira 6y agoBecause of the write hole, right? I've been avoiding btrfs because of that issue. Multiple copies are too wasteful and the parity implementation isn't perfect. Hope it gets fixed soon.
- zrm 6y agoThat was recently fixed in mdadm. You can now specify a journal device (--write-journal) which closes the write hole. I don't see any reason btrfs couldn't do something equivalent.