On Mon, Jun 23, 2008 at 05:45:45PM -0700, Richard Elling wrote: > > I think the ability to have different policies for file systems > is pure goodness -- though you pay for it on the backup/ > restore side.
That's a price I for one am willing to pay. ;) > A side question though, my friends who run Windows, > Linux, or OSX don't seem to have this bias towards isolating > /var. Is this a purely Solaris phenomenon? If so, how do we > fix it? This is not a purely Solaris phenomenon, this is a UNIX phenomenon. People who run Linux or OSX (I can't speak for Windows users) tend to be "new to the game" and feel that "This 40/80/500GB disk will never fill up" and so don't believe that seperating /var is needed. It doesn't matter how big your disk is, a rampant process can fill up any disk of any size, it's just a matter of how long it takes. It isn't just /var that can cause trouble either, it's just that /var is the "usual suspect" since it's the filesystem that tends to get written to by the largest number of different processes. /tmp on a system that doesn't do tmpfs (BSD for example) is another likely candidate. Keeping / as far away from everything else as possible is never a bad idea. ZFS only makes this task easier (IMHO) since you can set quotas and reserves on different filesystems, thus protecting yourself from damage, and also at the same time not "wasting" disk space that could be better used elsewhere. Opinionated? Me? Yes. ;) -brian -- "Coding in C is like sending a 3 year old to do groceries. You gotta tell them exactly what you want or you'll end up with a cupboard full of pop tarts and pancake mix." -- IRC User (http://www.bash.org/?841435) _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
