From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 187221] HPSA resetting logical / reset logical
Date: Mon, 29 Mar 2021 02:18:16 +0000 [thread overview]
Message-ID: <bug-187221-11613-UFf6CTHzl2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-187221-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=187221
vsudo (vsudoblog@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vsudoblog@gmail.com
--- Comment #2 from vsudo (vsudoblog@gmail.com) ---
I have a HPE Gen9 using RAI5, I get this error and distributed on this server
is resynced and I don't understand the reason why OS doesn't accept and failure
disk in RAID5 is normal.
[Sun Mar 28 09:47:04 2021] hpsa 0000:03:00.0: device is ready.
[Sun Mar 28 09:47:04 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: reset logical
completed successfully Direct-Access HP LOGICAL VO
LUME RAID-5 SSDSmartPathCap- En- Exp=1
[Sun Mar 28 09:54:54 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: resetting logical
Direct-Access HP LOGICAL VOLUME RAID-5 SSDSm
artPathCap- En- Exp=1
[Sun Mar 28 09:55:50 2021] hpsa 0000:03:00.0: device is ready.
[Sun Mar 28 09:55:50 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: reset logical
completed successfully Direct-Access HP LOGICAL VO
LUME RAID-5 SSDSmartPathCap- En- Exp=1
[Sun Mar 28 09:56:35 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: resetting logical
Direct-Access HP LOGICAL VOLUME RAID-5 SSDSm
artPathCap- En- Exp=1
[Sun Mar 28 09:57:01 2021] hpsa 0000:03:00.0: device is ready.
[Sun Mar 28 09:57:01 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: reset logical
completed successfully Direct-Access HP LOGICAL VO
LUME RAID-5 SSDSmartPathCap- En- Exp=1
[Sun Mar 28 10:00:56 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: resetting logical
Direct-Access HP LOGICAL VOLUME RAID-5 SSDSm
artPathCap- En- Exp=1
[Sun Mar 28 10:00:57 2021] hpsa 0000:03:00.0: device is ready.
[Sun Mar 28 10:00:57 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: reset logical
completed successfully Direct-Access HP LOGICAL VO
LUME RAID-5 SSDSmartPathCap- En- Exp=1
[Sun Mar 28 10:05:13 2021] hpsa 0000:03:00.0: scsi 0:1:0:4: resetting logical
Direct-Access HP LOGICAL VOLUME RAID-5 SSDSm
artPathCap- En- Exp=1
[Sun Mar 28 10:07:16 2021] INFO: task scsi_eh_0:473 blocked for more than 120
seconds.
[Sun Mar 28 10:07:16 2021] Not tainted 4.15.0-55-generic #60-Ubuntu
[Sun Mar 28 10:07:16 2021] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[Sun Mar 28 10:07:16 2021] scsi_eh_0 D 0 473 2 0x80000000
[Sun Mar 28 10:07:16 2021] Call Trace:
[Sun Mar 28 10:07:16 2021] __schedule+0x291/0x8a0
[Sun Mar 28 10:07:16 2021] ? dev_printk_emit+0x4a/0x70
[Sun Mar 28 10:07:16 2021] schedule+0x2c/0x80
[Sun Mar 28 10:07:16 2021] schedule_timeout+0x1cf/0x350
[Sun Mar 28 10:07:16 2021] ? __dev_printk+0x3c/0x80
[Sun Mar 28 10:07:16 2021] ? dev_printk+0x56/0x80
[Sun Mar 28 10:07:16 2021] io_schedule_timeout+0x1e/0x50
[Sun Mar 28 10:07:16 2021] wait_for_completion_io+0xba/0x140
[Sun Mar 28 10:07:16 2021] ? wake_up_q+0x80/0x80
[Sun Mar 28 10:07:16 2021] hpsa_scsi_do_simple_cmd.isra.60+0xb3/0xf0 [hpsa]
[Sun Mar 28 10:07:16 2021] hpsa_eh_device_reset_handler+0x3e4/0x7b0 [hpsa]
[Sun Mar 28 10:07:16 2021] ? __switch_to_asm+0x40/0x70
[Sun Mar 28 10:07:16 2021] ? __switch_to_asm+0x34/0x70
[Sun Mar 28 10:07:16 2021] ? scsi_device_put+0x2b/0x30
[Sun Mar 28 10:07:16 2021] scsi_eh_ready_devs+0x333/0xbf0
[Sun Mar 28 10:07:16 2021] ? __pm_runtime_resume+0x5b/0x80
[Sun Mar 28 10:07:16 2021] ? scsi_try_target_reset+0x90/0x90
[Sun Mar 28 10:07:16 2021] scsi_error_handler+0x4c3/0x5b0
[Sun Mar 28 10:07:16 2021] kthread+0x121/0x140
[Sun Mar 28 10:07:16 2021] ? scsi_eh_get_sense+0x200/0x200
[Sun Mar 28 10:07:16 2021] ? kthread_create_worker_on_cpu+0x70/0x70
[Sun Mar 28 10:07:16 2021] ret_from_fork+0x35/0x40
[Sun Mar 28 10:07:16 2021] INFO: task systemd-journal:109135 blocked for more
than 120 seconds.
[Sun Mar 28 10:07:16 2021] Not tainted 4.15.0-55-generic #60-Ubuntu
[Sun Mar 28 10:07:16 2021] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[Sun Mar 28 10:07:16 2021] systemd-journal D 0 109135 1 0x00000320
[Sun Mar 28 10:07:16 2021] Call Trace:
[Sun Mar 28 10:07:16 2021] __schedule+0x291/0x8a0
[Sun Mar 28 10:07:16 2021] ? intel_pstate_update_pstate+0x40/0x40
My website: https://vsudo.blog
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-03-29 2:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 13:39 [Bug 187221] New: HPSA resetting logical / reset logical bugzilla-daemon
2016-11-16 6:19 ` [Bug 187221] " bugzilla-daemon
2021-03-29 2:18 ` bugzilla-daemon [this message]
2021-03-29 2:19 ` bugzilla-daemon
2021-03-29 2:20 ` bugzilla-daemon
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=bug-187221-11613-UFf6CTHzl2@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.