here is the other posts that vanished.
2009/12/6 Richard Look for the panic string in /var/adm/messages* Hint: these messages are written by syslogd, so when you go to a machine that uses syslogd, you can discern the location of the log files by looking at the /etc/syslog.conf file. Look for a matching bug at http://bugs.opensolaris.org Others have reported that COMSTAR is kinda flaky prior to b114. If you do not want to upgrade to the dev builds, then be aware that good iSCSI performance for 2009.06 is predicated by the client enabling the write cache. -- richard 2009/12/6 Ignacio Marambio Catán <darkjo...@gmail.com>: oh, one more thing, try upgrading to /dev before filling any bugs, i'm sure a great many things were fixed since that opensolaris was released. To switch to the /dev repository pfexec pkg set-publisher -O http://pkg.opensolaris.org/dev opensolaris.org && pfexec pkg refresh --full && pfexec pkg install SUNWipkg && pfexec pkg image-update -v Then wait. Don't forget to read the release notes before starting out. 2009/12/6 Ignacio Marambio Catán <darkjo...@gmail.com>: > is there a kernwl dump in /var/crash/${hostname} if there is that. try > running the following command > > mdb -k unix.n vmcore.n > > where n is a number > after that run, in the prompt of mdb, run > > $C > > That should tell you where the kernel crashed and will give someone > more skilled than i am more information to know why it happened :) > > nacho -- This message posted from opensolaris.org _______________________________________________ opensolaris-help mailing list opensolaris-help@opensolaris.org
