It's way too late at night for me to give an in-depth answer, but I just wanted to let you know that if you plan on adding drives over time, you might want to check out running the disks in JBOD instead of RAID and then use ZFS to create the storage vo...
-
wrote on last edited by [email protected]
It's way too late at night for me to give an in-depth answer, but I just wanted to let you know that if you plan on adding drives over time, you might want to check out running the disks in JBOD instead of RAID and the use ZFS to create the storage volume. Redundancy supported, and you can add disks whenever you need more space. The disks don't even have to be the same size.
-
It's way too late at night for me to give an in-depth answer, but I just wanted to let you know that if you plan on adding drives over time, you might want to check out running the disks in JBOD instead of RAID and the use ZFS to create the storage volume. Redundancy supported, and you can add disks whenever you need more space. The disks don't even have to be the same size.
Agreeing with this, expanding a RAID array is not necessarily impossible, with something like RAID 5, and the right RAID setup, you could theoretically add an identical disk without wiping it all in the rebuild. RAID 1, you'll 100% need to copy the data somewhere that isn't the 2/4 disks in the meantime. In an environment where storage is expensive, RAID 1 is not suitable imo.
ZFS makes it so easy though. Throw a mismatched disk in? No big deal, it's in your pool now. Want double parity for extra peace of mind? You can do that. It self-heals so you don't need fsck, its maximum limits are too big to realistically matter on human scales, and the documentation on it is pretty good.