Not sure how traditional-traditional (hw RAID?) you’re referring to but you can use different disk sizes as well as grow LVM/mdraid or ZFS. It does indeed require a bit more thought and reading to do well. On the upside it’s probably much safer (for data integrity) and more performant.
As I remember ZFS did recently just add the ability to grow an array, but it’s not seamless and wastes space because of some limitations with it. You also need to learn the CLI procedures to do it without breaking something, vs just clicking a button on a webUI.
ZFS also recently had a major data loss bug so I’m not sure safer is accurate.
I do use ZFS on my servers, I’m not actually an unraid user myself. But managing ZFS is not easy and takes a lot of time to learn.
You’re right, raidz expansion is brand new and I probably wouldn’t use it for a few years. I was referring to adding new redundant vdevs to an existing pool which has always been supported as far as I know. E.g. if you have an existing raidz or mirror, you can add another raidz or mirror vdev to the pool. The pool size grows with the usable size of the new vdev. It’s just zpool add thepool mirror disk1 disk2 as far as I know. The downside being it results in less usable space - e.g. two raidz1 vdevs remove 2 disks from the usable space, whereas Unraid-raid would remove 1. For example if you have 3x 3TB and 3x 4TB disks, you’d end up with 14TB usable space with ZFS and 17TB with Unraid. On the flip side, the two raidz1 vdevs would have higher reliability since you can have one disk die in each vdev.
just clicking a button on a webUI.
No question. I think TrueNAS offers this too.
ZFS also recently had a major data loss bug so I’m not sure safer is accurate.
Imagine how many of those would be found in Unraid-raid if it was used as widely and for similar loads as ZFS. My argument isn’t that there aren’t bugs in storage systems. There are, and the more eyes have seen the code and the more users have lost data for more years, the fewer bugs would remain. Assuming similar competence of the system developers, ZFS being much older and ran for production loads makes it more likely to contain fewer data eating bugs than Unraid.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Not sure how traditional-traditional (hw RAID?) you’re referring to but you can use different disk sizes as well as grow LVM/mdraid or ZFS. It does indeed require a bit more thought and reading to do well. On the upside it’s probably much safer (for data integrity) and more performant.
As I remember ZFS did recently just add the ability to grow an array, but it’s not seamless and wastes space because of some limitations with it. You also need to learn the CLI procedures to do it without breaking something, vs just clicking a button on a webUI.
ZFS also recently had a major data loss bug so I’m not sure safer is accurate.
I do use ZFS on my servers, I’m not actually an unraid user myself. But managing ZFS is not easy and takes a lot of time to learn.
You’re right, raidz expansion is brand new and I probably wouldn’t use it for a few years. I was referring to adding new redundant vdevs to an existing pool which has always been supported as far as I know. E.g. if you have an existing raidz or mirror, you can add another raidz or mirror vdev to the pool. The pool size grows with the usable size of the new vdev. It’s just
zpool add thepool mirror disk1 disk2as far as I know. The downside being it results in less usable space - e.g. two raidz1 vdevs remove 2 disks from the usable space, whereas Unraid-raid would remove 1. For example if you have 3x 3TB and 3x 4TB disks, you’d end up with 14TB usable space with ZFS and 17TB with Unraid. On the flip side, the two raidz1 vdevs would have higher reliability since you can have one disk die in each vdev.No question. I think TrueNAS offers this too.
Imagine how many of those would be found in Unraid-raid if it was used as widely and for similar loads as ZFS. My argument isn’t that there aren’t bugs in storage systems. There are, and the more eyes have seen the code and the more users have lost data for more years, the fewer bugs would remain. Assuming similar competence of the system developers, ZFS being much older and ran for production loads makes it more likely to contain fewer data eating bugs than Unraid.