![]() The zvol should have a ext2 partition on it (as evidenced by the CentOS VM to which the zvol is currently shared by iSCSI): ~]# file - 63 16777153 da0 MBR (8.0G) The least you can do is give ZFS the means means to protect against failed/failing disks: more than just the minimum number of disks required.I'm trying to mount a snapshot of a ZFS zvol. ZFS goes to great lengths to use software to keep from loosing your data (checksums, parity/redundant copies, scrubbing, etc) without the need for an expensive and proprietary controller card. But if you, like most people considering ZFS for a home server, have come to the conclusion that you won't (or can't afford to) perform regular backups and likely won't notice/replace a failed disk immediately, you should really consider the incremental cost of a hotspare and mirroring/RAID-Z2 instead of simple parity (RAID-Z) it just increases the odds you'll still have your data a few years down the road. If you have everything backed up elsewhere, you don't care about the 5% chance of a second disk failing during rebuild. Really, it's all about how valuable your data is. Also, in case you're curious write performance is directly correlated with the number of VDEVs in the pool. If you'd chosen mirroring over raidz in the beginning, the initial five disks would've yielded a 4x3TB mirror + hotspare (6TB usable, 2 vdevs) and you could've just added pairs of disks as you needed them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |