From: maurilio.longo@libero.it
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] panic inside lmrc driver
Date: Mon, 19 Feb 2024 16:14:07 -0500 [thread overview]
Message-ID: <17083772470.e500A6BA.762619@composer.illumos.topicbox.com> (raw)
In-Reply-To: <17081161030.AA4fC5EE.45783@composer.illumos.topicbox.com>
[-- Attachment #1: Type: text/plain, Size: 4015 bytes --]
Hi all,
new problem today, similar to a previous one with loss of access to disks inside 'dati' pool.
Feb 19 15:39:41 pg-1 lmrc: [ID 408335 kern.warning] WARNING: lmrc0: resetting...
Feb 19 15:39:42 pg-1 lmrc: [ID 408335 kern.warning] WARNING: lmrc0: resetting...
Feb 19 15:39:42 pg-1 lmrc: [ID 408335 kern.warning] WARNING: lmrc0: resetting...
Feb 19 15:39:42 pg-1 lmrc: [ID 383856 kern.warning] WARNING: lmrc0: reset failed
Feb 19 15:39:42 pg-1 lmrc: [ID 998901 kern.warning] WARNING: lmrc0: AEN failed, status = 255
Feb 19 15:39:42 pg-1 lmrc: [ID 380853 kern.warning] WARNING: lmrc0: LD target map sync failed, status = 255
Feb 19 15:39:42 pg-1 lmrc: [ID 831201 kern.warning] WARNING: lmrc0: PD map sync failed, status = 255
Feb 19 15:39:42 pg-1 lmrc: [ID 383856 kern.warning] WARNING: lmrc0: reset failed
Feb 19 15:39:43 pg-1 zfs: [ID 961531 kern.warning] WARNING: Pool 'dati' has encountered an uncorrectable I/O failure and has been sus>
Feb 19 15:39:43 pg-1 zfs: [ID 961531 kern.warning] WARNING: Pool 'dati' has encountered an uncorrectable I/O failure and has been sus>
Feb 19 15:39:43 pg-1 zfs: [ID 961531 kern.warning] WARNING: Pool 'dati' has encountered an uncorrectable I/O failure and has been sus>
Feb 19 15:39:43 pg-1 zfs: [ID 961531 kern.warning] WARNING: Pool 'dati' has encountered an uncorrectable I/O failure and has been sus>
Feb 19 15:39:43 pg-1 zfs: [ID 961531 kern.warning] WARNING: Pool 'dati' has encountered an uncorrectable I/O failure and has been sus>
Feb 19 15:39:43 pg-1 zfs: [ID 961531 kern.warning] WARNING: Pool 'dati' has encountered an uncorrectable I/O failure and has been sus>
Feb 19 15:39:43 pg-1 zfs: [ID 961531 kern.warning] WARNING: Pool 'dati' has encountered an uncorrectable I/O failure and has been sus>
Feb 19 15:39:43 pg-1 zfs: [ID 961531 kern.warning] WARNING: Pool 'dati' has encountered an uncorrectable I/O failure and has been sus>
Feb 19 15:40:10 pg-1 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,43b8@1c/pci1590,32b@0/iport@v0/disk@5000cca85ee5ecb0,0 >
Feb 19 15:40:10 pg-1 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,43b8@1c/pci1590,32b@0/iport@v0/disk@50014ee6b2513c38,0 >
Feb 19 15:40:10 pg-1 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,43b8@1c/pci1590,32b@0/iport@v0/disk@5000c500aaf9b0c3,0 >
Feb 19 15:40:10 pg-1 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,43b8@1c/pci1590,32b@0/iport@v0/disk@5000c500aaf9bf2f,0 >
Feb 19 15:40:10 pg-1 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,43b8@1c/pci1590,32b@0/iport@v0/disk@5000cca85ee5ecb0,0 >
Feb 19 15:40:10 pg-1 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,43b8@1c/pci1590,32b@0/iport@v0/disk@50014ee6b2513c38,0 >
Feb 19 15:40:10 pg-1 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,43b8@1c/pci1590,32b@0/iport@v0/disk@5000c500aaf9b0c3,0 >
Feb 19 15:40:10 pg-1 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,43b8@1c/pci1590,32b@0/iport@v0/disk@5000c500aaf9bf2f,0 >
Feb 19 15:40:46 pg-1 fmd: [ID 377184 daemon.error] SUNW-MSG-ID: ZFS-8000-FD, TYPE: Fault, VER: 1, SEVERITY: Major#012EVENT-TIME: Mon >
Feb 19 15:40:46 pg-1 fmd: [ID 377184 daemon.error] SUNW-MSG-ID: ZFS-8000-FD, TYPE: Fault, VER: 1, SEVERITY: Major#012EVENT-TIME: Mon >
Feb 19 15:40:47 pg-1 fmd: [ID 377184 daemon.error] SUNW-MSG-ID: ZFS-8000-FD, TYPE: Fault, VER: 1, SEVERITY: Major#012EVENT-TIME: Mon >
Feb 19 15:40:47 pg-1 fmd: [ID 377184 daemon.error] SUNW-MSG-ID: ZFS-8000-FD, TYPE: Fault, VER: 1, SEVERITY: Major#012EVENT-TIME: Mon >
Feb 19 15:42:44 pg-1 unix: [ID 836849 kern.notice] #012#015panic[cpu0]/thread=fffffeb1f5b1e100:
Feb 19 15:42:44 pg-1 genunix: [ID 156897 kern.notice] forced crash dump initiated at user request
Feb 19 15:42:44 pg-1 unix: [ID 100000 kern.notice] #012
I've forced a kernel dump which can be seen here.
https://mega.nz/file/ojVHjQyI#63qlDThAL3FvM4pB04QmkjraMh4hoKXmaN5aHyC3-UU
Today, when the problem arised, I had just iozone running "alone".
Regards.
Maurilio.
[-- Attachment #2: Type: text/html, Size: 12578 bytes --]
next prev parent reply other threads:[~2024-02-19 21:14 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 10:31 maurilio.longo
2024-02-07 11:14 ` [developer] " Peter Tribble
2024-02-07 11:16 ` Hans Rosenfeld
2024-02-07 11:46 ` maurilio.longo
2024-02-07 12:04 ` maurilio.longo
2024-02-07 12:29 ` Hans Rosenfeld
2024-02-07 13:01 ` maurilio.longo
2024-02-07 16:47 ` maurilio.longo
2024-02-07 17:01 ` Hans Rosenfeld
2024-02-07 21:35 ` Hans Rosenfeld
2024-02-08 7:59 ` maurilio.longo
2024-02-08 10:42 ` Hans Rosenfeld
2024-02-08 11:01 ` maurilio.longo
2024-02-09 8:06 ` maurilio.longo
2024-02-09 19:55 ` Hans Rosenfeld
2024-02-09 20:36 ` maurilio.longo
2024-02-12 8:11 ` maurilio.longo
2024-02-13 19:32 ` Hans Rosenfeld
2024-02-13 20:55 ` maurilio.longo
2024-02-13 21:03 ` maurilio.longo
2024-02-15 6:50 ` maurilio.longo
2024-02-15 7:38 ` Carsten Grzemba
2024-02-15 8:11 ` Toomas Soome
2024-02-15 9:44 ` maurilio.longo
2024-02-16 14:36 ` maurilio.longo
2024-02-16 15:20 ` maurilio.longo
2024-02-16 15:27 ` maurilio.longo
2024-02-16 15:42 ` Robert Mustacchi
2024-02-16 20:41 ` maurilio.longo
2024-02-19 21:14 ` maurilio.longo [this message]
2024-02-20 8:58 ` maurilio.longo
2024-02-22 17:44 ` maurilio.longo
2024-02-26 8:59 ` maurilio.longo
2024-02-26 9:30 ` Carsten Grzemba
2024-08-26 12:30 ` manipm
2024-08-26 15:23 ` Hans Rosenfeld
2024-02-13 19:23 ` Hans Rosenfeld
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=17083772470.e500A6BA.762619@composer.illumos.topicbox.com \
--to=maurilio.longo@libero.it \
--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).