This indicates that share(1M) didn't produce any output, but returned a non-zero exit status. I'm not sure why this would happen - can you run the following by hand?
# share /export # echo $? Incidentally, the explicit 'zfs share' isn't needed, as we automatically share the filesystem when the options are set (which did succeed). - Eric On Fri, Aug 04, 2006 at 12:42:02PM -0400, Jim Connors wrote: > > Working to get ZFS to run on a minimal Solaris 10 U2 configuration. In > this scenario, ZFS is included the miniroot which is booted into RAM. > When trying to share one of the filesystems, an assertion is raised - > see below. If the version of source on OpenSolaris.org matches > Solaris 10 U2, then it looks like it's associated with a popen of > /usr/sbin/share. Can anyone shed any light on this? > > Thanks, > -- Jim C > > > # zfs list > NAME USED AVAIL REFER MOUNTPOINT > SYS 83K 163M 30.5K /SYS > export 110K 72.8G 25.5K /export > export/home 24.5K 72.8G 24.5K /export/home > # zpool list > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > SYS 195M 90K 195M 0% ONLINE - > export 74G 114K 74.0G 0% ONLINE - > # zfs set sharenfs=on export > # zfs share export > Assertion failed: pclose(fp) == 0, file ../common/libzfs_mount.c, line > 399, function zfs_share > Abort - core dumped > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
