From: Gabriele Bulfon <gbulfon@sonicle.com>
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] fmd core dump
Date: Fri, 9 Aug 2024 16:43:28 +0200 (CEST) [thread overview]
Message-ID: <148564749.1666.1723214608129@www> (raw)
In-Reply-To: <D2405D0B-3CF3-432F-A090-0EDC29010A2E@me.com>
[-- Attachment #1.1: Type: text/plain, Size: 2829 bytes --]
The problem happened again, but this time the rpool was not yet full.
The pstack output shows again the same problem:
feed68a5 _lwp_kill (5, 6, 22c4, fef45000, fef45000, c) + 15
fee68a7b raise (6) + 2b
fee41cde abort () + 10e
08079939 fmd_panic (8081400)
0807994b fmd_panic (8081400) + 12
08065394 fmd_alloc (50, 1) + 81
0806f6a5 fmd_event_create (1, d1da323a, 1bd4e8f, 0) + 18
08073ae3 fmd_module_timeout (fb8ef100, 2a1, d1da323a) + 20
0807bd21 fmd_timerq_exec (915db80) + 127
0807b299 fmd_thread_start (8131030) + 5b
feed1a3b _thrp_setup (fed82a40) + 88
feed1bd0 _lwp_start (fed82a40, 0, 0, 0, 0, 0)
I can't believe this global zone is out of virtual memory, it's running various zones with a lot of processes and they all goes fine.
Only fmd here is going panic.
What I found is an old issue I even forgot about: an infolog_hival file is being produced continuously.
Running a tail -f on it I get a continuous output like:
port_address w500304801d0a8808LH
PhyIdentifier88 %/pci@0,0/pci8086,2f02@1/pci15d9,808@0((
event_type port_broadcast_sesTPclass 3resource.sysevent.EC_hba.ESC_sas_hba_port_broadcast version __ttl0(__todf▒'|▒,▒▒,^C
As I remember, this may go on for some time then it will stop.
Any idea?
G
Sonicle S.r.l. : http://www.sonicle.com
Music: http://www.gabrielebulfon.com
eXoplanets : https://gabrielebulfon.bandcamp.com/album/exoplanets
Da: Toomas Soome via illumos-developer <developer@lists.illumos.org>
A: illumos-developer <developer@lists.illumos.org>
Data: 22 luglio 2024 16.10.42 CEST
Oggetto: Re: [developer] fmd core dump
On 22. Jul 2024, at 17:01, Gabriele Bulfon via illumos-developer <developer@lists.illumos.org> wrote:
Hi, I have a couple of systems, installed in 2012 and updated up to illumos 2019 (will have to update to 2024 later).
They periodically (every 3-4 months, sometimes earlier) create a core dump under /var/fm/fmd.
Looks like fmd core dumped, so no email notice is sent, and we end up filling the rpool.
I found this link: https://support.oracle.com/knowledge/Sun%20Microsystems/1020519_1.html
So here I attach the pstack of one of the dumps.
Any idea?
fmd_alloc() does panic when we are out of memory:
if (data == NULL)
fmd_panic("insufficient memory (%u bytes needed)\n", size);
You can try adding some more swap space perhaps?
rgds,
toomas
Gabriele
Sonicle S.r.l. : http://www.sonicle.com
Music: http://www.gabrielebulfon.com
eXoplanets : https://gabrielebulfon.bandcamp.com/album/exoplanets
<core.fmd.dump.pstack.txt>
illumos / illumos-developer / see discussions + participants + delivery options Permalink
[-- Attachment #1.2: Type: text/html, Size: 10249 bytes --]
next prev parent reply other threads:[~2024-08-09 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 14:01 Gabriele Bulfon
2024-07-22 14:10 ` [developer] " Toomas Soome
2024-07-22 14:21 ` Gabriele Bulfon
2024-08-09 14:43 ` Gabriele Bulfon [this message]
2024-08-09 16:28 ` Peter Tribble
2024-08-09 16:54 ` Toomas Soome
2024-08-09 16:47 ` Pramod Batni
-- strict thread matches above, loose matches on Subject: below --
2020-03-20 14:27 Gabriele Bulfon
2020-03-20 14:50 ` [developer] " Joerg Schilling
2020-03-20 16:02 ` RomanS
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=148564749.1666.1723214608129@www \
--to=gbulfon@sonicle.com \
--cc=developer@lists.illumos.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).