Adam Wilson wrote:
> I'm trying to use OpenSolaris as a zfs-over-nfs file server. I have one
> client, a Mac, connected to my Solaris box via a linksys router. The
> host and client are assigned static IP addresses. (My system/OS info is
> listed at the end of this post.)
[...]
> My system info:
>
> Solaris: SunOS Release 5.10 Version Generic_127128-11 64-bit / AMD64
> processor / Gigabyte GA-MA770-DS3-E mohterboard / 1 GB RAM
this is not OpenSolaris. Solaris 10 is a commercially supported product,
and the proper channel to address is your Sun Service contact.
That said: if the machine is indeed frozen (does it react to ping?), the
so-called "deadman timer" will enable you to get a crash dump: add this line:
set snooping=1
to the Solaris system's /etc/system file. The machine should panic when it
gets to the hung state.
If it's not completely frozen, this will have no effect. Boot it with kmdb
(or load kmdb when the machine is up: "mdb -K" - see "man kmdb" for
details), and when it seems hung, try to "drop" the machine to kmdb:
From the man-page:
The primary means for explicit debugger entry is with the
keyboard abort sequence for systems with local consoles and
the BREAK character for those with serial consoles. The
abort sequence is STOP-A or Shift-Pause for SPARC systems
with local consoles, and F1-A or Shift-Pause for x86 systems
with local consoles. See kbd(1) for a discussion of the
abort sequence and for instructions on disabling it.
once you've achieved that, type "$<systemdump", press return, and the
machine should create a crash dump in /var/crash/<hostname>/ upon reboot.
This will then be needed for further analysis.
HTH
Michael
--
Michael Schuster http://blogs.sun.com/recursion
Recursion, n.: see 'Recursion'
_______________________________________________
networking-discuss mailing list
[email protected]
