[EMAIL PROTECTED] wrote On 09/08/06 09:06,:

I have the same with my home-installserver. As a dirty solution I
set mount-at-boot to "no" for the lofs Filesystems, to get the system up.
But with every new OS added by JET the mount at reboot reappears.

Seems to me as the question "when should a lofs filesystem be mounted at boot".
When does a zfs filesystem get mounted?
Probably a zfs legacy mount together with a lower priority lofs mount
would do it.



JET needs to be taught about ZFS; there does not seem to be any other
way.

Maybe. However, I did not use JET. I set up ZFS using default (AFAIK at this point) parameters.


(JET/setup_install_server creates the loopback mounts; without making the
ZFS mounts into legacy mounts or creating them differently it will not work; personally I use auto_direct for the /tftpboot sub mounts; works
for anything)

I believe that add_install_client [with a -b option?] is what is creating my vfstab entries. I haven't had reboot issues until overnight (a system move), and I have been doing PXE boot of some x64 systems only recently, i.e. since the most recent power failure.

Install images are being put down via getimage, so it is possible that setup_install_server would do the same. (not sure whether getimage does a setup_install_server at it completion.)

Steffen


Casper

_______________________________________________
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

Reply via email to