Hi, I wanna try to setup a machine via jumpstart with ZFS boot using svn_b95. Usually (UFS) I use a profile like this for it: install_type initial_install system_type standalone usedisk c1t0d0 partitioning explicit filesys c1t0d0s0 256 / filesys c1t0d0s1 16384 swap filesys c1t0d0s3 4096 /var filesys c1t0d0s4 8192 /usr filesys c1t0d0s5 4096 /opt filesys c1t0d0s7 free /joker ... # c1t0 gets replaced by the real "bootdisk path" via begin script Is something similar now possible wrt. ZFS, i.e. something like zpool create boot c1t0d0 swap=16G zfs create boot/root ; zfs set reservation=512M boot/root zfs create boot/var ; zfs set reservation=4G boot/var zfs create boot/usr ; zfs set reservation=8G boot/usr zfs create boot/opt ; zfs set reservation=4G boot/opt ??? Regards, jel. -- Otto-von-Guericke University http://www.cs.uni-magdeburg.de/ Department of Computer Science Geb. 29 R 027, Universitaetsplatz 2 39106 Magdeburg, Germany Tel: +49 391 67 12768
There is a section on jumpstart for root ZFS in the ZFS Administration
Guide.
http://www.opensolaris.org/os/community/zfs/docs/zfsadmin.pdf
You should also find it documented in the appropriate release
installation documents (though I haven''t checked those lately)
-- richard
Jens Elkner wrote:> Hi,
>
> I wanna try to setup a machine via jumpstart with ZFS boot using svn_b95.
> Usually (UFS) I use a profile like this for it:
>
> install_type initial_install
> system_type standalone
> usedisk c1t0d0
> partitioning explicit
> filesys c1t0d0s0 256 /
> filesys c1t0d0s1 16384 swap
> filesys c1t0d0s3 4096 /var
> filesys c1t0d0s4 8192 /usr
> filesys c1t0d0s5 4096 /opt
> filesys c1t0d0s7 free /joker
> ...
> # c1t0 gets replaced by the real "bootdisk path" via begin script
>
>
> Is something similar now possible wrt. ZFS, i.e. something like
>
> zpool create boot c1t0d0 swap=16G
> zfs create boot/root ; zfs set reservation=512M boot/root
> zfs create boot/var ; zfs set reservation=4G boot/var
> zfs create boot/usr ; zfs set reservation=8G boot/usr
> zfs create boot/opt ; zfs set reservation=4G boot/opt
>
> ???
>
> Regards,
> jel.
>
On Thu, Aug 14, 2008 at 02:33:19PM -0700, Richard Elling wrote:> There is a section on jumpstart for root ZFS in the ZFS Administration > Guide. > http://www.opensolaris.org/os/community/zfs/docs/zfsadmin.pdfAh ok - thanx for the link. Seems to be almost the same, as on the web pages (thought, they are out of date ...)> >Is something similar now possible wrt. ZFS, i.e. something like > > > >zpool create boot c1t0d0 swap=16G > >zfs create boot/root ; zfs set reservation=512M boot/root > >zfs create boot/var ; zfs set reservation=4G boot/var > >zfs create boot/usr ; zfs set reservation=8G boot/usr > >zfs create boot/opt ; zfs set reservation=4G boot/opt > > > >???So the answer is NO :(((( . Regards, jel. -- Otto-von-Guericke University http://www.cs.uni-magdeburg.de/ Department of Computer Science Geb. 29 R 027, Universitaetsplatz 2 39106 Magdeburg, Germany Tel: +49 391 67 12768
On Thu, Aug 14, 2008 at 10:49:54PM -0400, Ellis, Mike wrote:> You can break out "just var", not the others.Yepp - and that''s not sufficient :( Regards, jel. -- Otto-von-Guericke University http://www.cs.uni-magdeburg.de/ Department of Computer Science Geb. 29 R 027, Universitaetsplatz 2 39106 Magdeburg, Germany Tel: +49 391 67 12768
I''m not sure why you want to separate out all these filesystems on a root disk these days? The reason I recall needing to do it over a decade ago, was because disks were so small and perhaps you couldn''t FIT /opt onto the same disk with /usr. So you needed to be able to say /usr is on this disk and /opt is over here on another one. Perhaps it would be good if you explained the need for all these filesystems? If you have apps that need a lot of space, they can have their own filesystems created after the OS is installed. Like your /joker for instance, just do a zfs create for that after the OS install. This is my profile: # #cluster This tells what cluster of packages to install. # SUNWCXall is Entire Solaris Software Group Plus OEM Support. # SUNWCall is Entire Solaris Software Group. # SUNWCprog is Developer Solaris Software Group. # SUNWCuser is End User Solaris Software Group. # SUNWCreq is Core System Support Software Group. # SUNWCrnet is Reduced Network Support Software Group. install_type initial_install pool rpool auto auto auto mirror c1t0d0s0 c1t1d0s0 bootenv installbe bename zfsroot dataset /var system_type standalone cluster SUNWCXall For applications which need a little space that is tightly managed to not impact other applications running on the same system, like scratch/tmp/lock-files which might go nuts, I just give them a piece of the TMPFS filesystem and set a limit on it''s size in /etc/vfstab: swap - /var/imap-proc tmpfs - yes size=512m swap - /var/imap-socket tmpfs - yes size=512m swap - /var/imap-log tmpfs - yes size=512m This message posted from opensolaris.org