ZFS: Use mirror vdevs, not RAIDZ
jrs-s.net
ZFS: Use mirror vdevs, not RAIDZ
1–10 of 133 posts
Re: ZFS: Use mirror vdevs, not RAIDZ
#2Re: ZFS: Use mirror vdevs, not RAIDZ
#3Re: ZFS: Use mirror vdevs, not RAIDZ
#4Re: ZFS: Use mirror vdevs, not RAIDZ
#5Re: ZFS: Use mirror vdevs, not RAIDZ
#6LOL.
Re: ZFS: Use mirror vdevs, not RAIDZ
#7> don’t be greedy. 50% storage efficiency is plenty. LOL.
Re: ZFS: Use mirror vdevs, not RAIDZ
#8There’s still a place for RAIDZ/RAIDZ2, and in my opinion that place is storing bulk data that isn’t too heavily accessed or that needs to be stored with an eye towards keeping £/GB down.
Yes, mirrors are faster. Yes, mirrors are easier to expand. But across 12 4TB disks that is 24TB instead of 40TB with RAIDZ2 - and that’s a lot of capacity to lose if you’re on a budget.
The rebuild times in this post seem high to me, though. I replaced 7x 2TB disks (nearly full) in a raidz1 in a backup pool with larger drives in about 30 hours.
Re: ZFS: Use mirror vdevs, not RAIDZ
#9But drive failure is much more likely during an operation like a resilver/resync, and I wonder if the majority of people espousing more risky RAID a setups (especially single parity) are those who just want hundreds of TB for a growing media collection.
I know for my critical data, I don't trust parity. Plus I can't afford the days or weeks long resilver operation, I need a working storage array that doesn't suffer drastically in performance if one drive goes bad.
Re: ZFS: Use mirror vdevs, not RAIDZ
#10“So backup your data!” - of course, but that’s just an implicitly larger pool.