cookiemonster wrote: ↑
08 Jan 2019 23:34
Hi JoseMR. I finally upgraded to RootOnZFS.
Some feedback from my setup. I was on embedded on a single USB stick with a data partition and swap on it.
1. I'm sure I read somewhere and was logical anyway to backup the data in any existing partition on the embedded installation media. I ignored the advice expecting to be able to mount it after installation but the data was not there. I put that as experience and so others don't make the same mistake. I'll have to track what was there and move on.
2. My installation has one HBA where all disks are attached to. My main pool and now my new two mirrored SSDs for the root pool. After installation and reboot I was unable to boot to new disks. For some reason the PCI slot it is in was disabled in BIOS. It took me a while and many reboots to track the problem. Solved now. Booted to Full on RootOnZFS, re-scanned for disks, force imported the pool. All good.
3. Actual feedback: I chose mirrored install on default OS partition size, chose my choice of size for mirrored swap and defaults for size of data partition. I ended up with default choices of size for OS and data that are not of my liking. They are Root: 59.59 GB, Data 57 GB, Swap 4.29 GB.
My point I chose swap 4 GB and left the installer chose the sizes for data and root. It would be even better if the installer gave the option at the end of giving the sizes it works out by choosing defaults and the option to go back to change them. Unless I didn't use the tool correctly and this was there and I missed it.
4. Question if I may: Once rebooted and the disks were presented by BIOS to chose device to boot from, in my case it gave me the option of choosing one of the two devices I installed in mirror to. I've chosen the first in the just because it is the first.
4.a. Does it matter which one I chose?
4.b. Am I right in thinking that the OS will, those two being mirrored, keep the data I put on them i,e, packages, data, configuration changes synced between the two or do I have to do it somehow?
Thanks in advance and great improvement.
Hi cookiemonster, sorry for overlook and the late reply, but I will try to answer your questions as simple as I can.
On regards to #1, yes, the user should backup the existing "Data" partition on Embedded if this data is very important(though unlikely) before a re-install generally, this is why is strongly advised not to put any critical "Data" on Embedded data partition unless this data is mirrored which is only available in RootOnZFS.
On regards to #2, if you are using an HBA for all, ZFS Data pool and for RootOnZFS, the motherboard and/or the HBA need boot support to be enabled to boot from the RootOnZFS drive(s), in my case I personally use the onboard SATA ports for OS and my LSI HBA for the ZFS storage pool, but either way it should work with no problems.
On regards to #3, the latest ZFS installer has the most sane defaults, and if you chose Mirror you will also noticed that there are 2 modes for the SWAP, one is redundant and the other is just like a JBod or spanned, if you chose Mirrored Swap @ 2GB in size, they will remains at 2GB redundant, if you chose Multiple Swap @ 2GB they will be summed to a 4GB total, Mirrored Swap is the recommended choice for maximum reliability and redundancy, as per the "Data" partition, under ZFS there is no such "Data" partition, but rather filesystems and as a plus no need to bother any longer with mounting this(which exception to legacy mount points), if you opted to create a "Data" filesystem(a dataset) under RootOnZFS, this will be automatically available after reboot and the space is shared across the "zroot" which is the tank for the Boot Environments, /tmp, /var and Data if user opted for it, this meant that the overall "zroot" space usage meter is shared between this filesystems, OTOH, there is the option for specify the zroot space you want, this is most likely for users who want to dedicate a disk partition solely for ZFS L2ARC, ZIL etc. under more complex and/or odd scenarios.
On regards to #4 and #4a, it does not mater from what drive you boot from as long as they mirrored makes no difference, between for keep an order and for administration simplicity, most users chose the first drive as the initial BIOS/EFI boot subsequently the second one etc., in the even of a failed one, the other will remain working until administrator maintenance schedule.
On regards to #4b, all the data put on RootOnZFS Mirror(either system or personal) is exactly as safe as any ZFS Mirror with all the self-healing and check-summing features of the ZFS, though I strongly recommend to leave the personal/critical data to be stored in a separate ZFS pool, between if the hardware is limited to one or 2 drives only, the user can still use the "Data" option to put their data on it and perform regular backups whenever possible.
If you need more help in regards to RootOnZFS, please don't hesitate to ask.