On Wed, Apr 06, 2011 at 08:08:06AM -0700, Erik Trimble wrote: > On 4/6/2011 7:50 AM, Lori Alt wrote: > On 04/ 6/11 07:59 AM, Arjun YK wrote: > > I'm not sure there's a defined "best practice". Maybe someone else > can answer that question. My guess is that in environments where, > before, a separate ufs /var slice was used, a separate zfs /var > dataset with a quota might now be appropriate. > Lori > > Traditionally, the reason for a separate /var was one of two major > items: > (a) /var was writable, and / wasn't - this was typical of diskless or > minimal local-disk configurations. Modern packaging systems are making > this kind of configuration increasingly difficult. > (b) /var held a substantial amount of data, which needed to be handled > separately from / - mail and news servers are a classic example > For typical machines nowdays, with large root disks, there is very > little chance of /var suddenly exploding and filling / (the classic > example of being screwed... <wink>). Outside of the above two cases, > about the only other place I can see that having /var separate is a > good idea is for certain test machines, where you expect frequent > memory dumps (in /var/crash) - if you have a large amount of RAM, > you'll need a lot of disk space, so it might be good to limit /var in > this case by making it a separate dataset.
People forget (c), the ability to set different filesystem options on /var. You might want to have `setuid=off' for improved security, for example. -- -Gary Mills- -Unix Group- -Computer and Network Services- _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
