Hello. I did use the forum search so I apologize in advance if I just missed this.
I'm setting up a new server with 9.2-stable and using ZFS on root. I'm using the basic 3 part GPT layout boot/swap/zfsroot.
I notice (from these forums and Google searches) that most people make separate usr and var (and maybe tmp or use tmpfs) datasets. This is consistent with what I'm used to on a UFS machine. Then most people seem to make separate ones for ports and src so they can be compressed. This also makes some sense to me. I run poudriere (which uses a few more datasets) and I have a separate multimedia dataset (music, movies, etc). I will also set up jails for a few processes (mailer, webserver, radius server). At this point, I have probably 10-15 datasets which makes
My question is about /var. I notice that most people seem to be splitting /var up into multiple partitions (var/spool, /var/empty, /var/db, /var/run, /var/crash, /var/db/pkg, /var/log, /var/mail, /var/tmp in the example I most recently saw). While I realize the advantages about being able to set and fine-tune compression, read-only, noexec, setuid, etc, it seems this makes administration of the server much more cumbersome. Is there a consensus on whether this is all necessary? Does it really provide any noticeable performance or security gains? I'm tempted to use a single var dataset and compress the whole thing. It will be a fairly low traffic home and media server (so I'm probably over thinking this whole thing, but I'm curious anyway). The system it's replacing only has about 1.1 GB in /var and was first put together in 2008.
Again, I'm mostly thinking of the long-term maintenance of the machine. I'm interested in your comments.
I'm setting up a new server with 9.2-stable and using ZFS on root. I'm using the basic 3 part GPT layout boot/swap/zfsroot.
I notice (from these forums and Google searches) that most people make separate usr and var (and maybe tmp or use tmpfs) datasets. This is consistent with what I'm used to on a UFS machine. Then most people seem to make separate ones for ports and src so they can be compressed. This also makes some sense to me. I run poudriere (which uses a few more datasets) and I have a separate multimedia dataset (music, movies, etc). I will also set up jails for a few processes (mailer, webserver, radius server). At this point, I have probably 10-15 datasets which makes
df
and zfs list
somewhat tedious to parse and figure what's going on on the system as time goes by, but I'll get used to it.My question is about /var. I notice that most people seem to be splitting /var up into multiple partitions (var/spool, /var/empty, /var/db, /var/run, /var/crash, /var/db/pkg, /var/log, /var/mail, /var/tmp in the example I most recently saw). While I realize the advantages about being able to set and fine-tune compression, read-only, noexec, setuid, etc, it seems this makes administration of the server much more cumbersome. Is there a consensus on whether this is all necessary? Does it really provide any noticeable performance or security gains? I'm tempted to use a single var dataset and compress the whole thing. It will be a fairly low traffic home and media server (so I'm probably over thinking this whole thing, but I'm curious anyway). The system it's replacing only has about 1.1 GB in /var and was first put together in 2008.
Again, I'm mostly thinking of the long-term maintenance of the machine. I'm interested in your comments.