From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Erwan Velu <erwanaliasr1@gmail.com>
Cc: Erwan Velu <e.velu@criteo.com>,
Don Brace <don.brace@microsemi.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
esc.storagedev@microsemi.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] scsi: smartpqi_init: Reporting 'logical unit failure'
Date: Wed, 06 Mar 2019 12:34:26 -0500 [thread overview]
Message-ID: <yq1y35rzz31.fsf@oracle.com> (raw)
In-Reply-To: <20190301160806.16099-1-e.velu@criteo.com> (Erwan Velu's message of "Fri, 1 Mar 2019 17:08:06 +0100")
Erwan,
> When the HARDWARE_ERROR/0x3e/0x1 case is triggered, the logical volume
> is offlined. When reading the kernel log, the reason why the device
> got offlined isn't reported to the user. This situation makes
> difficult for admins to estimate the root cause of the issue they
> analize.
Applied to 5.1/scsi-queue, thanks.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-03-06 17:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 16:31 [PATCH] scsi: smartpqi_init: Reporting 'logical unit failure' Erwan Velu
2019-02-27 16:31 ` Erwan Velu
2019-02-28 13:09 ` Erwan Velu
2019-02-28 20:03 ` Elliott, Robert (Persistent Memory)
2019-03-01 14:59 ` Erwan Velu
2019-03-01 14:58 ` [PATCH v2] " Erwan Velu
2019-03-01 14:58 ` Erwan Velu
2019-03-01 15:26 ` James Bottomley
2019-03-01 15:43 ` Erwan Velu
2019-03-01 15:56 ` James Bottomley
2019-03-01 16:00 ` Erwan Velu
2019-03-01 16:08 ` [PATCH v3] " Erwan Velu
2019-03-01 16:08 ` Erwan Velu
2019-03-05 22:30 ` Don.Brace
2019-03-05 22:30 ` Don.Brace
2019-03-06 17:34 ` Martin K. Petersen [this message]
2019-03-11 16:36 ` Erwan Velu
2019-03-11 16:43 ` Erwan Velu
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=yq1y35rzz31.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=don.brace@microsemi.com \
--cc=e.velu@criteo.com \
--cc=erwanaliasr1@gmail.com \
--cc=esc.storagedev@microsemi.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.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.