When UFS file systems were supported I used to keep my custom scripts on a UFS formated USB flash drive so that I had access to these scripts even if my storage pool was disconnected for some reason. Given how small the amount of data in /custom, I want to save it on the boot drive (a 100GB SSD). I do not plan to share /custom - it is only for use at the FreeNAS command line or with cron jobs.
How can I create a dataset called custom and have it automatically mounted under the root '/' as '/custom'?
(I would prefer a dataset over a simple directory because I can snapshot it for both protection and ease of backup.0
I tried creating the dataset using the information I found here:
https://www.freebsd.org/doc/handbook/zfs-quickstart.html using the following command:
which is not mounted. What am I missing? What do I need to do to auto mount?
Will doing this damage the automatic updates? Is there any good reason not to do this?
(It's OK if the updates remove /custom just as long as the update works. I will back up /custom for easy restoration.)
How can I create a dataset called custom and have it automatically mounted under the root '/' as '/custom'?
(I would prefer a dataset over a simple directory because I can snapshot it for both protection and ease of backup.0
I tried creating the dataset using the information I found here:
https://www.freebsd.org/doc/handbook/zfs-quickstart.html using the following command:
freenas# zfs create freenas-boot/ROOT/custom
and got the following result: Code:
NAME USED AVAIL REFER MOUNTPOINT freenas-boot/ROOT/custom 136K 103G 136K none
Will doing this damage the automatic updates? Is there any good reason not to do this?
(It's OK if the updates remove /custom just as long as the update works. I will back up /custom for easy restoration.)