I've searched, and I think I understand, but just want to verify that I have the right concept.
I am building a new PC, and want to set up the old one as a file server. Ultimately, I would like two "drives" (volumes? pools?), both with redundancy. One for the OS, and the rest for the media.
Drives:
Can I partition like this:
Then:
Is my thinking correct? Is there a better way of doing this?
I know that, assuming this method is optimal, I wouldn't create a mirror using both 0.5TB partitions on the single 2.0TB drive. I would need to use one for each mirror, or I'd be defeating the purpose of a mirror :)
The thing that strike me most in your case is the partitioning. That is a disk might be used by more than one vdev (aka group), which is of course a major risk, but I understand perfectly that this is an old PC giving a new life as a NAS (I have one at home as well).
There is no major loophole in your schema, except that:
Here are some best practices (details here) regarding the building of groups:
If I may add, keep in mind as well that your system will eventually evolve. You might want to be able to replace disks by bigger ones which would only be possible if your group are not too big (or you'll end up in having to get 8 new disks before being able to get some more space from your data pool).
You may as well consider forcing zfs to use 4k sectors (ashift= 12) even if in your case there is good chance that 512b sectors (ashift= 9) would be the default setting. Again, for later upgrade as you really, really don't want to mix ashift in a pool.
Edit: mixed vdev in a pool is possible, but not recommended (thanks @bahamat) and warning about "ashift".
Collected from the Internet
Please contact [email protected] to delete if infringement.
Comments