I am working on a NanoBSD project. I am planning an unconventional route with separate slices for APP and DATA.
So normal NanoBSD setup with UFS on s1,s2,s3.
Due to the appliance nature of the build I am looking for maximum filesystem protection for my extra slices.
Would ZFS on s4,s5 help any with filesystem resiliency?
Can I use both ZFS and UFS on the same drive?
This might end up on a industrial 4GB SD Card.
s1,s2,s3 take up around 800MB just for safety sake. So lets say I need a 2GB APP slice and 200MB DATA slice.
2GB for our APP slice is way more than I need.
I guess what I am asking is how to best use all the extra space above the NanoBSD setup.
Any tricks or tips. I just learned of interleaving swap. So I have much to learn about Unix. Can I RAID1 partitions?
I realize MBR is probably not going to work with ZFS, but NanoBSD has an UEFI option and I think GPT too.
My other option is to extend the NanoBSD script and use a MemoryDisk for these additional slices/partitions too..
That sounds real messy.
So normal NanoBSD setup with UFS on s1,s2,s3.
Due to the appliance nature of the build I am looking for maximum filesystem protection for my extra slices.
Would ZFS on s4,s5 help any with filesystem resiliency?
Can I use both ZFS and UFS on the same drive?
This might end up on a industrial 4GB SD Card.
s1,s2,s3 take up around 800MB just for safety sake. So lets say I need a 2GB APP slice and 200MB DATA slice.
2GB for our APP slice is way more than I need.
I guess what I am asking is how to best use all the extra space above the NanoBSD setup.
Any tricks or tips. I just learned of interleaving swap. So I have much to learn about Unix. Can I RAID1 partitions?
I realize MBR is probably not going to work with ZFS, but NanoBSD has an UEFI option and I think GPT too.
My other option is to extend the NanoBSD script and use a MemoryDisk for these additional slices/partitions too..
That sounds real messy.