IIRC, there was a problem with having smbshare=on and the CIFS service disabled and I think I saw a CR fix go by. I don't recall the CR number but a search of recent sharemgr updates would probably reveal it.
Rob Vassar wrote: > Following up in the name of completeness... Trying to forceload the > smbserv driver didn't help, but disabling Samba allows the system > to come up. So if you intend to try the kernel CIFS server, and > later move to Samba, keep notes. You'll likely have to undo every > step. If you don't have the sharemgr update to handle smbshare=on when CIFS is disabled, I suspect the only change would be to disable automatic sharing via CIFS. Alan > Rob > _______________________________________________ Rob Vassar wrote: > I had tried to configure the new Solaris CIFS server using a fresh install of > build 84. I couldn't seem to get it working with my MacOS X client, and > didn't have time to troubleshoot it. I decided to back out and use Samba. I > disabled smbserv and configured up Samba, and thought everything was fine. > Then I rebooted the machine... and now I have a nice repeatable reboot loop. > > > I think part of my problem is that I had set smbshare=on on a zfs pool. The > kernel crashes shortly after bringing up ZFS, and the stack trace appears to > implicate the smb server. > > > I can only poke around in 32 bit failsafe mode. I need to bring the machine > up further to get the crash dumps off the machine. I'm hopping on a plane > Sunday for Santa Clara, so if anyone has any weekend suggestions... :-) > > > Rob > > > This message posted from opensolaris.org > _______________________________________________ > storage-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/storage-discuss _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
