I have an SSD and a spindle-type HDD. I take regular backups and I do not use a mirrored device. I have been thinking about placing root on the SSD to get faster boot time, but I decided I do not want my root on UFS because I want the error-check and auto-fsck properties of zpool.
Now I have come up with this "genius idea"
1. Create the zpool only on the SSD's planned root (gpt partition size 512MB)
2. Give the entire zpool to pool's own zfs file set (the dataset which will be our root)
3. Now expand pool size by adding the spindle HDD
4. Copy root's files to tank, zfs create the other datasets (usr, var, etc) and copy your data to each sub-dataset.
The result "should" (or hopefully might) be the root dataset residing on the SSD, but usr, var, home, etc residing on the spindle HDD.
My question is this: In the beginning, when the pool is first created in this manner, it is possible that what I have described (root fs on the SSD) will be true. However, as time goes by and the system is updated by the likes of installworld/installkernel, there is the possibility that the reserved root space will start migrating off of the SSD and on to the HDD. This would result in part of root being on the SSD, while the other half residing on the HDD, plus the space vacated by root becoming occupied by files from other folders.
What do you guys think? Am I being too smart for my own good?
Now I have come up with this "genius idea"
1. Create the zpool only on the SSD's planned root (gpt partition size 512MB)
2. Give the entire zpool to pool's own zfs file set (the dataset which will be our root)
# zfs set reservation=512M tank
3. Now expand pool size by adding the spindle HDD
# zpool add tank <geom>
4. Copy root's files to tank, zfs create the other datasets (usr, var, etc) and copy your data to each sub-dataset.
The result "should" (or hopefully might) be the root dataset residing on the SSD, but usr, var, home, etc residing on the spindle HDD.
My question is this: In the beginning, when the pool is first created in this manner, it is possible that what I have described (root fs on the SSD) will be true. However, as time goes by and the system is updated by the likes of installworld/installkernel, there is the possibility that the reserved root space will start migrating off of the SSD and on to the HDD. This would result in part of root being on the SSD, while the other half residing on the HDD, plus the space vacated by root becoming occupied by files from other folders.
What do you guys think? Am I being too smart for my own good?