I guess I didn't make it clear that I had already tried using savecore
to retrieve the core from the dump device.
I added a larger zvol for dump, to make sure that I wasn't running out
of space on the dump device:
r...@host:~# dumpadm
Dump content: kernel pages
Dump device: /dev/zvol/dsk/rpool/bigdump (dedicated)
Savecore directory: /var/crash/host
Savecore enabled: yes
I was using the -L option only to try to get some idea of why the
system load was climbing to 1 during a simple file copy.
On Wed, Mar 11, 2009 at 4:58 PM, Richard Elling
<richard.ell...@gmail.com> wrote:
> Blake wrote:
>>
>> I'm attaching a screenshot of the console just before reboot. The
>> dump doesn't seem to be working, or savecore isn't working.
>>
>> On Wed, Mar 11, 2009 at 11:33 AM, Blake <blake.ir...@gmail.com> wrote:
>>
>>>
>>> I'm working on testing this some more by doing a savecore -L right
>>> after I start the copy.
>>>
>>>
>
> savecore -L is not what you want.
>
> By default, for OpenSolaris, savecore on boot is disabled. But the core
> will have been dumped into the dump slice, which is not used for swap.
> So you should be able to run savecore at a later time to collect the
> core from the last dump.
> -- richard
>
>
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
