[OmniOS-discuss] Two panics now while writing eager zeros to zvols

[Richard Jahnel]

Faulty output for yesterday:

--------------- ------------------------------------  -------------- ---------
TIME            EVENT-ID                              MSG-ID         SEVERITY
--------------- ------------------------------------  -------------- ---------
Oct 08 16:18:59 37ff548e-1a7e-48b7-cbc1-9577366cda82  SUNOS-8000-KL  Major

Host        : vstore1
Platform    : PowerEdge-R510Chassis_id  : 8K307S1
Product_sn  :

Fault class : defect.sunos.kernel.panic
Affects     : sw:///:path=/var/crash/unknown/.37ff548e-1a7e-48b7-cbc1-9577366cda82
                  faulted but still in service
Problem in  : sw:///:path=/var/crash/unknown/.37ff548e-1a7e-48b7-cbc1-9577366cda82
                  faulted but still in service

Description : The system has rebooted after a kernel panic.  Refer to
              http://illumos.org/msg/SUNOS-8000-KL for more information.

Response    : The failed system image was dumped to the dump device.  If
              savecore is enabled (see dumpadm(1M)) a copy of the dump will be
              written to the savecore directory /var/crash/unknown.

Impact      : There may be some performance impact while the panic is copied to
              the savecore directory.  Disk space usage by panics can be
              substantial.

Action      : If savecore is not enabled then please take steps to preserve the
              crash image.
              Use 'fmdump -Vp -u 37ff548e-1a7e-48b7-cbc1-9577366cda82' to view
              more panic detail.  Please refer to the knowledge article for
              additional information.

-----Original Message-----
From: Dan McDonald [mailto:danmcd at omniti.com]
Sent: Friday, October 09, 2015 12:47 PM
To: Richard Jahnel
Cc: omnios-discuss at lists.omniti.com; imemo; Dan McDonald
Subject: Re: [OmniOS-discuss] Two panics now while writing eager zeros to zvols


> On Oct 8, 2015, at 6:28 PM, Richard Jahnel <rjahnel at ellipseinc.com> wrote:
>
> Any ideas? Dump available upon request.
>

I have to go, but I took a quick look at your one dump:

> $c
vpanic()
hati_pte_map+0x3ab(ffffff16fb3dde70, 6f, ffffff007aef5358, 800000101cecd007, 0,
0)
hati_load_common+0x139(ffffff15ae13ca88, 806f000, ffffff007aef5358, 40b, 0, 0) hat_memload+0x75(ffffff15ae13ca88, 806f000, ffffff007aef5358, b, 0) segvn_faultpage+0x730(ffffff15ae13ca88, ffffff169c042ee8, 806f000, d000, 0,
ffffff009a23fb50)
segvn_fault+0x8e6(ffffff15ae13ca88, ffffff169c042ee8, 806f000, 1000, 1, 2) as_fault+0x31a(ffffff15ae13ca88, ffffff168f631de0, 806ff20, 1, 1, 2)
pagefault+0x96(806ff20, 1, 2, 0)
trap+0x2c7(ffffff009a23ff10, 806ff20, b)
0xfffffffffb8001d6()
> ::status
debugging crash dump vmcore.4 (64-bit) from vstore1 operating system: 5.11 omnios-f090f73 (i86pc) image uuid: 37ff548e-1a7e-48b7-cbc1-9577366cda82
panic message: hati_pte_map: flags & HAT_LOAD_REMAP dump content: kernel pages only
>


This is a panic while servicing a page fault.  Usually when I see something like this, I have to ask if your HW is okay.  ("fmadm faulty" show anything?)

Beyond that, I'll need to dig deeper, but I can't now.  Just wanted to let you know the stuff on the surface, at least.

Thanks for sharing the dump!
Dan

________________________________

The content of this e-mail (including any attachments) is strictly confidential and may be commercially sensitive. If you are not, or believe you may not be, the intended recipient, please advise the sender immediately by return e-mail, delete this e-mail and destroy any copies.