From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "martin@lichtvoll.de" <martin@lichtvoll.de>,
"ming.lei@redhat.com" <ming.lei@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"hdegoede@redhat.com" <hdegoede@redhat.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"regressions@leemhuis.info" <regressions@leemhuis.info>,
"tj@kernel.org" <tj@kernel.org>,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>
Subject: Re: [Possible REGRESSION, 4.16-rc4] Error updating SMART data during runtime and could not connect to lvmetad at some boot attempts
Date: Tue, 13 Mar 2018 14:56:54 +0000 [thread overview]
Message-ID: <1520953013.2638.2.camel@wdc.com> (raw)
In-Reply-To: <20180313143222.GA10883@ming.t460p>
T24gVHVlLCAyMDE4LTAzLTEzIGF0IDIyOjMyICswODAwLCBNaW5nIExlaSB3cm90ZToNCj4gT24g
VHVlLCBNYXIgMTMsIDIwMTggYXQgMDI6MDg6MjNQTSArMDEwMCwgTWFydGluIFN0ZWlnZXJ3YWxk
IHdyb3RlOg0KPiA+IE1pbmcgYW5kIEJhcnQsIEkgYWRkZWQgeW91IHRvIGNjLCBjYXVzZSBJIGhh
ZCB0byBkbyB3aXRoIHlvdSBhYm91dCBhbm90aGVyIA0KPiA+IGJsay1tcSByZXBvcnQsIHBsZWFz
ZSBmZWVsIGZyZWUgdG8gYWRhcHQuDQo+IA0KPiBMb29rcyBSSVAgcG9pbnRzIHRvIHNjc2lfdGlt
ZXNfb3V0KzB4MTcvMHgxZDAsIG1heWJlIGEgU0NTSSByZWdyZXNzaW9uPw0KDQpJIHRoaW5rIHRo
YXQgaXQncyBtdWNoIG1vcmUgbGlrZWx5IHRoYXQgdGhpcyBpcyBhIGJsb2NrIGxheWVyIHJlZ3Jl
c3Npb24uIFNlZQ0KZS5nLiAiW1BBVENIIHYyXSBibGstbXE6IEZpeCByYWNlIGJldHdlZW4gcmVz
ZXR0aW5nIHRoZSB0aW1lciBhbmQgY29tcGxldGlvbg0KaGFuZGxpbmciIChodHRwczovL3d3dy5t
YWlsLWFyY2hpdmUuY29tL2xpbnV4LWJsb2NrQHZnZXIua2VybmVsLm9yZy9tc2cxODMzOC5odG1s
KS4NCg0KQmFydC4=
prev parent reply other threads:[~2018-03-13 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <27165802.vQ9JbjrmvU@merkaba>
[not found] ` <f6e73c8e-1186-744b-c856-2c56ceeeab10@redhat.com>
2018-03-13 13:08 ` [Possible REGRESSION, 4.16-rc4] Error updating SMART data during runtime and could not connect to lvmetad at some boot attempts Martin Steigerwald
2018-03-13 14:32 ` Ming Lei
2018-03-13 14:56 ` Bart Van Assche [this message]
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=1520953013.2638.2.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=hdegoede@redhat.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=martin@lichtvoll.de \
--cc=ming.lei@redhat.com \
--cc=regressions@leemhuis.info \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox