Mike Gerdts wrote:
On Wed, Jun 4, 2008 at 11:18 PM, Rich Teer <[EMAIL PROTECTED]> wrote:
Why would one do that? Just keep an eye on the root pool and all is good.
The only good argument I have for separating out some of /var is for
boot environment management. I grew tired of repeating my arguments
and suggestions and wrote a blog entry.
http://mgerdts.blogspot.com/2008/03/future-of-opensolaris-boot-environment.html
Sorry it's taken me so long to weigh in on this.
The reason that the install program permits the user
to set up a separate /var dataset is because some
production environments require it. More exactly, some
production environments require that /var have its
own slice so that unrestrained growth in /var can't
fill up the root file system. (I have no idea whether
this is actually a good or sufficient policy.
I just know that some customer environments have
such a policy.)
With zfs, we don't actually have to put /var in its own
slice. We can achieve the same goal by putting it
in its own dataset and assigning a quota to that dataset.
That's really the only reason we offered this option.
Lori
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
