Brian Hechinger wrote: > On Mon, Jun 23, 2008 at 11:18:21AM -0600, Lori Alt wrote: > >> Sorry it's taken me so long to weigh in on this. >> > > You're busy with important things, we'll forgive you. ;) > > >> 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. >> > > And thank you for doing so. I will always put /var in it's own "area" > even if the definition of that area has changed with the use of ZFS. > > Rampant writes to /var can *still* run / out of space even on ZFS, being > able to keep that from happening is never a bad idea as far as I'm > concerned. :) > >
I think the ability to have different policies for file systems is pure goodness -- though you pay for it on the backup/ restore side. 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? -- richard _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
