zfs discuss - Jun 2006 - add_install_client and ZFS and SMF incompatibility

Hi,

I just set up an install server on my notebook and of course all the installer
data is on a ZFS volume. I love the "zfs compression=on" command!

It seems that the standard ./add_install_client script from the S10U2 Tools
directory creates an entry in /etc/vfstab for a loopback mount of the Solaris
miniroot into the /tftpboot directory.

Unfortunately, at boot time (I''m using Nevada build 39), the mount_all
script tries to mount the loopback mount from /vfstab before ZFS gets its
filesystems mounted.

So the SMF filesystem/local method fails and I have to either mount all ZFS
filesystems from hand, then re-run mount_all or replace the vfstab entry with
a simple symlink. Which only works until you say add_install_client the next
time.

Is this a known issue?

Best regards,
   Constantin

-- 
Constantin Gonzalez                            Sun Microsystems GmbH, Germany
Platform Technology Group, Client Solutions                http://www.sun.de/
Tel.: +49 89/4 60 08-25 91                   http://blogs.sun.com/constantin/

Constantin Gonzalez <Constantin.Gonzalez at Sun.COM> writes:
> Is this a known issue?
Yes, I''ve raised this during ZFS Beta as SDR-0192.  For some reason, I
don''t have a CR here.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University

On Fri, Jun 23, 2006 at 04:51:21PM +0200, Constantin Gonzalez
wrote:
> Hi,
> 
> I just set up an install server on my notebook and of course all the
installer
> data is on a ZFS volume. I love the "zfs compression=on" command!
> 
> It seems that the standard ./add_install_client script from the S10U2 Tools
> directory creates an entry in /etc/vfstab for a loopback mount of the
Solaris
> miniroot into the /tftpboot directory.
> 
> Unfortunately, at boot time (I''m using Nevada build 39), the
mount_all
> script tries to mount the loopback mount from /vfstab before ZFS gets its
> filesystems mounted.
> 
> So the SMF filesystem/local method fails and I have to either mount all ZFS
> filesystems from hand, then re-run mount_all or replace the vfstab entry
with
> a simple symlink. Which only works until you say add_install_client the
next
> time.
> 
> Is this a known issue?
The easiest way to work around it is to turn the zfs mount into a
"legacy"
mount, and mount it using vfstab.

	zfs set mountpoint=legacy pool/dataset
	(add pool/dataset mount line to vfstab)

Cheers,
- jonathan

-- 
Jonathan Adams, Solaris Kernel Development