On 04/ 6/11 07:59 AM, Arjun YK wrote:
Hi,
I am trying to use ZFS for boot, and kind of confused about how the
boot paritions like /var to be layed out.
With old UFS, we create /var as sepearate filesystem to avoid various
logs filling up the / filesystem
I believe that creating /var as a separate file system was a common
practice, but not a universal one. It really depended on the
environment and local requirements.
With ZFS, during the OS install it gives the option to "Put /var on a
separate dataset", but no option is given to set quota. May be, others
set quota manually.
Having a separate /var dataset gives you the option of setting a quota
on it later. That's why we provided the option. It was a way of
enabling administrators to get the same effect as having a separate /var
slice did with ufs. Administrators can choose to use it or not,
depending on local requirements.
So, I am trying to understand what's the best practice for /var in
ZFS. Is that exactly same as in UFS or is there anything different ?
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
Could someone share some thoughts ?
Thanks
Arjun
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
